hard to get rid of nouveau

[Florian Hänel]

I spent half a day trying to get rid of nouveau, as it was crashing on suspend.

I added it to the kenrel commandline as nouveau.blacklist=yes and made sure it was in modprobe.d from the nvidia package installed nvidia-graphics-drivers.conf yet it still keeps being loaded.

I checked the initrd contained all the blacklists above.

Finally I stumbled across /lib/systemd/system/nvidia-fallback.service as the culprit. I had to manually disable it since it did not realize I am on prime and wanted the intel integrated graphics by default.

[Florian Hänel (heeen)]

this is on 18.04, nvidia-396, kernel 4.17.11

[Florian Hänel (heeen)]

I think this service should check if nvidia is wanted with prime-select

[martin (martin-andersen)]

Had the same 'experience' with several of our systems this week. What I fail to comprehend is why the <expletive> can this override 'nouveau.blacklist=1' & 'rdblacklist=nouveau' kernel options as well as blacklist statements in modprobe -

/etc/modprobe.d/nvidia-384_hybrid.conf:blacklist nouveau
/etc/modprobe.d/nvidia-384_hybrid.conf:blacklist lbm-nouveau
/etc/modprobe.d/nvidia-384_hybrid.conf:alias nouveau off
/etc/modprobe.d/nvidia-384_hybrid.conf:alias lbm-nouveau off
/etc/modprobe.d/nvidia-graphics-drivers.conf:blacklist nouveau
/etc/modprobe.d/nvidia-graphics-drivers.conf:blacklist lbm-nouveau
/etc/modprobe.d/nvidia-graphics-drivers.conf:alias nouveau off
/etc/modprobe.d/nvidia-graphics-drivers.conf:alias lbm-nouveau off

All of which have worked properly in the past. The initrd was rebuilt with those settings in place.

To the person only experiencing this during suspend: you were lucky. Neither of the systems with 1080 & 1080 Ti Nvidia cards would even let you log in with the noveau driver active (X crashes immediately). There was a very good reason it was disabled, but naturally systemd should be able to override it simply with a new service file...

[Florian Hänel (heeen)]

To be fair, systemd does not ship the fallback file, the Nvidia package does.

[martin (martin-andersen)]

That is correct. However, systemd still facilitates loading a kernel module which is clearly blacklisted in both kernel boot options and in modprobe.d conf files. It is unwanted behaviour.