I had all this working wonderfully on a Thinkpad T480 on Ubuntu Disco, until a recent reboot after an update (possibly due to kernel 5.0.0-27, possibly due to a udev update)
bbswitch would fail to enable the card, with the following in dmesg: pci 0000:00:01.0: Refused to change power state, currently in D3 After a lot of futzing about and installing/reinstalling, the steps mentioned in the OP, #31, #32 and #35 worked, with the following change to bumblebee.conf: PMMethod=none I think that this means that my nvidia card is on all the time -- I'm not sure how to check its state with bbswitch disabled -- but I can at least run the desktop off of the Intel card, and games and such off of the nvidia card, which helps with stability and heat for me. (It's possible that I did something to change the acpi power management settings when booting the kernel, and those changes got blown up by the update.) -- You received this bug notification because you are a member of Bumblebee Project, which is subscribed to bumblebee in Ubuntu. Matching subscriptions: Bumblebee Team https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 Status in bumblebee package in Ubuntu: Confirmed 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/bumblebee.conf needs two library paths changed (because of the changes for GLVND): [driver-nvidia] LibraryPath=/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu XorgModulePath=/usr/lib/x86_64-linux-gnu/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules/input 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.d/nvidia- bl.conf works for me: 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-fallback.service 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_DISALLOW_PATCHING=1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bumblebee 3.2.1-17 Uname: Linux 4.16.0-041600rc6-generic x86_64 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.conffile..etc.bumblebee.xorg.conf.nouveau: [modified] modified.conffile..etc.bumblebee.xorg.conf.nvidia: [modified] mtime.conffile..etc.bumblebee.bumblebee.conf: 2018-03-23T12:17:54.683287 mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2018-03-22T14:01:52.732698 mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2018-03-22T14:57:34.141995 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- Mailing list: https://launchpad.net/~bumblebee Post to : bumblebee@lists.launchpad.net Unsubscribe : https://launchpad.net/~bumblebee More help : https://help.launchpad.net/ListHelp