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

  • Replies 5.9k
  • Views 1.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

6 minutes ago, ich777 said:

Are you really sure that the card was working before? Please test it if possible in another system.

At your earlier suggestion i have tried it in another system and it is fully functional

  • Author
2 minutes ago, Obbyed said:

At your earlier suggestion i have tried it in another system and it is fully functional

Did you install a driver and put a 3D load too?

 

1 hour ago, Obbyed said:

Warning: file_put_contents(): Only -1 of 163 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/notify on line 218

Uh wait, how much RAM do you have in your system?

How much space do you have on your USB Flash device?

1 minute ago, ich777 said:

Did you install a driver and put a 3D load too?

 

Uh wait, how much RAM do you have in your system?

How much space do you have on your USB Flash device?

Yes I did

 

Currently have 4gb as it was bought as a barebones server, i have 16gb of space on the USB

  • Author
9 minutes ago, Obbyed said:

Currently have 4gb as it was bought as a barebones server

4GB of are too less for the base system and the driver nowadays.

 

You need at least 8GB of RAM for the driver to work since they are getting bigger and bigger with each revision.

Just now, ich777 said:

4GB of are too less for the base system and the driver nowadays.

 

You need at least 8GB of RAM for the driver to work since they are getting bigger and bigger with each revision.

Thankfully i have an 8GB kit coming on monday just to keep me online, thank you very much for your help

Hello Everyone,

I'm having a strange issue with my Nvidia Card (TESLA P4).

When I boot the server is working just fine.
It can transcode in PLEX & Unmanic.

 

After a couple of hours (or days it depends) - it stops working and it's no more recognized from the plugin:

immagine.png.7aa2524d1bd8bac7d8f9c7da9d5468fe.png

 

Does somebody have the same issue?

sekiro-diagnostics-20230129-1248.zip sekiro-diagnostics-20230129-0900.zip

On 1/27/2023 at 7:08 PM, ich777 said:

I really don't know what causes that issue because I barely can't reproduce it and I'm pretty much clueless what it could be since Unraid runs from RAM and the package is also installed on boot, so this basically means everything is installed fresh on each reboot.

 

I can only imagine that something in Docker prevents it from running properly because that's the only place in the chain where something is stored across reboots.

 

Anyways, glad that everything is now working for you again!

Hey I found the root cause!

Krusader grabs something locking out  /proc/sys/kernel/overflowuid

I haven't dug into it too much. but basically if I run krusader I cannot restart anything that uses the GPU without a system reboot.

 

This is only the (looks it up) the one from your repository the binhex one is ok even when it has root privileges. (I did have your one on root privileges with the advised settings)

Edited by BomB191

  • Author
3 hours ago, TDA said:

After a couple of hours (or days it depends) - it stops working and it's no more recognized from the plugin:

Seems like the Kernel module crashed, that happens usually because of some kind of hardware failure or hardware incompatibility.

Jan 26 02:59:57 Sekiro kernel: NVRM: GPU at PCI:0000:05:00: GPU-5d7f9c28-8f84-bb4a-7ae8-2456be369183
Jan 26 02:59:57 Sekiro kernel: NVRM: GPU Board Serial Number: 0322717107488
Jan 26 02:59:57 Sekiro kernel: NVRM: Xid (PCI:0000:05:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
Jan 26 02:59:57 Sekiro kernel: NVRM: GPU 0000:05:00.0: GPU has fallen off the bus.
Jan 26 02:59:57 Sekiro kernel: NVRM: GPU 0000:05:00.0: GPU serial number is 0322717107488.
Jan 26 02:59:57 Sekiro kernel: NVRM: A GPU crash dump has been created. If possible, please run
Jan 26 02:59:57 Sekiro kernel: NVRM: nvidia-bug-report.sh as root to collect this data before
Jan 26 02:59:57 Sekiro kernel: NVRM: the NVIDIA kernel module is unloaded.

 

Is your card cooled enough so that it don't overheat?

  • Author
3 hours ago, BomB191 said:

but basically if I run krusader I cannot restart anything that uses the GPU without a system reboot.

I will try that hopefully soon (my test server is still broken), thank you for the hint, but by default Krusader shouldn't be able to edit anything on the host...

When I start jellyfin, I use Nvidia to appear
docker: Error response from daemon: Unknown runtime specified nvidia.
See 'docker run --help'.
How can I solve it? None of the methods on the network are good

image.thumb.png.8c446d615fdb4c11963618540719764e.pngimage.thumb.png.03130d3a5b3cce58640e120099d1fb0b.pngtower-diagnostics-20230130-0952.zip

  • Author
7 hours ago, 56025192 said:

How can I solve it? None of the methods on the network are good

Please read the first post again, did you restart the Docker service after installing the plugin?

 

EDIT: Now I see the issue, you are updating the daemon.json on boot in the go file:

# Update mirrors
tee /etc/docker/daemon.json <<-'EOF'
{
 "registry-mirrors" : [
  "http://REMOVED.com",
  "https://REMOVED.com",
  "http://REMOVED.cn"]
}
EOF

 

Please delete this entry or at least comment it, reboot and see how it looks like when there no modification is made.

I would recommend that you add the required entries for Nvidia in your go file routine.

 

Hope that helps. ;)

 

EDIT2: Take also a look at this post where I explain how you can inject your mirrors too:

 

3 hours ago, ich777 said:

Please read the first post again, did you restart the Docker service after installing the plugin?

 

EDIT: Now I see the issue, you are updating the daemon.json on boot in the go file:

# Update mirrors
tee /etc/docker/daemon.json <<-'EOF'
{
 "registry-mirrors" : [
  "http://REMOVED.com",
  "https://REMOVED.com",
  "http://REMOVED.cn"]
}
EOF

 

Please delete this entry or at least comment it, reboot and see how it looks like when there no modification is made.

I would recommend that you add the required entries for Nvidia in your go file routine.

 

Hope that helps. ;)

 

EDIT2: Take also a look at this post where I explain how you can inject your mirrors too:

 

Thank you. The problem has been solved

I'm having trouble getting my A4000 working. I enabled UEFI and above 4G decoding, but I'm still getting this error:

Jan 30 08:30:32 montero kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1457)
Jan 30 08:30:32 montero kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

nvidia-smi and driver plugin both say no devices found, but the card shows up in system devices, so I'm not sure what's the issue. Card works fine on my gaming pc running windows.

 

montero-diagnostics-20230130-1136.zip

  • Author
2 hours ago, TealNerd said:

nvidia-smi and driver plugin both say no devices found, but the card shows up in system devices, so I'm not sure what's the issue. Card works fine on my gaming pc running windows.

First of all you have an error:

Jan 30 08:30:25 montero root: libkmod: kmod_config_parse: /etc/modprobe.d/nvidia.conf line 1: ignoring bad line starting with 'nvidia'

in your nvidia.conf file, it should be:

options nvidia NVreg_OpenRmEnableUnsupportedGpus=1

 

Second, you even don't use the Open Source driver package, please remove the file completely, reboot afterwards and post the Diagnostics again if the card isn't working.

 

Did you also enable Resizable BAR support in your BIOS?

 

2 hours ago, TealNerd said:

I enabled UEFI

If possible boot in legacy mode, I see in the initial post that you've wrote that it was working but stopped working after a reboot, did you boot in legacy mode when it was working?

@ich777 I saw the advice in other places to boot in legacy mode, but my motherboard doesn't seem to support enabling above 4g decoding and resizable bar in legacy mode (fwiw uefi is working fine for me now as well). I removed the file, and enabled resizable bar but still getting the same error.

montero-diagnostics-20230130-1450.zip

Edited by TealNerd

  • Author
59 minutes ago, TealNerd said:

I saw the advice in other places to boot in legacy mode, but my motherboard doesn't seem to support enabling above 4g decoding and resizable bar in legacy mode.

Then try booting without these options with legacy mode and see if it helps.

In the other thread you've said that it was working before correct?

 

Can you please check if a BIOS update is available for you motherboard? It seems to me that this is some kind of hardware incompatibility issue or at least some kind of wrong implementation in the BIOS.

1 minute ago, ich777 said:

Then try booting without these options with legacy mode and see if it helps.

In the other thread you've said that it was working before correct?

 

Can you please check if a BIOS update is available for you motherboard? It seems to me that this is some kind of hardware incompatibility issue or at least some kind of wrong implementation in the BIOS.

I'll check for a bios update, as for legacy with the options disabled, it doesn't work then either. The diag from the other thread was with legacy and no pcie options

Edited by TealNerd

Will these drivers allow UNRAID to access the 8 GPU cores on an older A10 series CPU?

 

hmmm... a test of the installation indicates that no, it won't find the "built in" GPU:

image.thumb.png.b92e67b43030d9552e01ce168a01c1bc.png

 

Anyone have any tips on configuration items that might enable this?

 

Had I been paying enough attention when I purchased the CPU, I wouldn't have purchased this one for a server. Sigh...

Edited by FreeMan

32 minutes ago, ich777 said:

Then try booting without these options with legacy mode and see if it helps.

In the other thread you've said that it was working before correct?

 

Can you please check if a BIOS update is available for you motherboard? It seems to me that this is some kind of hardware incompatibility issue or at least some kind of wrong implementation in the BIOS.

Updated bios to latest version, booted in legacy mode and no dice, getting the same error message. Is there anything specific I can look for in logs to get a clearer picture of what's going on?

3 hours ago, FreeMan said:

Will these drivers allow UNRAID to access the 8 GPU cores on an older A10 series CPU?

 

Why would you think a Nvidia driver would be used to utilize a AMD GPU?

54 minutes ago, ConnerVT said:

 

Why would you think a Nvidia driver would be used to utilize a AMD GPU?

Because I know just enough to be dangerous and don't recall who makes which GPUs. My bad. I used to obsess over this stuff, but I've got too many other priorities in life to worry about keeping up. Now I just dabble when I can.

 

Tucks tail and scurries away

  • Author
9 hours ago, TealNerd said:

The diag from the other thread was with legacy and no pcie options

I see that the driver is loaded for the device:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104GL [RTX A4000] [10de:24b0] (rev a1)
    Subsystem: Dell GA104GL [RTX A4000] [1028:14ad]
    Kernel driver in use: nvidia
    Kernel modules: nvidia_drm, nvidia

...but it still fails:

Jan 30 12:49:00 montero kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x25:0x65:1457)
Jan 30 12:49:00 montero kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

My last two recommendations are that you try to force the PCIe slot where the card is connected to PCIe Gen3 and that you disable C-States in your BIOS.

 

I have now a few users issues with AMD B-Series Chipset boards which are not working correctly, it seems to me that this is a bad implementation in the BIOS or some kind of hardware incompatibility issue.

Hello,

 

I have recently encountered an issue with this driver working with an old Geforce 970, i recently had this working for several days transcoding my media library all setup and working with no issue.

 

However today completely out of the blue (I hadn't been changing settings or fiddling with it) it stopped working, it is no longer recognised with your driver. 

 

System devices does show it

 

IOMMU group 16:[10de:13c2] 03:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)

 

The output from nvidia-smi - No devices found

 

Server has been rebooted and i have confirmed this isnt hardware (cables unplugged or lose, the fan is spinning on the GPU)

 

I am a unraid novice so please be gentle :P

 

Unraid version 6.11.5

And i was using the production branch of the Geforce driver

 

Thanks in advance

Getting the "no devices were found" but not sure when it started.  I know it used to work.

I have a quadro p2000.

Dug through this topic and found the solution from September:

On 9/23/2022 at 2:01 PM, ich777 said:

Please do the following (this is only necessary if you upgraded before I recompiled the driver):

  1. Open up a Unraid terminal and execute:
    rm -f /boot/config/plugins/nvidia-driver/packages/5.19.9/*
  2. Close the terminal
  3. Go to the Nvidia-Driver Plugin page
  4. Click on the button "Update & Download" (please wait until the download finished and the Done button is displayed)
  5. Reboot

 

But it didn't fix it.

Attaching diagnostics.  Would greatly appreciate any help.  Thank you so much.

tower-diagnostics-20230201-0906.zip

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.