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

Andreas Beckmann anbe at debian.org
Mon Sep 14 10:43:36 UTC 2015

On 2015-09-06 21:14, Luca Boccassi wrote:
> When both legacy and mainline drivers are installed, and the mainline is
> selected through update-alternatives, the legacy kernel module is loaded on
> boot, causing X to fail to start.
> When testing the new legacy series with the renamed uvm module, I somehow
> missed this. No clue how that could happen, my sincere apologies.

> I'm out of ideas. Any clue where to look next?

When is the module loaded? From initrd or later?

Is the module included in the initrd at all? (Usually there is no need
for this.)

Are you sure your initrd was up-to-date, it could contain stale modprobe
config (rebuild it with update-initramfs -u)?

What is triggering the module load?

Something in /etc/modules or /etc/modules-load.d?
(we should collect this information in our bug script, too)


More information about the pkg-nvidia-devel mailing list