I’ve just installed Truenas Scale 24.04, and I see the error messages cycling on the screen:
NVRM: No NVIDIA GPU found.
nvidia-link: Unregistered Nvlink Cire, major device number 240
nvidia-link: Nvlink Core is being initialized, major device number 240
NVRM: The NVIDIA GeForve GTX 650 Ti GPU installed in this system
NVRM: is supported through the NVIDIA 470.xx Legacy drivers.
NVRM: Please visit www.nvidia.com/object/unix.html for more information.
NVRM: The 545.23.08 NVIDIA driver will ignore this GPU. Continue probe...
I’m guessing I have to downgrade the NVIDIA driver to the supported one 470.xx Legacy. How to do that?
Unfortunately we don’t have a supported method to downgrade the NVIDIA drivers to the Legacy branch. There might be a way to do it manually but it’s likely to cause overall instability and conflicts with upgrading.
Is it possible to pick up a newer, supported card like the Quadro P400 if you’re just looking for video transcode capabilities?
If you aren’t planning to use the more advanced functionality of your NVIDIA card (video encode/decode, GPU-compute, etc) then there’s no harm in only using the base display driver - however, a 650TI is probably not as power-efficient as alternative or newer cards.
To be honest all I need is the Plex server and Immich. I agree that my card isn’t powerful, I’m just reusing the old Dell computer. I need to check if it can support anything better than the installed card. Its an old Dell XPS
So, if I leave it as it is right now, is there a way to stop that cycling message on the screen? It looks like the system is constantly trying to engage that driver with the current card
I’ve only ever seen that message come up once during boot-time in dmesg for unsupported/legacy cards, not cycling through the console. Perhaps it’s Plex trying to constantly poll/restart the NVIDIA services.
Barring really weird systems, PCI Express tends to just work, and is backwards compatible. NVIDIA tends to include legacy BIOS/CSM support in their GPUs, and a P400 isn’t that new.
I have the same “issue”
Old PC that I’m just playing with… not critical at all… getting basically the same message as the OP… and I saw the question asked but no answer…
the console keeps cycling the message over and over…
is there a way to stop it?
Or is it an issue at all and just let it go and ignore the message?
I’m getting what I think is the same issue using the current build of Dragonfly (24.4.02?) using a K600 gpu. I know my gpu is not supported with the 545.23.0 driver included in this version. I know the last version to support the 470.x driver is Angelfish (original/22.x) release. I also know upgrading from 22.x to 23.x drops the legacy driver (expected, but still a bummer). I don’t need to use the gpu other than for the console (if I do later I will just get a newer card and install it as a second gpu).
What I would like to do is suppress the console messages as they are distracting at a minimum, and rather intrusive when doing console activities.
I suspect there is a service or config that could be disabled via the CLI to stop this behavior (beyond me though). Likely whatever is calling for NVLINK CORE. Possibly Kubernetes/Containers.
I THINK these started after activating support for Applications.
I THINK the message appears once per network port. I have 6 network ports on my machine and I get 5 of these dumps every 5 minutes. Only one port is currently connected. I will try disabling the other ports to see if that changes anything (pessimistic).
I do plan to install some apps later, so I’d rather not break or disable support for apps and virtual machines trying to resolve this.
Actually, there are other services I’d like to disable too to optimize the boot (eg: I am not running truenas under vmware so those things could be disabled, etc, but not an issue for today).
Update: I counted and got six of these NVLINK messages, so that matches 1:1 with the six network ports on my machine.
So far disabling some interfaces has had interesting results (not the good kind). Seems like Truenas really does not want users to disable physical interfaces once it finds them.
I think I will go back on Core. Used it for about 3 years without any problems, why I even bothered to try Scale.
The Scale is unstable and has performance issues, sometimes I have to restart the computer because I cannot login or GUI is unresponsive.
I started getting these messages after enabling a VM / Docker
I’m building a new TrueNAS machine with some upgrades and decided to go with scale rather than core as VMs seem to be better
I’m using a NVidia NVS295 pcie x1 as I’m using the PCIe x16 slots for HBA & 10Gb (cards are x8 but board only has x16 - which has been split to 2 x8) - these are handy cards as they use x1 slot which means they can free up the x16 slot for HBA in low power/cost systems, where the CPU doesn’t have integrated graphics
I’m going swap out Ryzen 1700x for a Ryzen 3 PRO 4350G (Single core performance & power usage plus Integrated graphics) I’ll report what I find
Coming back off a vacation here, sorry for the delay in response.
That card would be “supported” as a console display device, but it lacks any kind of real modern acceleration capabilities, so you wouldn’t be able to use it for anything measurable for Apps.
Folks in regards to those with older Nvidia GPUs - the drivers on Scale are now ‘too new’. Nvidia dropped support for GPUs older than the 1000 series a while back.
If you’re 100% insistent on getting the GPU operational again without making hardware changes, you’d be stuck enabling dev mode, removing current nvidia drivers, and installing old nvidia drivers.
If you’re not comfortable doing this without assistance, then I wouldn’t recommend doing it at all. Any updates to TrueNAS that you’d install after you implement would undo your changes & you’d have to repeat them.
This carries risk (unlimited power involves unlimited chances to fork up your NAS), is unsupported (not in the sense that it won’t work, but if you have any issues implementing these changes or cause issue while implementing then you’re SOL), and is something you’d have to decide by yourselves if it is worth it.
It ain’t a TrueNAS fault; it is that the drivers that most recent versions of Scale is running don’t include your GPU anymore, by design, courtesy of Nvidia.
Hopefully this answers questions on the ‘but what steps do I need to just get it working again no mater what’.
