Bug#731654: Blacklist resolved

Andreas Beckmann anbe at debian.org
Tue Dec 10 17:36:01 UTC 2013


On 2013-12-10 18:16, ael wrote:
> I see
> glx-alternative-nvidia.postinst:
> $(add_slave /etc/modprobe.d/nvidia-blacklists-nouveau.conf nvidia-blacklists-nouveau.conf /etc/nvidia/nvidia-blacklists-nouveau.conf)
> 
> I have checked and 
> /etc/modprobe.d/nvidia-blacklists-nouveau.conf
> is now present & correct.
> 
> So the dpkg-reconfigure fixed that as well - as expected, I guess.

Yes. so you can disable the nvidia driver via the alternatives and the
blacklist gets removed automatically. Well, needs a dpkg-reconfigure
glx-alternative-nvidia, but thats it.

> Thus it looks like a single point of failure: the postinst of
> glx-alternative-nvidia aborted when it found a pre-existing
> nvidia_drv.so already installed?

Can I find this somewhere in the logfiles you sent previously?

> And that in part because it does not conflict
> with the standard package?

The current and legacy driver packages are intentionally co-installable
to support e.g. live-systems. And the current driver gets the highest
priority in the alternatives, of course.

If you have any ideas how to improve the packaging and/or documentation
for the legacy drivers, I'd like to hear them - especially from a user
who got into the trouble :-)

Maybe adding another metapackage that depends on the legacy driver and
conflicts with all the other drivers - would this help? How should it be
called? Or should the "co-installable" metapackage
nvidia-legacy-173xx-driver be renamed (ito what?) and replaced by a
"only-173xx" meta-package (named nvidia-legacy-173xx-driver)?

Andreas



More information about the pkg-nvidia-devel mailing list