23 hours ago, killercola said:

However, now when I try to reboot it goes to the boot gui and then the display is gets no signal and unraid does not launch.

Are you sure that it doesn't boot or do you see just a blinking cursor in the top left corner?

23 hours ago, killercola said:

I am able to get unraid to launch with my p2000 or with my p2000 and 5060ti. when I have both in they now show up for whatever reason. but I can't get it to boot with just the 5060ti.

Just to be clear, the OpenSource driver only supports GPUs RTX20 and up (including the GTX16 series) and the other drivers only supports up to RTX40 series.

So to speak you can't utilize both cards in your system, it's either you P2000 or your RTX5060ti.

I'm not sure what's going on with the boot issue since this seems very strange to me and usually has nothing to do with the Nvidia Driver.

From what I see from you Diagnostics, the RTX5060ti is properly recognized and should work, I see no other obvious issue.

If the card is dropping from the Bus then you can try to put nvidia-persistenced in your go file. Please also check that your Power Supply is up to the task since they degrade over time.

it goes to the boot gui and then the display says no signal and turns off. in about 5 min it will try again.

when using unraid 7.0 it would not detect the gpu driver. I'm going to try rolling the os back to 7.0 to see if that might fix things.

my intent is to only use the 5060 but until I can solve the boot issue I will have to keep the p2000

thanks for helping with what you can!

Edited December 3, 2025Dec 3 by killercola

ok looks like the boot issue was related to 7.2.2

but now I can't get it to detect the gpu.

uploading the new images and diagnostics. is it possible I just have a defective gpu?

Edited December 6, 2025Dec 6 by killercola

21 hours ago, killercola said:

but now I can't get it to detect the gpu.

Are you sure that Above 4G Decoding is enabled and Resizable BAR Support is enabled? You have a lot of these messages in your sysslog:

Dec 3 08:48:41 Tower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Dec 3 08:48:41 Tower kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:0c:00.0)

Dec 3 08:48:41 Tower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Dec 3 08:48:41 Tower kernel: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:0c:00.0)

and as a result from this message:

Dec 3 08:50:36 Tower kernel: NVRM: kbusVerifyBar2_GB202: MMUTest BAR0 window offset 0x70e000 returned garbage 0x0

Dec 3 08:50:36 Tower kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Generic memory error [NV_ERR_MEMORY_ERROR] (0x00000072) returned from kbusVerifyBar2_HAL(pGpu, pKernelBus, NULL, NULL, 0, 0) @ kern_bus_gm107.c:352

Dec 3 08:50:36 Tower kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Generic memory error [NV_ERR_MEMORY_ERROR] (0x00000072) returned from kbusStateInitLockedKernel_HAL(pGpu, pKernelBus) @ kern_bus_gm107.c:457

Dec 3 08:50:36 Tower kernel: NVRM: RmInitNvDevice: *** Cannot initialize the device

Dec 3 08:50:36 Tower kernel: NVRM: RmInitAdapter: RmInitNvDevice failed, bailing out of RmInitAdapter

Dec 3 08:50:36 Tower kernel: NVRM: rmapiReportLeakedDevices: Device object leak: (0xc1e00003, 0xcaf00000). Please file a bug against RM-core.

Dec 3 08:50:36 Tower kernel: NVRM: nvAssertFailedNoLog: Assertion failed: 0 @ rmapi.c:935

Dec 3 08:50:36 Tower kernel: NVRM: rmapiReportLeakedDevices: Device object leak: (0xc1e00004, 0xcaf00000). Please file a bug against RM-core.

Dec 3 08:50:36 Tower kernel: NVRM: nvAssertFailedNoLog: Assertion failed: 0 @ rmapi.c:935

Dec 3 08:50:36 Tower kernel: NVRM: nvAssertFailedNoLog: Assertion failed: listCount(&pKernelBus->virtualBar2[gfid].usedMapList) == 0 @ kern_bus_vbar2.c:346

Dec 3 08:50:36 Tower kernel: NVOC: __nvoc_objDelete: Child class KernelVideoEngine not freed from parent class OBJGPU.NVRM: iovaspaceDestruct_IMPL: 4 left-over mappings in IOVAS 0xc00

Dec 3 08:50:36 Tower kernel: NVRM: GPU 0000:0c:00.0: RmInitAdapter failed! (0x24:0x72:1100)

Dec 3 08:50:36 Tower kernel: NVRM: GPU 0000:0c:00.0: rm_init_adapter failed, device minor number 0

Dec 3 08:50:36 Tower kernel: NVRM: _kgspBootGspRm: unexpected WPR2 already up, cannot proceed with booting GSP

Dec 3 08:50:36 Tower kernel: NVRM: _kgspBootGspRm: (the GPU is likely in a bad state and may need to be reset)

Dec 3 08:50:36 Tower kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM

Dec 3 08:50:36 Tower kernel: NVRM: GPU 0000:0c:00.0: RmInitAdapter failed! (0x62:0x40:1860)

Dec 3 08:50:36 Tower kernel: NVRM: GPU 0000:0c:00.0: rm_init_adapter failed, device minor number 0

Hello everyone,

I'm having an issue with the latest driver version:

I tried to revert back to the older version, which was running (580.105.08), and my TeslaP4 is back up and running.

Is there some problem with the latest driver or what?

2 hours ago, TDA said:

I tried to revert back to the older version, which was running (580.105.08), and my TeslaP4 is back up and running.

Thank you for this. I updated my server to 7.2.2 yesterday and jellyfin kept failing saying it couldn't see the card. I tried changing the driver to the latest, and the open source and neither worked for me. After changing to the 580.105.08 driver, my 1050ti started working again.

9 hours ago, ich777 said:

Are you sure that Above 4G Decoding is enabled and Resizable BAR Support is enabled? You have a lot of these messages in your sysslog:

THANK YOU. That was the issue....

9 hours ago, Taubin said:

I tried changing the driver to the latest, and the open source and neither worked for me. After changing to the 580.105.08 driver, my 1050ti started working again.

11 hours ago, TDA said:

Is there some problem with the latest driver or what?

First of all, does anyone of you two have Diagnostics from where the issue occurred?

Otherwise it is really hard to troubleshoot.

You are talking about Driver version 590.44.01 correct (please also do keep in mind that this is a beta driver - latest is not always grates :D )?

Issue here is more the hardware that you are using, this is the first driver which is dropping everything before the first RTX series (Turing), so to speak Pascal and everything before is not supported anymore, please see (under the section Supported Products) :

https://www.nvidia.com/en-us/drivers/details/258750/

You now have to make sure that you stay below driver version 590

Hello-

I am also getting the "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running" error after upgrading my driver to 590.44.01 this morning. Any docker that uses the extra parameters "--runtime=nvidia" will no longer start. I've attached my diagnostics to hopefully troubleshoot the issue.

Thank you!

tower-diagnostics-20251205-0740.zip

25 minutes ago, LakersFan said:

Thank you!

Please read the post above yours and you have your answer (especially the last paragraph).

Thanks @ich777 . I initially read that post but thought it was a different issue. So I rolled it back and it works. Basically what you're saying though, is I'll no longer be able to update this particular GPU, right?

Just now, LakersFan said:

Basically what you're saying though, is I'll no longer be able to update this particular GPU, right?

It seems now that Nvidia made 10 series now legacy which basically means that you are stuck on driver version 580, however please keep in mind that Pascal so to speak 10 series cards are now almost 10 years old.

It's also clearly visible in the syslog:

Dec 5 07:26:34 Tower kernel: NVRM: The NVIDIA NVIDIA GeForce GTX 1060 6GB GPU installed in this system is

Dec 5 07:26:34 Tower kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please

Dec 5 07:26:34 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more

Dec 5 07:26:34 Tower kernel: NVRM: information. The 590.44.01 NVIDIA driver will ignore

Dec 5 07:26:34 Tower kernel: NVRM: this GPU. Continuing probe...

Dec 5 07:26:34 Tower kernel: NVRM: The NVIDIA NVIDIA GeForce GTX 1050 Ti GPU installed in this system is

Dec 5 07:26:34 Tower kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please

Dec 5 07:26:34 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more

Dec 5 07:26:34 Tower kernel: NVRM: information. The 590.44.01 NVIDIA driver will ignore

Dec 5 07:26:34 Tower kernel: NVRM: this GPU. Continuing probe...

Dec 5 07:26:34 Tower kernel: NVRM: No NVIDIA GPU found.

On 12/5/2025 at 9:08 PM, ich777 said:

It seems now that Nvidia made 10 series now legacy which basically means that you are stuck on driver version 580, however please keep in mind that Pascal so to speak 10 series cards are now almost 10 years old.

It's also clearly visible in the syslog:

Dec 5 07:26:34 Tower kernel: NVRM: The NVIDIA NVIDIA GeForce GTX 1060 6GB GPU installed in this system is

Dec 5 07:26:34 Tower kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please

Dec 5 07:26:34 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more

Dec 5 07:26:34 Tower kernel: NVRM: information. The 590.44.01 NVIDIA driver will ignore

Dec 5 07:26:34 Tower kernel: NVRM: this GPU. Continuing probe...

Dec 5 07:26:34 Tower kernel: NVRM: The NVIDIA NVIDIA GeForce GTX 1050 Ti GPU installed in this system is

Dec 5 07:26:34 Tower kernel: NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please

Dec 5 07:26:34 Tower kernel: NVRM: visit http://www.nvidia.com/object/unix.html for more

Dec 5 07:26:34 Tower kernel: NVRM: information. The 590.44.01 NVIDIA driver will ignore

Dec 5 07:26:34 Tower kernel: NVRM: this GPU. Continuing probe...

Dec 5 07:26:34 Tower kernel: NVRM: No NVIDIA GPU found.

is it fixed that you can set the driver version to a different , but the plugin will eventually switch back to "latest"?

I guess that would be annoying, untested (i also got the error with my 1050ti)

Edited December 8, 2025Dec 8 by NewDisplayName

4 minutes ago, NewDisplayName said:

I hope its fixed that you can change the driver version

Cool, didn't know that you can't change the driver version. :D

5 minutes ago, NewDisplayName said:

but the plugin will eventually switch back to "latest"?

For now yes because I haven't changed legacy versions, who knows what Nvidia does next and if they stick to that that driver 580 is now legacy but I will fix that eventually.

Hi - I've had a notification email a couple of times over the last few weeks saying...

Event: Nvidia Driver
Subject: Notification
Description: Found new Nvidia Driver v580.105.08 but a download error occurred! Please try to download the driver manually!
Importance: alert

However, v580.105.08 is the version I have installed. Whenever this happens, my log has several of these lines listed...

Dec  9 09:56:39 unRAID1 kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)
Dec  9 09:56:39 unRAID1 kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Dec  9 09:57:35 unRAID1 kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:884)
Dec  9 09:57:35 unRAID1 kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

And shortly after, if I go to the Nvidia driver page I get no cards found. Appreciated the GPU stats plugin is separate, but on the dashboard no cards listed (Vendor command returned unparseable data).

Sometimes it comes back, maybe bouncing on and off. I've rebooted and it's gone back to being stable for a while.

This is an A2000 (after upgrading from 1050ti), not used in VM, latest version of Unraid.

It's not catastrophic, but up until recently my machine's been pretty stable. Could easily be something I've left misconfigured though.

Thanks!

unraid1-diagnostics-20251209-0958.zip

2 minutes ago, Cessquill said:

Sometimes it comes back, maybe bouncing on and off. I've rebooted and it's gone back to being stable for a while.

This is a common issue with newer cards it seems.

Please try to add:

nvidia-persistenced

to your go file and reboot.

However most of the times it seems some kind of hardware compatibility issue.

Make sure your BIOS is up to date, you have Resizable BAR Support and above 4G Decoding enabled in your BIOS.

Check that you PSU is up to the task (please don't forget that PSUs degrade over time).

8 minutes ago, Cessquill said:

Hi - I've had a notification email a couple of times over the last few weeks saying...

This is a different issue and not related to the other issue.

Can you also please send a screenshot from your plugin page please.

3 minutes ago, ich777 said:

Can you also please send a screenshot from your plugin page please.

I'll add the line to my go file (can I put it in a user script on array start?).

I'll check the BIOS - pretty sure it's on the last update SuperMicro did but I'll check the settings. To be honest it's getting a little old and needs replacing, but that's a job for next year. The PSU should be up to it, but again, age...

Thank you for your time

6 minutes ago, Cessquill said:

I'll add the line to my go file (can I put it in a user script on array start?).

The command needs to be executed exactly once, when the server starts.

I would leave it in the go file.

Oh and please execute it once if you haven't rebooted yet. Few users said that this solved their issues.

22 hours ago, ich777 said:

The command needs to be executed exactly once, when the server starts.

I would leave it in the go file.

Oh and please execute it once if you haven't rebooted yet. Few users said that this solved their issues.

Command added to go file, BIOS confirmed to be up to date (2021), BIOS is up to date, above 4G Decoding enabled, but I do not have Resizable BAR Support available. Fingers crossed that buys a bit of time until a full system upgrade.

I will look at the PSU too since I added an extra drive a few weeks ago - might have tipped it over the edge 🤔

Thank you for your help again.

4 hours ago, Cessquill said:

I will look at the PSU too since I added an extra drive a few weeks ago - might have tipped it over the edge 🤔

Yeah, these new GPUs can produce pretty significant Power Spikes in your system and this could be one reason why the GPU falls from the bus and doesn't recover properly.

10 minutes ago, ich777 said:

Yeah, these new GPUs can produce pretty significant Power Spikes in your system and this could be one reason why the GPU falls from the bus and doesn't recover properly.

Good point, thank you. I've just checked - I've got a 920w power supply and it's powering 24 drives + parity + SSDs + GPU. If it was 920w new it could well be struggling.

It's a SuperMicro chassis, so not a regular PSU. I've just seen I can get a 1U 1280W supply that fits and is still part of their quiet range, so that might be worth a try (used prices are worth the risk).

EDIT: Used good condition 1200w supply - £24, just purchased. There's also 1400w, but they're still £250+

Edited December 10, 2025Dec 10 by Cessquill

I’m trying to get my GPU to work with Jellyfin.

While troubleshooting, I noticed that the GPU was detected at first. But as soon as I started Jellyfin and played a movie, the GPU disappeared. When I ran watch nvidia-smi in the Unraid terminal, it reported “no GPU.” After that, the GPU also disappeared from the Unraid NVIDIA plugin—it went from showing up normally to not being detected at all.

Dec 11 07:43:28 Happy2Me kernel: NVRM: Rate limiting GSP RPC error prints for GPU at PCI:0000:01:00 (printing 1 of every 30). The GPU likely needs to be reset.

Dec 11 07:45:24 Happy2Me kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0xffff:1740)

Dec 11 07:45:24 Happy2Me kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 11 07:45:24 Happy2Me kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2790)

Dec 11 07:45:24 Happy2Me kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Dec 11 07:45:26 Happy2Me kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x40:2790)

Its an GeForce GTX 1650

Edited December 10, 2025Dec 10 by tombstone

3 minutes ago, tombstone said:

Its an GeForce GTX 1650

I just briefly read a post in some thread that the newest nvidia driver dropped support for all 1x series cards. Or maybe it was just 10xx cards, can't remember exactly. But maybe you need to roll back to a previous driver? Check what cards your driver supports.

13 minutes ago, strike said:

I just briefly read a post in some thread that the newest nvidia driver dropped support for all 1x series cards. Or maybe it was just 10xx cards, can't remember exactly. But maybe you need to roll back to a previous driver? Check what cards your driver supports.

Thanks, but I just checked and it seems like it’s still supported, but the plugin is using the beta version?

7 hours ago, tombstone said:

But as soon as I started Jellyfin and played a movie, the GPU disappeared.

Please post your diagnostics.