bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bumblebee (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
bumblebee fails to work in Ubuntu 18.04 with nvidia-driver-390 unless these configuration changes are made:
1. For optirun to work, /etc/bumblebee/
[driver-nvidia]
LibraryPath=
XorgModulePath=
With these changes, optirun works correctly on my laptop (using the primus bridge) but primusrun still fails.
2. For power management to work (ie turning the nvidia card off whilst not in use), the nouveau and nvidia modules need blacklisting so they don't load on boot, and nvidia_drm and nvidia_modeset need aliasing to off so they never load. Otherwise, nvidia_drm attaches to drm_kms_helper and then bumblebee can't unload the nvidia module and turn off the card. This configuration file in /etc/modprobe.
blacklist nouveau
blacklist nvidia
blacklist nvidia_drm
blacklist nvidia_modeset
alias nouveau off
alias nvidia_drm off
alias nvidia_modeset off
(The first two lines are already in bumblebee.conf. I found I also had to alias nouveau to off because gdm?/mutter? so desperately wants to load it.)
Update: aliasing nouveau to off doesn't stop the nvidia-fallback service from loading the nouveau module, so if nouveau is still loading, you could try running this command:
systemctl disable nvidia-
You'll need to reboot because nouveau is already loaded, but the change should be permanent unless something else re-enables the nvidia-fallback service.
Finally, to run mesa applications, you need to set this variable:
export __GLVND_
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bumblebee 3.2.1-17
Uname: Linux 4.16.0-
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 12:18:02 2018
InstallationDate: Installed on 2017-08-16 (218 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: bumblebee
UpgradeStatus: Upgraded to bionic on 2017-11-17 (125 days ago)
modified.
modified.
mtime.conffile.
mtime.conffile.
mtime.conffile.
Status changed to 'Confirmed' because the bug affects multiple users.