Please revert to debian-alternatives based prime-select
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-prime (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The new prime-select has some problems.
It is very slow to switch, since it does initramfs -u each time
It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers.
These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux.
I know there is bug in logind meaning that a restart is required to poweroff the nvidia card.
But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-prime 0.8.7
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 21 12:25:58 2018
Dependencies:
InstallationDate: Installed on 2017-10-19 (183 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitec
SourcePackage: nvidia-prime
UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago)
Changed in nvidia-prime (Ubuntu): | |
status: | Confirmed → Fix Released |
I think this is all a repercussion of using glvnd.
I tried switching to intel mode and this results in a machine that cannot be logged in to. Also, the other framebuffer ttys are nt accessible. I recovered by going into friendly-recovery, getting a root shell, remounting my ssd as rw and executing prime-select nvidia then rebooting.