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

[Andreas Beckmann]

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 depends
> on both legacy main and current main modules, but it turns out it doesn't make
> any difference).

That is actually the culprit.

In my case I could produce something similar:

modules.dep:nvidia/nvidia-legacy-340xx.ko: kernel/drivers/gpu/drm/drm.ko kernel/drivers/i2c/i2c-core.ko
modules.dep:nvidia/nvidia-current-uvm.ko: nvidia/nvidia-current.ko kernel/drivers/gpu/drm/drm.ko kernel/drivers/i2c/i2c-core.ko
modules.dep:nvidia/nvidia-current.ko: kernel/drivers/gpu/drm/drm.ko kernel/drivers/i2c/i2c-core.ko
modules.dep:nvidia/nvidia-legacy-340xx-uvm.ko: nvidia/nvidia-current.ko kernel/drivers/gpu/drm/drm.ko kernel/drivers/i2c/i2c-core.ko

Loading nvidia-legacy-340xx-uvm would trigger loading the nvidia-current module
(which is turned into a harmless no-op if nvidia-legacy-340xx was already loaded)


I now have a modprobe.conf (using only install and remove, no more alias)
that does these commands correctly:

modprobe nvidia		# use the options
modprobe nvidia-uvm	# load both, use the options for nvidia
modprobe -r nvidia	# unload both
modprobe -r nvidia-uvm	# unload only uvm

is there any need that the following also works *correctly*

modprobe nvidia-FOO
modprobe nvidia-FOO-uvm	# load both
modprobe -r nvidia-FOO	# unload both
modprobe -r nvidia-FOO-uvm

for FOO \in {current, -legacy-XYZxx}?

That may be impossible without patching the module source ...

What would be the caller for these?


Andreas