Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] Nvidia-Driver

Featured Replies

Any one else that cant select older driver then 590 my ti1050 is supported to 580 not on 590.
When i push the update button i get a flash to select drivers but then it locks the page again.
Have tried to remove plugin remove from plugin history rebooted unraid.

14063.901043] nvidia-nvlink: Nvlink Core is being initialized, major device number 237

[14063.901051] NVRM: The NVIDIA NVIDIA GeForce GTX 1050 Ti GPU installed in this system is

NVRM: supported through the NVIDIA 580.xx Legacy drivers. Please

NVRM: visit http://www.nvidia.com/object/unix.html for more

NVRM: information. The 595.58.03 NVIDIA driver will ignore

NVRM: this GPU. Continuing probe...

  • Replies 5.9k
  • Views 1m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • To utilize your Nvidia graphics card in your Docker container(s) the basic steps are:   Add '--runtime=nvidia' in your Docker template in 'Extra Parameters' (you have to enable 'Advanced

  • Recompiled the drivers and they are now just working fine (to get it working scroll down):   Please do the following (this is only necessary if you upgraded before I recompiled the dri

  • I'm currently spinning up my build VM and compiling the drivers again, currently drivers for 6.11.0 stable are not available...

Posted Images

  • Author

Sorry for the inconvenience with the Nvidia Legacy Driver (580.x) and the new Unraid builds but it seems that Nvidia didn't update their page for the Legacy branch where the version numbers are pulled from and therefore the driver was never built for the new beta versions:

CleanShot 2026-04-02 at 11.47.08.png

However I've implemented a fix so that the correct driver versions are pulled now.

The compilation just started and the drivers will be available in the next 30 minutes for the new Unraid beta, please switch the driver version manually if you are already affected from this (upgrades from this point on won't have that issue).

5 hours ago, Nogami said:

Just tried 7.3 b2 and don't see a way of selecting v580.142 for my Quadro P600 card?

In Beta 2, the v580.142 is gone, no more support for GTX 1080 (

  • Author
1 minute ago, unRaiderX said:

In Beta 2, the v580.142 is gone, no more support for GTX 1080 (

Sorry but please read the post one above your post. :D

41 minutes ago, ich777 said:

Sorry for the inconvenience with the Nvidia Legacy Driver (580.x) and the new Unraid builds but it seems that Nvidia didn't update their page for the Legacy branch where the version numbers are pulled from and therefore the driver was never built for the new beta versions:

CleanShot 2026-04-02 at 11.47.08.png

However I've implemented a fix so that the correct driver versions are pulled now.

The compilation just started and the drivers will be available in the next 30 minutes for the new Unraid beta, please switch the driver version manually if you are already affected from this (upgrades from this point on won't have that issue).

Thank you very much @ich777
The 580.142 is back )

Edited by unRaiderX

I'm having an issue on the second beta with the driver plugin. Docker can't find the nvidia runtime, so Jellyfin will not start with it enabled. I have a Quadro P620, so I'm using 580.142. My GPU is detected just fine and is showing up in the plugin. I have rebooted a number of times at this point, including totally removing the driver plugin, rebooting, reinstalling, and rebooting again... none of that has helped.

Edited by hubleyku

@hubleyku I have the same problem on unraid 7.3.0-beta.2 using a Quatro p2000.

All the containers that have --runtime=nvidia give an error.

I am using driver version 580.142 and am considering trying to downgrade to 7.3.0-beta.1

I dont know if downgrading would help.

docker: Error response from daemon: unknown or invalid runtime name: nvidia

Update: downgraded to unraid 7.3.0-beta.1. It is now working again. Same driver version. I don't know if the drivers are specific to the Unraid version or if it is just a bug in beta2 or a setting that needs to be updated.

Edited by anthony0030
Adding update

It was an easy fix once I understood it. Just fall back to the appropriate driver. Why anyone would force the latest driver in such an update is a mystery. Honor what's there - or at least give us the option to retain the existing driver...

Edited by jeffreywhunter

2 hours ago, jeffreywhunter said:

It was an easy fix once I understood it. Just fall back to the appropriate driver. Why anyone would force the latest driver in such an update is a mystery. Honor what's there - or at least give us the option to retain the existing driver...

@jeffreywhunter Did you get it working on 7.3.0-beta.2? What GPU do you have?

  • Author
4 hours ago, hubleyku said:

I'm having an issue on the second beta with the driver plugin. Docker can't find the nvidia runtime, so Jellyfin will not start with it enabled. I have a Quadro P620, so I'm using 580.142. My GPU is detected just fine and is showing up in the plugin. I have rebooted a number of times at this point, including totally removing the driver plugin, rebooting, reinstalling, and rebooting again... none of that has helped.

Can you please post Diagnostics?

3 hours ago, anthony0030 said:

Update: downgraded to unraid 7.3.0-beta.1. It is now working again. Same driver version. I don't know if the drivers are specific to the Unraid version or if it is just a bug in beta2 or a setting that needs to be updated.

Cool, why wouldn't you post Diagnostics when you have issues? Is is pretty hard to troubleshoot if nothing is provided.

  • Author
9 hours ago, unRaiderX said:

Thank you very much @ich777
The 580.142 is back )

Just to double check, on your machine everything is working correct?

  • Author
2 hours ago, jeffreywhunter said:

It was an easy fix once I understood it. Just fall back to the appropriate driver. Why anyone would force the latest driver in such an update is a mystery. Honor what's there - or at least give us the option to retain the existing driver...

Sorry but this was my mistake as I explained in this post:

https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/226/#findComment-1616114

The existing driver will be kept if the 580.x driver version is selected but the driver was never compiled because Nvidia didn't update their documentation as explained above.

2 hours ago, ich777 said:

Can you please post Diagnostics?

Cool, why wouldn't you post Diagnostics when you have issues? Is is pretty hard to troubleshoot if nothing is provided.

I'm having the same issue.

Went through the upgrade to 7.3b2 and migrated to a spare nvme drive for booting. Everything appears to be functioning well.

Found Plex wouldn't start.

"docker: Error response from daemon: unknown or invalid runtime name: nvidia"

Thats odd. The nvidia driver is installed. Set to v580 for my 1050. I can see the GPU in the Dashboard via the GPU Statistics plugin.

Removed the nvidia variables and it starts AOK. So no immediate panic.

I updated the plugin, and re-selected v580. Plex starts now with the NVIDIA_VISIBLE_DEVICES and NVIDIA_DRIVER_CAPABILITIES both set to all.

However hardware transcoding isn't happening.

Attached are my diagnostics.

tower-diagnostics-20260402-1836.zip

Edited by djtodd

3 hours ago, djtodd said:

I'm having the same issue.

Went through the upgrade to 7.3b2 and migrated to a spare nvme drive for booting. Everything appears to be functioning well.

Found Plex wouldn't start.

"docker: Error response from daemon: unknown or invalid runtime name: nvidia"

Thats odd. The nvidia driver is installed. Set to v580 for my 1050. I can see the GPU in the Dashboard via the GPU Statistics plugin.

Removed the nvidia variables and it starts AOK. So no immediate panic.

I updated the plugin, and re-selected v580. Plex starts now with the NVIDIA_VISIBLE_DEVICES and NVIDIA_DRIVER_CAPABILITIES both set to all.

However hardware transcoding isn't happening.

Attached are my diagnostics.

tower-diagnostics-20260402-1836.zip

Same issue here.. Having --runtime=nvidia as an extra parameter returns an "invalid parameter" error.

Removing it allows the docker to start, but without hardware transcoding.

  • Author

@Nogami & @jeffreywhunter & @Per771 & @unRaiderX & @anthony0030 & @djtodd:

I've rebuilt the driver once more, if you are already on the new beta please remove the plugin, install it again, select the 580.x driver version and reboot.

If you are back on stable then please just upgrade and it should work right out of the box, granted you've selected driver version 580.x in the plugin.

5 hours ago, ich777 said:

@Nogami & @jeffreywhunter & @Per771 & @unRaiderX & @anthony0030 & @djtodd:

I've rebuilt the driver once more, if you are already on the new beta please remove the plugin, install it again, select the 580.x driver version and reboot.

If you are back on stable then please just upgrade and it should work right out of the box, granted you've selected driver version 580.x in the plugin.

OK, I removed the plugin, re-installed it, and made sure it was on v580. Rebooted.

Doesn't appear to have changed anything. HW transcoding still isn't happy.

I've included screen shots and diagnostics as well as my docker template, because hey, the problem could be me.

gpu.jpg

transcode.jpg

docker.jpg

tower-diagnostics-20260403-0816.zip

  • Author
1 hour ago, djtodd said:

Doesn't appear to have changed anything. HW transcoding still isn't happy.

Did the container start with --runtime=nvidia

If yes, then the issue lies somewhere else.

55 minutes ago, ich777 said:

Did the container start with --runtime=nvidia

If yes, then the issue lies somewhere else.

Yes, it's started with the --runtime=nvidia

I guess 7.3b2 somehow broke hardware transcoding.

FWIW, I opened a bug report. @anthony0030 you in particular might want to check/comment as you can roll back to b1, and I can't as I moved from 7.2.4

https://product.unraid.net/p/7-3b2-breaks-hardware-transcoding-in-plex?b=unraid-os-bugs

Edited by djtodd

  • Author
42 minutes ago, djtodd said:

I guess 7.3b2 somehow broke hardware transcoding.

I don't think that Unraid is the culprit here since I just tested it and with Jellyfin everything is working as expected.

1 hour ago, ich777 said:

I don't think that Unraid is the culprit here since I just tested it and with Jellyfin everything is working as expected.

I can confirm that the new driver works with beta 2. Jellyfin launches and transcodes work.

4 hours ago, djtodd said:

OK, I removed the plugin, re-installed it, and made sure it was on v580. Rebooted.

Doesn't appear to have changed anything. HW transcoding still isn't happy.

I've included screen shots and diagnostics as well as my docker template, because hey, the problem could be me.

gpu.jpg

transcode.jpg

docker.jpg

tower-diagnostics-20260403-0816.zip

Hi,

In your NVIDIA_VISIBLE_DEVICES you need to put your NVIDIA ID, found in the NVIDA setting, start with GPU-xxxxxx-xxxxx-xxx-xx-

3 hours ago, unRaiderX said:

Hi,

In your NVIDIA_VISIBLE_DEVICES you need to put your NVIDIA ID, found in the NVIDA setting, start with GPU-xxxxxx-xxxxx-xxx-xx-

I swear I'm not on drugs. Doesn't help. Switch anything to transcode and the CPU goes nuts.

I've tried an Android device, a Windows Plex app (not the web app), and various media sources. Most stuff direct plays of course, but when I force it to 720p (for example)

Screenshot 2026-04-03 164657.jpg

Screenshot 2026-04-03 170237.jpg

At any rate, I appreciate the help @ich777 . I'm not sure what I'm doing wrong, but we tried.

Like the responsible adult that I am I thought "This is incentive to build a new system on Intel hardware and get frustrated by QuickSync instead!" 😆

Upgraded to 7.3.0-beta.2 it’s working now!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.