1 hour ago, ConnerVT said:

Best to manually select a 580.xx.xx version

I would recommend to set the plugin to a static 580.x version since the plugin is now updated to check if there is a 580.x driver selected and it will automatically check for a 580.x driver version if the current one couldn't be found because of a system upgrade.

16 hours ago, bombz said:

Appreciate the feedback whenever someone has a moment to follow-up.

As said above, I would recommend to set a static 580.x driver version and then trigger the upgrade OS upgrade process.

3 hours ago, ConnerVT said:

If you are still using the Quadro P2000 you will want to stay on 580.xx.xx. Nvidia has obsoleted the Pascal based cards and is removing support for them from 590.xx.xx.

Best to manually select a 580.xx.xx version (latest one is fine).

Hey, appreciate the insight. Yes currently using the Quadro P2000. I was unaware of the driver/hardware support changes. Your feedback clarified the next steps.

Thank you for you time to clarify.

8 hours ago, ich777 said:

I would recommend to set the plugin to a static 580.x version since the plugin is now updated to check if there is a 580.x driver selected and it will automatically check for a 580.x driver version if the current one couldn't be found because of a system upgrade.

As said above, I would recommend to set a static 580.x driver version and then trigger the upgrade OS upgrade process.

Thanks ich777, respect you and everyone's knowledge here in the community!
It has been a busy few weeks which has taken me out of the loop, which required me to reach out for a quick sanity check before proceeding.

Was able to update the the plugin successfully today.
Attached current status of the plugin

Currently I am pending triggering the OS update as I require to select a maintenance window that works best.
From what I am understanding, before proceeding, is to manually select/set the radio button to 580.82.09 (screenshot) before pushing the OS update? If I am correct, doing this will keep it on the current version; which will allow further review of the driver, after the OS update/maintenance window?

Open to feedback, thank you again!

Thank you again.

I'll give my input here, as ich777 is offline and it is after midnight at his house. I gave a short answer earlier, as I was unsure of the current behavior of the plugin code. If you scroll through the past few pages of this thread, you will see a number of people having issues after updating their driver after removed support for the Pascal cards in the 590.xx.xx drivers. ich777's response made it more clear how the plugin is handling it.

I would proceed like this:

• Select your current version (v580.82.09) in the Available Versions area of the Nvidia plugin (not Latest v580.82.09). Click UPDATE and DOWNLOAD. The plugin will check, see that it is already installed, and quickly give you the Done button.

• You can now update the Unraid OS

During the Unraid update, there is a Nvidia helper program that checks if an Nvidia driver is installed, and updates it if the driver version currently installed is one that is available for the Unraid version you are upgrading to (ich777 needs to recompile drivers for each kernel that Unraid uses). If the driver version is not available for that kernel, it updates to one that is. In the past, it updated to the "Latest" version. Worked great for a long time.

Then things got funny. The latest RTX 5xxx GPUs require the open source drivers. The Pascal cards now only work with the 580.xx.xx (and older) drivers. Looks as ich777 now added additional checks, so if you are on a 580.xx.xx driver, it will only update to the latest version of 580.xx.xx (and not 590.xx.xx, which won't work for the Quadro Pxxxx GPUs).

I think an Available Version is a good safety net to prevent accidentally finding yourself on a 590.xx.xx version after unthinkingly updating.

You also may want to start thinking about updating to a newer GPU. I recently replaced my Quadro P400 with a RTX A400. The P400 will probably be supported for a year or more, but its time is running out. Eventually there won't be a diver that supports the card that can be compiled against a future Unraid kernel, or a change to the runtime code used in Docker containers may require a later Nvidia driver version.

17 minutes ago, ConnerVT said:

I'll give my input here, as ich777 is offline and it is after midnight at his house. I gave a short answer earlier, as I was unsure of the current behavior of the plugin code. If you scroll through the past few pages of this thread, you will see a number of people having issues after updating their driver after removed support for the Pascal cards in the 590.xx.xx drivers. ich777's response made it more clear how the plugin is handling it.

I would proceed like this:

• Select your current version (v580.82.09) in the Available Versions area of the Nvidia plugin (not Latest v580.82.09). Click UPDATE and DOWNLOAD. The plugin will check, see that it is already installed, and quickly give you the Done button.

• You can now update the Unraid OS

During the Unraid update, there is a Nvidia helper program that checks if an Nvidia driver is installed, and updates it if the driver version currently installed is one that is available for the Unraid version you are upgrading to (ich777 needs to recompile drivers for each kernel that Unraid uses). If the driver version is not available for that kernel, it updates to one that is. In the past, it updated to the "Latest" version. Worked great for a long time.

Then things got funny. The latest RTX 5xxx GPUs require the open source drivers. The Pascal cards now only work with the 580.xx.xx (and older) drivers. Looks as ich777 now added additional checks, so if you are on a 580.xx.xx driver, it will only update to the latest version of 580.xx.xx (and not 590.xx.xx, which won't work for the Quadro Pxxxx GPUs).

I think an Available Version is a good safety net to prevent accidentally finding yourself on a 590.xx.xx version after unthinkingly updating.

You also may want to start thinking about updating to a newer GPU. I recently replaced my Quadro P400 with a RTX A400. The P400 will probably be supported for a year or more, but its time is running out. Eventually there won't be a diver that supports the card that can be compiled against a future Unraid kernel, or a change to the runtime code used in Docker containers may require a later Nvidia driver version.

Hello,

Appreciate this feedback and attention to detail.

I proceeded as per your instruction's and selected the driver version manual/static - v580.82.09, which quickly prompted the Done button.

The context and additional information helped, thank you for taking to time to explain that.

Regarding the suggestion regarding considering a new GPU, replacing the current Quadro P2000. I appreciate you tossed the A400 in the hat, truthfully the P2000 was deployed strictly for transcoding, and wasn't locked or limited to how many sessions or transcodes it could do.

With that, I wouldn't know where to start with comparable replacement GPU and I am happy you mentioned the A400 as it gives me a baseline to go from and look at that card specifically or comparable models. I may circle back with some questions on that. (NVidia vs AMD)

Thank you again!

This plugin has been working fine for my Testa P40 and Quadro but the latest update seems to be broken. I removed the plugin, rebooted and reinstalled the plugin but it force installs the v490 driver instead of the v480. This results in the Nvidia plugin page hanging (requiring a phpfpm restart). Is there a way to manually install the v480 drivers?

4 hours ago, jserio said:

This results in the Nvidia plugin page hanging (requiring a phpfpm restart).

Do you possibly have two php errors on the page, if yes then you might suffer from a broken plugin, please follow this post:

Please note that the 480.x driver isn't available anymore, you have to choose driver version 580.x now for your Pascal based card (I would recommend to choose a static 580.x version since 590.x won't work for your card).

Brand new Unraid user here..be gentle.

Yesterday i setup the latest Unraid 7.2.3 on a PC, worked fine. I setup the attached RTX 4060TI with the nvidia driver app using latest 590 drivers and also the gpu statistics app. Everything worked fine. I powered down the server disconnected monitors and moved the box to another area headless and now when i check the driver i get NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

I get the same in terminal, I system devices i see the following..Where else can i look or what info can i provide. My nest step will be to reconnect the monito and see what that does..

PCI Devices and IOMMU Groups

IOMMU group 0:				[8086:1912] 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
				PCI Device change Action:Added VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
IOMMU group 1:				[8086:191f] 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
IOMMU group 2:				[8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07)
IOMMU group 3:				[8086:a12f] 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
				Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub
				Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub
				Bus 002 Device 002 Port 2-6 ID 18a5:0243 Verbatim, Ltd Flash Drive (Store'n'Go)
IOMMU group 4:				[8086:a13a] 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
IOMMU group 5:				[8086:a102] 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
				[1:0:0:0] disk ATA Samsung SSD 840 7B0Q /dev/sdb 250GB
				[2:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sdc 500GB
				[3:0:0:0] disk ATA Samsung SSD 850 4B6Q /dev/sdd 256GB
				[4:0:0:0] disk ATA Samsung SSD 850 2B6Q /dev/sde 500GB
				[5:0:0:0] disk ATA Samsung SSD 850 4B6Q /dev/sdf 256GB
IOMMU group 6:				[8086:a167] 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1)
IOMMU group 7:				[8086:a110] 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
IOMMU group 8:				[8086:a118] 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
IOMMU group 9:				[8086:a145] 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31)
				[8086:a121] 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
				[8086:a170] 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
				[8086:a123] 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
IOMMU group 10:				[8086:15b8] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
IOMMU group 11:				[1b21:1242] 03:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
				Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub
				Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub
IOMMU Removed:				[10de:2803] 01:00.0 VGA compatible controller: NVIDIA Corporation AD106 [GeForce RTX 4060 Ti] (rev a1)
				PCI Device change Action:Removed
IOMMU Removed:				[10de:22bd] 01:00.1 Audio device: NVIDIA Corporation AD106M High Definition Audio Controller (rev a1)
				PCI Device change Action:Removed

56 minutes ago, crazyc said:

Brand new Unraid user here..be gentle.

Please post your Diagnostics if you have hardware related questions (click on the "Diagnostics" texts if you don't know how to get them) and drag the zip file here into the textbox.

I will do this for you tomorrow, very late here. I will send two diagnostics as I got it to work by reconnecting the monitor so will send one of both if still having issues tomorrow

Edited February 2Feb 2 by crazyc

Okay tested this morning and can confirm working with Monitor Diagnostic attached and NOT working without monitor. I am wanting to use the graphics card for Immich and Unmanic..

Strangley after doing this test, monitor attached screen working and plugin working then disconnected monitor so no screen plugin not working. I have come accross issues booting after removing the monitor. Orginally this was due to Bios not remembereing Boot order so yesterday i disabled all except for the USB. It appears as if the grahics card locks sometimes when removing monitor for testing. System has been rock solid fo a few days with monitor connected. Waiting on dummy plug. @ich777 how do those logs look?

crazytower-with monitor-diagnostics-20260203-0736.zipcrazytower-without monitor-diagnostics-20260203-0741.zip

Edited February 4Feb 4 by crazyc

I (and others) over the years have seen Unraid not boot unless a monitor is plugged into a Nvidia card. Simple solution is to use a DisplayPort dummy plug. Less than $10 on Amazon.

48 minutes ago, ConnerVT said:

I (and others) over the years have seen Unraid not boot unless a monitor is plugged into a Nvidia card. Simple solution is to use a DisplayPort dummy plug. Less than $10 on Amazon.

Thanks for the heads up ConnerVT. I have ordered 1 for now..For many years I have run multiple QNAP's filled with the Arr's etc. This little venture in to Unraid is an experiment and a first for me, haqving fun for the most part. I am wanting to take the load of the QNAP's and process video files with Unmanic and photo fiels with Immich to begin.

On 2/2/2026 at 11:29 PM, crazyc said:

@ich777 how do those logs look?

Sorry, I think @ConnerVT already answered all questions, that's why I didn't looked at them.

Usually I only need Diagnostics to see what's going on.

Thanks for the hint with a connected display, didn't know that this was necessary for Nvidia too. :)

Reply, not a problem. I will report back when the dummy plug arrives

Is blackwell supposed to work? I just got a new card and it's not showing up. AI tells me blackwell isn't supported in unraid yet. Can someone confirm before I pull the card out?|||

FYI, error is:
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

I don't see the card anywhere in the device manager. Have tried reseating it, made sure 4g encoding and r-bar are enabled. Just confirmed it works in another PC.

6000 Pro Blackwell GPU

bertha-diagnostics-20260205-1437.zip

Edited February 5Feb 5 by samsausages

48 minutes ago, samsausages said:

Is blackwell supposed to work? I just got a new card and it's not showing up. AI tells me blackwell isn't supported in unraid yet. Can someone confirm before I pull the card out?|||

Sorry, but I don't see a Nvidia GPU in your system, at least that what's lspci tells me.

Hey folks. I keep having this reoccuring issue were my nvidia 5050 will fail to be recognized by the driver after a few days. I'm not sure what the cause is, this never happened before with my 1660. I have reinstalled the driver plugin a few times, as well as made sure that the open source driver is being used. I have attached diagnostics to this message, appreciate any help I can get.

dingleberry-diagnostics-20260205-1850.zip

6 hours ago, DingusKahn said:

Hey folks. I keep having this reoccuring issue were my nvidia 5050 will fail to be recognized by the driver after a few days. I'm not sure what the cause is, this never happened before with my 1660. I have reinstalled the driver plugin a few times, as well as made sure that the open source driver is being used. I have attached diagnostics to this message, appreciate any help I can get.

dingleberry-diagnostics-20260205-1850.zip

This is your error:

Feb 5 18:47:49 Dingleberry kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242

Feb 5 18:47:49 Dingleberry kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed

Feb 5 18:47:49 Dingleberry kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed

Feb 5 18:47:49 Dingleberry kernel: NVRM: osInitNvMapping: *** Cannot attach gpu

Feb 5 18:47:49 Dingleberry kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter

Feb 5 18:47:49 Dingleberry kernel: NVRM: GPU 0000:2b:00.0: RmInitAdapter failed! (0x22:0x51:763)

Feb 5 18:47:49 Dingleberry kernel: NVRM: GPU 0000:2b:00.0: rm_init_adapter failed, device minor number 0

Feb 5 18:47:52 Dingleberry kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from memdescAllocInternal(pMemDesc) @ memdesc.c:1359

Please make sure that you have:

1. The latest BIOS version

2. Above 4G Decding enabled in your BIOS

3. Resizable BAR Support enabled in your BIOS

I also compiled a new Open Source driver yesterday that you can try: v590.48.01

Hi everyone, 👋

I already talked about this problem on the Discord server, and they suggested that I open a post here.

My issue is the following: I recently installed my first GPU, an RTX A2000 Ada Gen with 16GB. When the Nvidia Driver Plugin is not installed, my CPU and RAM usage are completely normal.

However, as soon as I install the Nvidia Driver Plugin in order to use the GPU, my RAM usage almost doubles, and one CPU core is constantly at 100% usage. Overall CPU load also increases significantly.

lom-001-diagnostics-20260206-2222.zip

Important is I tested it for the latest and the 580. driver!

I would really appreciate any help with this issue.

Thank you!
🙏🏻 Nicalion

8 hours ago, Nicalion said:

I would really appreciate any help with this issue.

Please try to uninstall the GPU Statistics plugin and see if that resolves your issue.

GPU Statistics calls nvidia-smi every N seconds (depending on how it's configured in the plugin) and that could cause your CPU spikes.

I can't tell much about the RAM usage, however please do keep in mind that Unraid runs from RAM and the driver is also installed to RAM, compressed it has about 400MB so to speak that should be about 700 to 800MB decompressed if I'm not mistaken and that will also go into RAM.

On 2/1/2026 at 7:52 AM, ConnerVT said:

If you are still using the Quadro P2000 you will want to stay on 580.xx.xx. Nvidia has obsoleted the Pascal based cards and is removing support for them from 590.xx.xx.

Best to manually select a 580.xx.xx version (latest one is fine).

Thanks again for all the help.
Managed to grab a NVIDIA RTX A400 and was able to successfully install it today. Everything is working well and updated to the new OS using the v590.48.01 drivers.

Appreciate the recommendations and assistance from everyone including @ich777 should be a nice GPU change for the coming years.

On 2/1/2026 at 7:52 AM, ConnerVT said:

If you are still using the Quadro P2000 you will want to stay on 580.xx.xx. Nvidia has obsoleted the Pascal based cards and is removing support for them from 590.xx.xx.

Best to manually select a 580.xx.xx version (latest one is fine).

@ich777 I am facing the same issue where my server "forgets" my device (RTX 5060 Ti).

I already checked:

• Latest BIOS version installed

• "Above 4G Decoding" enabled

• "Resizable BAR Support" enabled

i updated the Open Source driver today to the new version: v590.48.01. if the problem persists i share my logs

1 hour ago, value1338 said:

i updated the Open Source driver today to the new version: v590.48.01. if the problem persists i share my logs

Please post your Diagnostics after your GPU is "forgotten".

Thanks for releasing Nvidia Driver Version: 590.48.01. No more nvidia error (NV_ERR_NO_MEMORY) and missing GPU (5070ti) when quitting Gaming Windows VM. So it's really a fix from drivers

Edited February 10Feb 10 by sausuke