Bug#718774: Nvidia module rename patch break bumblebee

LOMBARD Maxime berillions at gmail.com
Wed Aug 7 16:11:48 UTC 2013


To launch glxgears with Intel card correctly, i must to re-install mesa-glx
and nvidia-glx (I launch this command with Nvidia 304.88 and it works) :

> aptitude reinstall libgl1-mesa-glx libgl1-mesa-glx:i386 libgl1-nvidia-glx
> libgl1-nvidia-glx:i386 bumblebee-nvidia
>

So now, if i launch "update-alternatives --config glx", i have this result :

> 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
>
>
If i launch "glxgears", i have this :

> Error: couldn't get an RGB, Double-buffered visual
>

For "primusrun glxgears", i have this :

> primus: fatal: Bumblebee daemon reported: error: Could not load GPU driver
>


2013/8/7 LOMBARD Maxime <berillions at gmail.com>

> Hi Vincent,
>
> 1- I re-installed Debian Sid + Nvidia Experimental. Concerning
> "nvidia-modprobe.conf, i have this :
>
>> berillions at 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 at 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 <vincentc1208 at 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).
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20130807/ab5ecdf5/attachment.html>


More information about the pkg-nvidia-devel mailing list