Bug#718774: Nvidia module rename patch break bumblebee

Vincent Cheng vincentc1208 at gmail.com
Wed Aug 7 08:39:36 UTC 2013


Hi Maxime and Francesco,

If you could take a moment to confirm a few things for me for
debugging purposes, that'd be great.

First, can you verify that with the latest nvidia-alternative package
from experimental, that you have a file called
"/etc/nvidia/nvidia-modprobe.conf" present on your filesystem, and
that it contains an alias for the nvidia module (nvidia-current)? In
that case, the module being renamed shouldn't be an issue...

Second, please verify that:
# update-alternatives --config glx
...only gives you the option of having /usr/lib/nvidia provide the glx
alternative, but if you do:
# apt-get install --reinstall libgl1-mesa-glx
# update-alternatives --config glx
...you are now given the option to select /usr/lib/mesa-diverted as
the desired glx alternative (which you should do; your primary X
server is driven by your intel gpu and requires mesa's libGL for 3d
acceleration, not nvidia's).

Thanks,
Vincent

Note for self reference: may be related to #717650 or #718954. Also
interesting leads provided on upstream github ticket
(https://github.com/Bumblebee-Project/Bumblebee/issues/452).



More information about the pkg-nvidia-devel mailing list