Hi Vincent, 1- I re-installed Debian Sid + Nvidia Experimental. Concerning "nvidia-modprobe.conf, i have this :
> berillions@debian64:~$ cat /etc/nvidia/nvidia-modprobe.conf > alias nvidia nvidia-current > 2- Result of "update-alternatives --config glx" before to re-install "libgl1-mesa-glx" : > root@debian64:/home/berillions# update-alternatives --config glx > There is only a "alternative" in the group of links glx (which supplies > /usr/lib/glx) : /usr/lib/nvidia > --> I tried to launch primusrun glxgears : "primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver" 3- Result after to re-install "libgl1-mesa-glx" : > It exist 2 choices for alternative glx (which supplies /usr/lib/glx). > > Select Way Priority State > ------------------------------------------------------------ > * 0 /usr/lib/nvidia 100 automatic mode > 1 /usr/lib/mesa-diverted 5 manual mode > 2 /usr/lib/nvidia 100 manual mode > I must to choose "/usr/lib/mesa-diverted" ? 2013/8/7 Vincent Cheng <vincentc1...@gmail.com> > 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). >
