Bug#802246: Can't modprobe -r nvidia, rmmod works
Luca Boccassi
luca.boccassi at gmail.com
Mon Oct 19 21:22:47 UTC 2015
On Mon, 2015-10-19 at 11:32 +0300, Alexander Monakov wrote:
> Hi, I initially triaged this bug when it was reported against bumblebee.
>
> I'm not clear why you stopped providing "alias nvidia nvidia-current"
> (and likewise for -uvm module). I believe providing that alias is
> sufficient to solve this issue. With your current scheme, "modprobe
> nvidia" works but "modprobe -r nvidia" fails. Why is that desirable?
> Why was the alias removed?
Hello Alexander,
The problem was that the nvidia's modprobe conf was moved to
glx-alternative and it was not configured (since on a bumblebee setup
glx is served by mesa). This was fixed by Andreas with a new diversion
specifically for bumblebee setups. I'm not seeing issues now with
modprobe -r nvidia.
The reason for the change was that the old version broke when
nvidia-current and nvidia-legacy-YYYxx were installed.
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20151019/82e38ab5/attachment-0001.sig>
More information about the pkg-nvidia-devel
mailing list