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

[Andreas Beckmann]

On 2015-09-18 00:54, Luca Boccassi wrote:
> I am really out of ideas! :-(

so just that I got it right, you configured the nvidia alternative to
use nvidia-current and not nvidia-legacy-340xx

upon boot the 340.76 (nvidia-legacy-340xx) gets loaded by unknown means


let's start with manual (un-)loading

rmmod nvidia-uvm nvidia
modprobe -v nvidia
rmmod nvidia-uvm nvidia
modprobe -v nvidia-uvm
rmmod nvidia-uvm nvidia
modprobe -v char-major-195-0
rmmod nvidia-uvm nvidia

nvidia-modprobe
cat /proc/driver/nvidia/version
rmmod nvidia-uvm nvidia

nvidia-modprobe -u
cat /proc/driver/nvidia/version
rmmod nvidia-uvm nvidia


If no module is loaded and you have a manual xorg configuration that
enables nvidia, what happens if you start X? The module should get
loaded - the correct one? uvm, too ?



Andreas