Bug#798207: nvidia-legacy-340xx-driver: Wrong module loaded, X fails to start when legacy installed alongside mainline driver

Luca Boccassi luca.boccassi at gmail.com
Tue Sep 15 08:44:49 UTC 2015

On Sep 15, 2015 03:15, "Andreas Beckmann" <anbe at debian.org> wrote:
> On 2015-09-06 21:14, Luca Boccassi wrote:
> > I tried looking into modules.dep and seeing what depmod was doing, but
it all
> > looks fine (minus a minor thing that turns out is unrelated: legacy-uvm
> > on both legacy main and current main modules, but it turns out it
doesn't make
> > any difference).
> That is actually the culprit.

If I remember correctly, to test that I just deleted the legacy uvm module
and ran depmod again, but it didn't make any difference, I think because
uvm is not loaded at boot anyway. This is all from memory as I can't check
right now. Later tonight or tomorrow I'll look again and give more details
and answer all the other questions. Sorry for the delay!

Kind regards,
Luca Boccassi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20150915/4c84bb52/attachment-0001.html>

More information about the pkg-nvidia-devel mailing list