Reverting rmmod->modprobe change in bumblebee/3.2.1-8 (was: Re: Bumblebee functionality broken by the last update made by Vincent Cheng on 26-July-2015 - please react as fast as possible)
luca.boccassi at gmail.com
Sat Aug 8 17:36:45 UTC 2015
On Fri, 2015-08-07 at 01:07 -0700, Vincent Cheng wrote:
> Hi Luca,
> (cc-ing upstream and original bug reporter)
> It seems that your fix for #793389 (the rmmod->modprobe patch you
> committed as ), which I recently backported to the bumblebee PPA
>  (source at ) to keep the PPA packages in sync with the packages
> in Debian/Ubuntu, is likely the source of a regression for Ubuntu
> users using that PPA (see conversation below, and ), i.e. the
> nvidia kernel module isn't being automatically unloaded using modprobe
> for some reason (but apparently worked with rmmod previously). I'm not
> sure why this happens; I suspect it has something to do with Ubuntu's
> nvidia packages not including an alias even though they rename the
> module like Debian's packages. Since it does cause a regression in
> Ubuntu, and just by skimming #793389 I don't quite understand whether
> this fixes anything in Debian (isn't the fix for #793386 enough to fix
> module unloading?), would you be ok with me reverting ? Upstream is
> also suggesting that the patch be reverted.
I have pushed a new branch for review on Alioth , please have a look
when you have time.
The idea is, if building on Ubuntu, to add an alias and a remove rule
for each driver supported by Bumblebee.
The alias is necessary because it seems that, due to how the
update-alternatives is handled on Ubuntu, a modprobe rule for the driver
is not installed if the main provider of libgl is not the Nvidia driver
Please let me know what you think!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part
More information about the pkg-nvidia-devel