Comment 3 for bug 1457150

Revision history for this message
STrRedWolf (strredwolf) wrote :

I'm affected by this too, but I've found a work-around. The big thing is that the bumblebee package expects the nvidia-current package to be installed, which loads in nvidia-304... and expects the kernel module to be named "nvidia-current" and the X11 driver modules to be in /usr/lib/nvidia-current.

The problem is, that's not the current set of drivers. The latest NVidia has is 352, while Ubuntu offers 346. The kernel module for 346 in the nvidia-346-updates package is "nvidia_346_updates" and the library path is /usr/lib/nvidia-346-updates.

Well, at least the naming convention is consistent.

So? Edit /etc/bumblebee/bumblebee.conf. Change the following lines in the [driver-nvidia] section:

KernelDriver=nvidia-current
LibraryPath=/usr/lib/nvidia-current:/usr/lib32/nvidia-current
XorgModulePath=/usr/lib/nvidia-current/xorg,/usr/lib/xorg/modules

to

KernelDriver=nvidia-346-updates
LibraryPath=/usr/lib/nvidia-346-updates:/usr/lib32/nvidia-346-updates
XorgModulePath=/usr/lib/nvidia-346-updates/xorg,/usr/lib/xorg/modules

Basicaly find/replace "nvidia-current" with "nvidia-346-updates". Save, reboot, test with "primusrun glxgears". If that works, brutally test it by installing Steam and Team Fortress 2. :)