Actually, with the bumblebee package from Sid repository, the rules file used to compile bumblebee is :
If i launch "optirun -vv glxgears" for the first time with Nvidia driver from Experimental, i have this result : [ 46.563213] [DEBUG]Reading file: /etc/bumblebee/bumblebee.conf > [ 46.563666] [DEBUG]optirun version 3.2.1 starting... > [ 46.563684] [DEBUG]Active configuration: > [ 46.563707] [DEBUG] bumblebeed config file: > /etc/bumblebee/bumblebee.conf > [ 46.563722] [DEBUG] X display: :8 > [ 46.563735] [DEBUG] LD_LIBRARY_PATH: > /usr/lib/x86_64-linux-gnu/nvidia:/usr/lib/i386-linux-gnu/nvidia:/usr/lib/nvidia > [ 46.563751] [DEBUG] Socket path: /var/run/bumblebee.socket > [ 46.563766] [DEBUG] Accel/display bridge: auto > [ 46.563780] [DEBUG] VGL Compression: proxy > [ 46.563794] [DEBUG] VGLrun extra options: > [ 46.563809] [DEBUG] Primus LD Path: > /usr/lib/x86_64-linux-gnu/primus:/usr/lib/i386-linux-gnu/primus:/usr/lib/primus:/usr/lib32/primus > [ 46.571805] [DEBUG]Using auto-detected bridge primus > [ 46.982048] [INFO]Response: No - error: Could not load GPU driver > > [ 46.982062] [ERROR]Cannot access secondary GPU - error: Could not load > GPU driver > > [ 46.982066] [DEBUG]Socket closed. > [ 46.982078] [ERROR]Aborting because fallback start is disabled. > [ 46.982083] [DEBUG]Killing all remaining processes. > When i launch the same command after to replace "KernelDriver=nvidia" by "KernelDriver=nvidia-current" in "/etc/bumblebee/bumblebee.conf", i have the same message. It's very strange because this error is only for Nvidia drivers from Experimental. Nvidia driver from Exp. (255.08) and Sid (304.88) use Kernel3.10 patch. I have just seen that both drivers use the Module_rename patch but : 1- Nvidia 304.88 works without problem (module name = nvidia) 2- Why the module name for the recent driver is "nvidia-current" ? (On Archlinux, for the driver 319.32, it's always "nvidia" for the module name) 2013/8/5 Andreas Beckmann <a...@debian.org> > On 2013-08-05 12:16, LOMBARD Maxime wrote: > > With this new module name, bumblebee can't activate the nvidia driver > > because it can't load GPU driver. See Bug #717687 > > How does bumblebee load the nvidia module? > > A 'modprobe nvidia' works fine after the rename. > > > Andreas > >
