On 7/2/2025 at 5:48 AM, ich777 said:

I think this is your issue:

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU at PCI:0000:02:00: GPU-257c8daf-576b-fa9e-c3c1-94f40e3e4347

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU Board Serial Number: 1422019097083

Jul 1 13:18:36 OrbitalHub kernel: NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU 0000:02:00.0: GPU has fallen off the bus.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: GPU 0000:02:00.0: GPU serial number is 1422019097083.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: A GPU crash dump has been created. If possible, please run

Jul 1 13:18:36 OrbitalHub kernel: NVRM: nvidia-bug-report.sh as root to collect this data before

Jul 1 13:18:36 OrbitalHub kernel: NVRM: the NVIDIA kernel module is unloaded.

Jul 1 13:18:36 OrbitalHub kernel: NVRM: Xid (PCI:0000:02:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)

However as you can see you even got a Xid error which you can learn more about here:

https://docs.nvidia.com/deploy/xid-errors/index.html#xid-error-listing

(in your Case you got Error 79)

Does this happen often for you or did this just happen for the first time? If this happened for the first time was this possibly during the Parity check or on the beginning from the Parity check?

If this happened during the Parity check for the first time make sure that your Power Supply is up to the task since such errors can happen at peaks where the Power Supply delivers power a bit too late or even to less which is required by the GPU.

Don't forget that power supplies also degrade over time.

Just because I saw it, please remove the file /boot/config/modprobe.d/nvidia.conf <- this isn't needed anymore, you also don't have the correct driver installed anyways.
You can also remove it by issuing this command from a Unraid Terminal:

rm -f /boot/config/modprobe.d/nvidia.conf

I am also getting this exact same issue this morning with my Tesla P4 (GP104GL). The only change was updating Unraid to 7.1.4.

Nvidia Info:

Nvidia Driver Version: 575.64.05

Open Source Kernel Module: No

Installed GPU(s):
0:
Tesla P4
01:00.0
GPU-1452e99e-5e98-1d02-48fa-434f381c4ea3

The plugin has no issues seeing the card, and Plex is configured to correctly detect it and use it. When Plex starts using it to transcode, the stream will eventually fail when it gets the "off the bus" error and will lock up the Plex docker.

I initially thought it was because I needed to update the Nvidia Driver Version to the latest (previously it was on v575.57.08).

Prior to the 7.1.4 upgrade, no issues transcoding or streaming (usually 4+ streams at once) and had about 30 days uptime. I've tested it with just the Plex docker running and nothing else and it still throws this error.

Aug 3 13:36:30 plex2 kernel: NVRM: GPU at PCI:0000:01:00: GPU-1452e99e-5e98-1d02-48fa-434f381c4ea3

Aug 3 13:36:30 plex2 kernel: NVRM: GPU Board Serial Number: 0421519083008

Aug 3 13:36:30 plex2 kernel: NVRM: Xid (PCI:0000:01:00): 79, GPU has fallen off the bus.

Aug 3 13:36:30 plex2 kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.

Aug 3 13:36:30 plex2 kernel: NVRM: GPU 0000:01:00.0: GPU serial number is 0421519083008.

Aug 3 13:36:30 plex2 kernel: NVRM: A GPU crash dump has been created. If possible, please run

Aug 3 13:36:30 plex2 kernel: NVRM: nvidia-bug-report.sh as root to collect this data before

Aug 3 13:36:30 plex2 kernel: NVRM: the NVIDIA kernel module is unloaded.

Aug 3 13:36:30 plex2 kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)

Was hoping it was an issue where I could just roll back to a previous driver version and not have to revert the Unraid update.

On 8/3/2025 at 2:43 AM, simmo said:

I mentioned at the bottom of my post that I can't run diagnostics with the P4000 and the nvidia driver installed as it calls nvidia-smi and so locks up the process. I have attached a new diagnostics.zip with the P4000 installed but without the nvidia drivers.

Okay, issue with those old drivers (series 535) is that they don't compile against newer Kernels which Unraid uses.

However you are now running the nouveau driver, I assume because of nvidia-smi:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104GL [Quadro P4000] [10de:1bb1] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:11a3]

Kernel modules: nouveau

01:00.1 Audio device [0403]: NVIDIA Corporation GP104 High Definition Audio Controller [10de:10f0] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:11a3]

02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106GL [Quadro P2200] [10de:1c31] (rev a1)

Subsystem: Hewlett-Packard Company Device [103c:131b]

Kernel modules: nouveau

02:00.1 Audio device [0403]: NVIDIA Corporation GP106 High Definition Audio Controller [10de:10f1] (rev a1)

Subsystem: Hewlett-Packard Company Device [103c:131b]

On 8/3/2025 at 2:43 AM, simmo said:

In fact, Deepseek-r1 running on ollama on the P4000 tells me that the minimum CPU requirement for the P4000 is a 4th gen or better i5 (Haswell or better). I'm using an i5-3450 which is 3rd gen (Ivy Bridge). Could this be true? I can't find this requirement in any of the NVIDIA documentation.

Possible, some applications need newer instruction sets which these old CPUs doesn't support anymore.

However from what I know a P4000 should work just fine even with the latest driver which is available in the plugin.

20 hours ago, ThESoul said:

Any help is appreciated!

Sorry, without Diagnostics I can't help.

14 hours ago, haincito said:

I wanted to ask if any of you know about the driver support for an Nvidia Quadro P4000 so you can use it for transcoding with this plugin. I've the opportunity to buy this GPU for 100€ and I was wondering if it'll be worth the money and if it'll work properly.

Yes, but keep in mind when the driver version v580 is released they will drop support for Pascal which is the P4000 based on.

I would rather recommend that you get something future proof like the Nvidia T400/T600/T1000 (Turing based an now also a few years old) or you look into a Nvidia A400 (Ada based).

For a few simultaneous h265 main streams theses cards should be more than enough.

10 hours ago, zanetheinsane said:

Aug 3 13:36:30 plex2 kernel: NVRM: Xid (PCI:0000:01:00): 154, GPU recovery action changed from 0x0 (None) to 0x1 (GPU Reset Required)

It seems that your GPU needs to be reset since you got XID error 154 however I really can't tell what causes the issue, you can try to downgrade to the previous version from Unraid and see if you are experiencing the same issue.

However what you can try first is:

1. Update the BIOS, if a BIOS update is available

2. Check if ResizableBAR support is enabled in your BIOS

3. Check if Above 4G Decoding is enabled in your BIOS

You can learn more about XID errors here: Click

10 hours ago, zanetheinsane said:

Was hoping it was an issue where I could just roll back to a previous driver version and not have to revert the Unraid update.

Please always include Diagnostics in hardware issue posts.

1 hour ago, ich777 said:

Sorry, without Diagnostics I can't help.

Apologies i should have included these from the start:
ThESoul - Diagnostics.zip

I have also tried the GPU in a different PCIE slot, BIOS updates, reinstalling the drivers more times than i can count.

1 hour ago, ich777 said:

However from what I know a P4000 should work just fine even with the latest driver which is available in the plugin.

@ich777 thanks again for all your help.

With a bit more digging I have found that the card doesn't actually work with the 535 drivers either. nvidia-smi doesn't freeze (like it does with the newer drivers), but it does give "Unknown Error" results for some of the GPU power and clock readings. I even installed an older version of Ubuntu so I could try the 470 drivers and they give the same error results. So it looks like the card is faulty as you suggested.

I have attached the output of "nvidia-smi --query" just in case anyone is interested.

nvidia-smi-535.txt

1 hour ago, ThESoul said:

I have also tried the GPU in a different PCIE slot, BIOS updates, reinstalling the drivers more times than i can count.

First of all I would recommend that you upgrade to 7.1.4

On 8/3/2025 at 11:52 AM, ThESoul said:

GTX 1050 TI

Sorry that I have to say that but it seems like you have a counterfeit card on hand:

Aug 3 19:03:07 HomeServer kernel: NVRM: The Unknown NVIDIA GF1xx Series GPU installed in this

You usually can easily spot that here:

05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:0000]

Kernel modules: nouveau, nvidia_drm, nvidia

05:00.1 Audio device [0403]: NVIDIA Corporation GF116 High Definition Audio Controller [10de:0bee] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:0000]

The fist PCI device (05:00.0) is your GPU, which is listed as a GP107 (Pascal) with a changed vBIOS it seems, however the second device that you can see above (05:00.1) is the Audio Device from that card where you can see that it's a GF116 which basically means it's Fermi 2.0 based which is not supported anymore: Click <- this is often times the main indication since only the GPU is changed but not the Audio Controller.

34 minutes ago, ich777 said:

First of all I would recommend that you upgrade to 7.1.4

Sorry that I have to say that but it seems like you have a counterfeit card on hand:

Aug 3 19:03:07 HomeServer kernel: NVRM: The Unknown NVIDIA GF1xx Series GPU installed in this

You usually can easily spot that here:

05:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:0000]

Kernel modules: nouveau, nvidia_drm, nvidia

05:00.1 Audio device [0403]: NVIDIA Corporation GF116 High Definition Audio Controller [10de:0bee] (rev a1)

Subsystem: NVIDIA Corporation Device [10de:0000]

The fist PCI device (05:00.0) is your GPU, which is listed as a GP107 (Pascal) with a changed vBIOS it seems, however the second device that you can see above (05:00.1) is the Audio Device from that card where you can see that it's a GF116 which basically means it's Fermi 2.0 based which is not supported anymore: Click <- this is often times the main indication since only the GPU is changed but not the Audio Controller.

Interesting ok thank you, sucks to hear but i guess i will look at getting a new GPU for media transcoding.

Is there any entry level GPU you would reccomend for this? looking to mainly just do 1440P with the occasional 4k stream.

1 hour ago, ThESoul said:

Interesting ok thank you, sucks to hear but i guess i will look at getting a new GPU for media transcoding.

Is there any entry level GPU you would reccomend for this? looking to mainly just do 1440P with the occasional 4k stream.

Please look at that post:
https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/202/#findComment-1571235

5 hours ago, ich777 said:

I would rather recommend that you get something future proof like the Nvidia T400/T600/T1000 (Turing based an now also a few years old) or you look into a Nvidia A400 (Ada based).

I just did a quick search, and it looks as the prices for A400 have dropped to about the same as T400 here in the US. Something to keep an eye on moving forward.

On 7/29/2025 at 10:58 AM, musicking said:

Still showing problems :(

Well, after way too many hours, I think my card is failing.

Purchased an Intel ARC a380 for transcoding and hopefully won't see anymore issues with "no devices found".

7 hours ago, musicking said:

Well, after way too many hours, I think my card is failing.

Thanks for the Update, however sad to hear that it is failing.

However the ARC A380 is a good choice for transcoding but not for power draw. Otherwise a Nvidia T400, T600, T1000 or even better a Nvidia A400 would be good choice.

On 7/12/2025 at 4:40 AM, micka said:

Ah yes, forgot i added this to test without GSP earlier.( same issue without it though )

Yeah well, after looking on github's issues it seems like it is related to power state, some users are reporting kinda similar issues.

Looks like there is a patch you can build (https://github.com/NVIDIA/open-gpu-kernel-modules/commit/c7e72135da83ff027755b4a61a3ff09a32fe00c3) but the drawback is you don't have eco mode anymore and you draw more power at idle.
I'll keep looking at github, thanks for the help guys ^^

also been seeing these errors & warnings, also using a 5060 Ti:

Aug  7 19:10:01 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from _memdescAllocInternal(pMemDesc) @ mem_desc.c:1353
Aug  7 19:10:01 Thermaltake kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615
Aug  7 19:10:01 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502
Aug  7 19:10:01 Thermaltake kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image
Aug  7 19:10:01 Thermaltake kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM
Aug  7 19:10:01 Thermaltake kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)
Aug  7 19:10:01 Thermaltake kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from _memdescAllocInternal(pMemDesc) @ mem_desc.c:1353
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242
Aug  7 19:10:30 Thermaltake kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
Aug  7 19:10:30 Thermaltake kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:742)
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from _memdescAllocInternal(pMemDesc) @ mem_desc.c:1353
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242
Aug  7 19:10:30 Thermaltake kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
Aug  7 19:10:30 Thermaltake kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:742)
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Edited August 16, 2025Aug 16 by Kitoro
atch

19 minutes ago, Kitoro said:

also been seeing these errors & warnings, also using a 5060 Ti:

Please update your BIOS, you are running a beta BIOS and there is already a newer BIOS version available, after that make sure to enable Above 4G Decoding and Resizable BAR Support.

19 hours ago, Kitoro said:

also been seeing these errors & warnings, also using a 5060 Ti:

Aug  7 19:10:01 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from _memdescAllocInternal(pMemDesc) @ mem_desc.c:1353
Aug  7 19:10:01 Thermaltake kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from status @ kernel_gsp.c:4615
Aug  7 19:10:01 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from kgspCreateRadix3(pGpu, pKernelGsp, &pKernelGsp->pGspUCodeRadix3Descriptor, NULL, pGspFw->pImageData, pGspFw->imageSize) @ kernel_gsp.c:4502
Aug  7 19:10:01 Thermaltake kernel: NVRM: kgspInitRm_IMPL: Error preparing GSP-RM image
Aug  7 19:10:01 Thermaltake kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM
Aug  7 19:10:01 Thermaltake kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x51:1941)
Aug  7 19:10:01 Thermaltake kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from _memdescAllocInternal(pMemDesc) @ mem_desc.c:1353
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242
Aug  7 19:10:30 Thermaltake kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
Aug  7 19:10:30 Thermaltake kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:742)
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvCheckOkFailedNoLog: Check failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from _memdescAllocInternal(pMemDesc) @ mem_desc.c:1353
Aug  7 19:10:30 Thermaltake kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from nvStatus @ message_queue_cpu.c:242
Aug  7 19:10:30 Thermaltake kernel: NVRM: _kgspInitRpcInfrastructure: GspMsgQueueInit failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: kgspConstructEngine_IMPL: init RPC infrastructure failed
Aug  7 19:10:30 Thermaltake kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
Aug  7 19:10:30 Thermaltake kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x51:742)
Aug  7 19:10:30 Thermaltake kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

thermaltake-diagnostics-20250807-2013.zip

Hello,
I tried with another GPU ( 1660 TI ) and i seem to get the same error on 575.57.08.
The 1660 TI is working properly when using closed blob.
Could it be related to this driver version ?

41 minutes ago, micka said:

Could it be related to this driver version ?

I don‘t think so because otherwise more users would report that issue.

About 10 users reported issues from about 8k downloads so I assume this is a hardware incompatibility or another hardware related issue for these users.

The thing is i keep finding issues related to this with no fix whatsoever , if someone was able to make it work they would probably tell us at some point no ?
I found this reddit as well : https://www.reddit.com/r/unRAID/comments/1k69ufy/rtx_50_series_cards_and_unraid_issues/?tl=fr
Because i can install the open blob driver successfully, nvidia-smi will work, but as soon as i'm trying to use GSP related features ( such as encoding, decoding etc ... ) the GPU won't work.

8k downloads on the open blob driver ?
Were you able to try the open blob driver ?

1 hour ago, micka said:

Were you able to try the open blob driver ?

im using this driver

and can confirm, ffmpeg decode, encode works fine here ...

also paathrough to VM works fine which doesnt belong to this driver plugin now, just to confirm, all fine here at least ...

Just now, alturismo said:

im using this driver

and can confirm, ffmpeg decode, encode works fine here ...

also paathrough to VM works fine which doesnt belong to this driver plugin now, just to confirm, all fine here at least ...

The driver version differ from what i got, i'm using the 575.57.08 :

That is the option i got for the 1660 TI and the 5060

1 hour ago, micka said:

Were you able to try the open blob driver ?

On the open source version for Unraid 7.1.4 there are of course fewer downloads but there are about combined 1.5k downloads:

name: 6.12.24-Unraid,

name: nvidia-565.77-6.12.24-Unraid-1.txz,

download_count: 645,

name: nvidia-570.144-6.12.24-Unraid-1.txz,

download_count: 1657,

name: nvidia-570.153.02-6.12.24-Unraid-1.txz,

download_count: 2176,

name: nvidia-570.169-6.12.24-Unraid-1.txz,

download_count: 2199,

name: nvidia-570.172.08-6.12.24-Unraid-1.txz,

download_count: 1933,

name: nvidia-570.181-6.12.24-Unraid-1.txz,

download_count: 1044,

name: nvidia-575.51.02-6.12.24-Unraid-1.txz,

download_count: 14675,

name: nvidia-575.57.08-6.12.24-Unraid-1.txz,

download_count: 10183,

name: nvidia-575.64-6.12.24-Unraid-1.txz,

download_count: 8852,

name: nvidia-575.64.03-6.12.24-Unraid-1.txz,

download_count: 10937,

name: nvidia-575.64.05-6.12.24-Unraid-1.txz,

download_count: 8365,

name: nvidia-580.65.06-6.12.24-Unraid-1.txz,

download_count: 4722,

name: nvos-570.144-6.12.24-Unraid-1.txz,

download_count: 684,

name: nvos-575.57.08-6.12.24-Unraid-1.txz,

download_count: 828,

(the last two who are starting with the name "nvos-")

2 minutes ago, micka said:

The driver version differ from what i got, i'm using the 575.57.08 :

I assume you are not on Unraid 7.2 beta series correct?

3 minutes ago, micka said:

The driver version differ from what i got, i'm using the 575.57.08 :

im using it always here ... so basically never had any issues here, same before, same now with my 5080 since beginning june

sample from encode, pretty fast also ...

3 hours ago, ich777 said:

I assume you are not on Unraid 7.2 beta series correct?

No but i can try it, i was wondering if the new linux kernel would help ( or if the nvidia plugin was any different in that Unraid version )

3 hours ago, alturismo said:

im using it always here ... so basically never had any issues here, same before, same now with my 5080 since beginning june

I think the plugin suggests the version based on your GPU and since the RTX 5080 was released before the 5060 i think it's normal behaviour (don't know why i got the same version for the 1660 TI though).
The thing is i got an RTX 5080 i could put in but i got to get it out of my rig and it would be complicated ( not a regular PC case ) so i'd rather solve it without testing it ^^"

The same driver as @alturismo appear as closed blob to me but it's working properly

41 minutes ago, micka said:

or if the nvidia plugin was any different in that Unraid version

No.

8 minutes ago, micka said:

The same driver as @alturismo appear as closed blob to me but it's working properly

The closed source driver branch will not work with 50 series cards, if you are using a 50series card then you have to use the open source branch.

Your 1660Ti won‘t work with the open source branch, only the proprietary driver will work with the 1660Ti since it’s Pascal based.