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

7 minutes ago, ich777 said:

But this then seems more like a Plex issue than a driver issue.

 

If the card is recognized on the plugin page it should be working.

 

What input material are you trying to transcode? Do you use the Plex webclient to force a transcode, it is know that there is an issue and transcodig isn‘t working there.

Also see this post and a few above:

 

I've been trying to transcode 4k to 1080 on the android app, the samsung tv app and web client. Even straight 4k original on my home network it would pass that to the GPU to deal with but all bottlenecked at CPU now, no GPU usage.

  • Replies 5.9k
  • Views 1.2m
  • 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
26 minutes ago, thelostnorthman said:

no GPU usage.

What does the Plex transcoding log say, what variables habe you passed through in the Plex template? Did you do it like mentioned in the second post or did you use another variable, Extra Parameter?

I have the Nvidia Quadro K4000 graphics card.

When I try to install the latest from the plugin, I get this error:

 

image.thumb.png.db4f2e5d9bf3045a48e9de115d595368.png

 

The Nvidia drivers page points me to this driver for Linux 64bit which is fairly recent (March 2023)

image.thumb.png.af8bc736616f665a9d6e8970af56b978.png

image.thumb.png.dca179b6ff22121f6929a3b392fbfb01.png

 

However, when I use the plugin, the only 470.xxx one that it provides is the one at the bottom: v470.141.03

image.thumb.png.4d52eae46136f6bcefad70adcf4e3755.png

I want to be able to use this card with Docker for apps that use the "--runtime=nvidia" parameter like stable-diffusion etc. that detect the NVIDIA GPU and ask for its GPUID e.g. GPU-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxx.

 

Is this something that can be supported?

 

 

 

 

 

Edited by frakman1

  • Author
1 hour ago, frakman1 said:

When I try to install the latest from the plugin, I get this error:

Without the Diagnostics I can't say anything. It is most likely the case that there is something else preventing the card from showing up.

 

1 hour ago, frakman1 said:

However, when I use the plugin, the only 470.xxx one that it provides is the one at the bottom: v470.141.03

This is still the same driver...

3 hours ago, ich777 said:

This is still the same driver...

Thanks. I will try and get some logs but it's good to know which driver to use now.

 

  • Author
1 hour ago, frakman1 said:

Thanks. I will try and get some logs but it's good to know which driver to use now.

 

Please post your Diagnostics so that I can tell what‘s going on, you can also send them via PM if you feel more comfortable that way.

Are there any issues with unraid 6.12.1?

  • Author
5 minutes ago, enJOyIT said:

Are there any issues with unraid 6.12.1?

Not that I‘m aware of, what issues are you talking about?

If you are ecperiencing issues, please always include your Diagnostics.

 

6.12.1 is in terms of the Nvidia Driver plugin the same as 6.12.0

I just posted here: 

 

 

At bootup it's telling me that the nvidia package seems to be corrupt. How can I redownload the driver?

 

Ah, I think I have to wait until the redownload is finished 🙂 I didn't read the whole message after Checksum error 🙂

 

Should there be a "porgress bar" while downloading? --> No, it's finished now...

 

Rebooted and it's working again.

 

Thank you 😄

Edited by enJOyIT

  • Author
55 minutes ago, enJOyIT said:

I just posted here: 

This is a plugin and you should always use the support thread because strictly speaking Limetech has nothing to do with it.

 

55 minutes ago, enJOyIT said:

At bootup it's telling me that the nvidia package seems to be corrupt. How can I redownload the driver?

Did you waited with the reboot until the Plugin-Update-Helper told you it is safe to reboot?

 

55 minutes ago, enJOyIT said:

Ah, I think I have to wait until the redownload is finished 🙂 I didn't read the whole message after Checksum error 🙂

After the download finished it should have told you just to reboot.

 

55 minutes ago, enJOyIT said:

Should there be a "porgress bar" while downloading? --> No, it's finished now...

No, it tells you to wait until the Done button appears and that you should not close this window.

 

 

Glad that it is now working again, please always read the dialogues. :)

Hi there!

 

After the latest update of the plugin including an update of Unraid to 6.12.1 and the latest nvidia driver, it seems my graphics card no longer shows up. 

 

Keeps displaying the driver as being corrupt on the boot screen, even after multiple re-installs, re-downloads of various driver versions and reboots - without any success.

 

I don't have any Adguard or the like on my home network.

 

Worth noting I have also reinstalled Unraid on my USB flash drive, only keeping the config folder.

 

Hope someone can help me narrow down my problem :)

tower-diagnostics-20230621-1834.zip

  • Author
5 minutes ago, Olitrolli said:

Keeps displaying the driver as being corrupt

Where does it say this, do you have a screenshot please?

The driver size seems correct to me and I don't think the checksum is wrong.

 

Have you yet tried just to reboot after verifying the checksums? From what I can tell from your syslog it wasn't downloaded and installed later on in the boot process.

9 minutes ago, ich777 said:

Where does it say this, do you have a screenshot please?

The driver size seems correct to me and I don't think the checksum is wrong.

 

Have you yet tried just to reboot after verifying the checksums? From what I can tell from your syslog it wasn't downloaded and installed later on in the boot process.

This is the response I get:

FATAL: Module nvidia not found in directory /lib/modules.....

 

I deleted the plugin. Went to download it again and now it won't let me download it.

 

Just rebooted the system as well and same response :-((

 

1389737302_Screenshot2023-06-21at19_14_48.thumb.png.40b34fc6fe02560367ffc7cccc71256c.png

Okay. So through the power of rebooting again again I managed to download the plugin and get confirmation that the driver had been installed. I pressed the "done" button and went for another reboot to finalize the install.

 

This is what the plugin displays once booted into Unraid.

 

 

Screenshot 2023-06-21 at 19.32.55.png

  • Author
40 minutes ago, Olitrolli said:

I deleted the plugin. Went to download it again and now it won't let me download it.

 

Just rebooted the system as well and same response :-((

The usual way is that you remove the plugin, then reboot and then reinstall the plugin again and reboot again.

 

30 minutes ago, Olitrolli said:

This is what the plugin displays once booted into Unraid.

Please post your Diagnostics, this is completely different from before.

So the Unraid UI froze and crashed before I was able to download the diagnostics and I was forced to reboot once again.

 

 

I managed to take a picture of the boot which might point us in the direction of the problem.

 

The "NVIDIA-SMI..." no longer shows up in the plugin after having logged back in.

 

Again, really appreciate the help here:)

 

signal-2023-06-21-205507_002.thumb.jpeg.075074444214bcc417756651f135f903.jpeg

Screenshot 2023-06-21 at 20.59.37.png

tower-diagnostics-20230621-2056.zip

  • Author
1 hour ago, Olitrolli said:

Again, really appreciate the help here:)

These Diagnostics are the same as before, the driver did not install for whatever reason on your system even if it tells it in the syslog.

The message on boot just tells you that the driver package did not install

 

I need the Diagnostics when the plugin reports that "nvidia-smi is not able..."

 

Do the following:

  1. Uninstall the plugin
  2. Reboot
  3. Pull a fresh copy from the plugin from the CA App
  4. Reboot
  5. The plugin should report that nvidia-smi failed -> pull the Diagnostics imitatively and post them here

 

Did you change anything in the BIOS, did you maybe do a BIOS update or anything similar, was it always the case that you've booted into UEFI instead of Legacy mode?

Please check also if you have C-States in the BIOS disabled -> this causes mostly issues with Nvidia cards.

36 minutes ago, ich777 said:

These Diagnostics are the same as before, the driver did not install for whatever reason on your system even if it tells it in the syslog.

The message on boot just tells you that the driver package did not install

 

I need the Diagnostics when the plugin reports that "nvidia-smi is not able..."

 

Do the following:

  1. Uninstall the plugin
  2. Reboot
  3. Pull a fresh copy from the plugin from the CA App
  4. Reboot
  5. The plugin should report that nvidia-smi failed -> pull the Diagnostics imitatively and post them here

 

Did you change anything in the BIOS, did you maybe do a BIOS update or anything similar, was it always the case that you've booted into UEFI instead of Legacy mode?

Please check also if you have C-States in the BIOS disabled -> this causes mostly issues with Nvidia cards.

 

Okay! So I replicated the nvidia-smi fail scenario and attached the diagnostics below.

 

No I haven't changed any BIOS settings recently and have always booted into UEFI. Would you recommend booting in Legacy mode instead?

 

Will check C-states in BIOS when I get home but haven't touched or had any problems with it before :-/

Screenshot 2023-06-21 at 22.58.50.png

tower-diagnostics-20230621-2259.zip

  • Author
8 hours ago, Olitrolli said:

Okay! So I replicated the nvidia-smi fail scenario and attached the diagnostics below.

I have to look into that issue when I got home from work.

 

It is really strange to me since another user on 6.12.1 is utilizing the driver just fine:

 

8 hours ago, Olitrolli said:

No I haven't changed any BIOS settings recently and have always booted into UEFI. Would you recommend booting in Legacy mode instead?

With the Nvidia Driver yes, however if you haven't experienced any issues so far then it should work on 6.12.1 also just fine.

 

8 hours ago, Olitrolli said:

Will check C-states in BIOS when I get home but haven't touched or had any problems with it before 😕

Most AMD users have to disable C-States so that the card can work properly.

 

I think something else is going on on your system but I can't tell for sure what.

 

BTW just because I noticed it, don't switch between various driver version since this won't magically solve your issue, stick to the latest one by switching it makes diagnosing the issue much harder for me.

 

What is the device 0000:07:00.0 in your system and why did you bind it to VFIO? If all of that doesn't help can you try to downgrade to 6.12.0 and see if that fixes the issue?

 

I've also now took a quick look how often driver version 535.54.03 was downloaded and as of time of writing it was downloaded about 2000 times, so I'm assuming it is working fine since otherwise I would have many reports that the driver isn't working.

13 hours ago, ich777 said:

I have to look into that issue when I got home from work.

 

It is really strange to me since another user on 6.12.1 is utilizing the driver just fine:

 

With the Nvidia Driver yes, however if you haven't experienced any issues so far then it should work on 6.12.1 also just fine.

 

Most AMD users have to disable C-States so that the card can work properly.

 

I think something else is going on on your system but I can't tell for sure what.

 

BTW just because I noticed it, don't switch between various driver version since this won't magically solve your issue, stick to the latest one by switching it makes diagnosing the issue much harder for me.

 

What is the device 0000:07:00.0 in your system and why did you bind it to VFIO? If all of that doesn't help can you try to downgrade to 6.12.0 and see if that fixes the issue?

 

I've also now took a quick look how often driver version 535.54.03 was downloaded and as of time of writing it was downloaded about 2000 times, so I'm assuming it is working fine since otherwise I would have many reports that the driver isn't working.

 

So I re-seated the graphics card and disabled C-states in the BIOS and boom! No more "corrupted" driver.

 

Before that I had even tried to reinstall Unraid on an entirely new and formatted USB flash drive with same results.

 

I have never touched the C-state BIOS option prior - weird if that had turned into a problem all of a sudden.

 

Thank you so much @ich777!:D

 

I really want to support you for the help you do for this community. Is sponsoring you on Github the right place to go? 

hello every, i'm a new guy from china for unraid.

Formly i got a nvidia CMP 40HX mining card, it composed by specially TU-106 chip with 8GB GDDR6, and modified to support PCIE1.1 x16 by the seller.

that's interesting to use it run games & beachmark at windows platform.

but now i wonder to install it to my unraid server for  AI / CUDA computing (like hashcat docker and etc), but didn't work.

all drivers of the plugin ''nvidia driver'' has didn't identifing this card. there's no any info of this card in plugin interface, 

I'm trying to search this problem in google, the other Linux OP like Ubuntu、PVE can manual install correct driver by apt-get, but unraid can't do it like that. 

so could you have any plan to add a correct driver? all i just known the 460~490 of offical version and some open source of third party is available.

all thx!

 

Edited by bdm965

  • Author
9 hours ago, bdm965 said:

nvidia CMP 40HX mining card

I don't know that card but I know such cards exist.

 

9 hours ago, bdm965 said:

all i just known the 460~490 of offical version and some open source of third party is available.

What is the correct driver? You can install the legacy driver 470.xx in the plugin and of course the latest ones.

 

If the driver is not publicly available from Nvidia I can't help here because this would violate their EULA.

Hi,

 

have a supported card (quadro K4000 - Latest Legacy GPU version (470.xx series): 470.182.03) that works and followed the instructions re: docker off/on/reboot etc. Card wasn't bound, but tried binding/rebooting then unbinding/rebooting just to be sure.

 

Still the plug-in doesn't recognise it.

 

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

 

Attached diagnotics (followed your steps from a post on the previous page of this thread re: uninstall/reboot/reinstall/reboot/c-state off/switched to legacy etc.

 

 

tower-diagnostics-20230625-0009.zip

Edited by CouchPawTayTow
add diag

  • Author
3 hours ago, CouchPawTayTow said:

have a supported card (quadro K4000 - Latest Legacy GPU version (470.xx series): 470.182.03) that works and followed the instructions re: docker off/on/reboot etc. Card wasn't bound, but tried binding/rebooting then unbinding/rebooting just to be sure.

Form the Diagnostics I see that you are usig the latest driver version not the 470.xx legacy driver.

 

Jun 25 10:06:50 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 243
Jun 25 10:06:50 Tower kernel: NVRM: The NVIDIA Quadro K4000 GPU installed in this system is
Jun 25 10:06:50 Tower kernel: NVRM:  supported through the NVIDIA 470.xx Legacy drivers. Please
Jun 25 10:06:50 Tower kernel: NVRM:  visit http://www.nvidia.com/object/unix.html for more
Jun 25 10:06:50 Tower kernel: NVRM:  information.  The 535.54.03 NVIDIA driver will ignore
Jun 25 10:06:50 Tower kernel: NVRM:  this GPU.  Continuing probe...
Jun 25 10:06:50 Tower kernel: NVRM: No NVIDIA GPU found.
Jun 25 10:06:50 Tower kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 243


Please install the legacy driver, reboot and then post the Diagnostics again.

10 hours ago, ich777 said:

Form the Diagnostics I see that you are usig the latest driver version not the 470.xx legacy driver.

 

Apologies - by legacy, I meant the boot drive.

 

Switched to the 470 driver and now it's recognising it.

 

Cheers for your help!

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.