NVRM: The NVIDIA probe routine was not called for 1 device(s) - how to fix?
Steven Robbins
steve at sumost.ca
Sat Oct 5 23:15:29 BST 2024
I have recently discovered that kern.log is full of instances of the following
diagnostic:
[ 15.708329] nvidia-nvlink: Nvlink Core is being initialized, major device
number 236
[ 15.708334] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[ 15.709177] NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA
device(s).
[ 15.709178] NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
[ 15.709178] NVRM: No NVIDIA devices probed.
I run debian/unstable and this has been happening for at least a month.
Using " lsmod|grep nouveau", I can confirm that the nouveau driver is loaded.
Google and chatgpt suggest to remove or disable the nouveau. I can't remove
it because it is being used by a dozen other things at present.
I assume the idea is that it should be blacklisted. Indeed, I have a file that
indicates it should be blacklisted:
$ cat /etc/nvidia/current/nvidia-blacklists-nouveau.conf
# You need to run "update-initramfs -u" after editing this file.
# see #580894
blacklist nouveau
However, as noted above, nouveau is indeed loaded by something at boot time.
Now my questions begin:
Q0. Am I right to assume that I need to (re-)enable the nouveau blacklist?
Q1. I've used the proprietary drivers for years, and never had to manually
run "update-initramfs". Has something changed such that I need to do this?
Q2. There is no "update-initramfs" on my system. Google suggests it is part
of "initramfs-tools". However, attempting to install that will remove
"dracut", which appears to be itself a tool for creating a ramfs? I didn't
consciously choose dracut so I presume it has superceeded initramfs? Is
there a "dracut" equivalent of "update-initramfs -u"?
Q3. Assuming dracut is indeed replacing the other system, is there a command
missing in some package postinstall to do the needed magic?
Many thanks for any pointers you can provide.
-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-nvidia-devel/attachments/20241005/71873029/attachment.sig>
More information about the pkg-nvidia-devel
mailing list