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

attached is the diagnostics, also when I select a previous version of the driver I get the message attached earlier regarding v590.xx already downed loaded. it does appear to be something problematic with the plugin.

mercury-diagnostics-20260119-1810.zip

  • 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
11 minutes ago, holtdw01 said:

attached is the diagnostics, also when I select a previous version of the driver I get the message attached earlier regarding v590.xx already downed loaded. it does appear to be something problematic with the plugin.

Do you also have these messages on the plugin page:
grafik.png

If yes, then this basically means the plugins is broken and you have to uninstall it.

If the plugin is still there after you uninstalled it and rebooted then something else is wrong with your system which I can't tell what it be, please make a post in the General Support subforums.

I see from your syslog that the initialization from the GPU was done early, but failed obviously because it's a 590.x version driver, so this means the removal from the plugin was not successful, which isn't an issue from the plugin itself usually since the plugin doesn't handle the removal, this is outside of the scope from the plugin.

However I would recommend that you do the following:

  1. Remove the Plugin

  2. Reboot

  3. Check if the Plugin is still there, if yes create a post in the General Support subforums, if not continue

  4. Install the Plugin again

  5. Select a 580.x driver version

  6. Click Update & Download and wait until the Dialog windows says it's finished

  7. Reboot

After that the correct Nvidia driver should be installed.

6 hours ago, ich777 said:

Sorry, such old versions aren't supported anymore and the Open Source Driver won't be recompiled for such an old Unraid version (released about a year ago).

However you can compile your own driver package and have to make sure that it's correctly load at boot, please see this container:
https://github.com/ich777/unraid_kernel
and the build script for the Nvidia Drivers is here:
https://github.com/unraid/unraid-nvidia-driver/tree/master/source

Please do note that in my opinion it's not worth to go through all the effort and just upgrade to 7.2.3, I haven't heard anything bad about 7.2.3, I would strongly recommend to upgrade.

Ah, thank you so much ich777! This is very helpful info honestly, years ago I compiled a custom kernel for Unraid ~6.8 for the Fusion-IO cards, and was heart broken when that was no longer possible with the newer versions. I'm not exactly sure on how to build the Nvidia driver, as this likely more complex than compiling the driver into the kernel, or making a loadable .ko module, none the less it will be a fine adventure ..... o7 .

Really appreciate you taking the time to put all that together over the years and share the link and the environment to compile a driver. The installscript.sh alone is very helpful to get all the proper autoconf and make, gcc, etc. That was always such a pain with slackware not having a package manager that can just pull and or build (eg emerge).

I will need to figure out lots, but intend to follow though on this until Unraid V7 has more what I'm after.

Thanks,

Jonathan

OK, I was able to get the unraid-kernel docker setup, specified gcc_11.2.0.

I wasn't sure if need to run the installscript.sh, but tried with and without, both times ran into some issues with missing dependencies for cmake ( openssl-solibs, libarchive, libxml2). Manually installed them (from slackware 15), think is OK for now. I took the kernel ".config" file from 6.1.125, and copy into 6.1.126 and was able to "make modules" successfully !

Good start!

I cloned unraid-nvidia-driver to /usr/src, and ran into a few questions. I checked out the compile.sh, and noted the instructions and the bottom, but upon trying the example commands and even older versions, it doesn't seem to kick anything off. I see the wget looks like its designed to fetch the nvidia package and then run it with command line options you've figured out, I'd really love to use that if I can figure out how its intended to be run?

I am not sure what ${DATA_DIR} should be, variable not defined in the docker, can only assume there is some sort of setup I missed or inadvertently skipped?

1. compile.sh - what should DATA_DIR be defined as ? Assume /usr/src? The kernel helper docker by default doesn't have it defined and I've probably missed where that step somewhere?

"root@0052624a534f:/usr/src# echo $DATA_DIR

root@0052624a534f:/usr/src# set | grep -i data

root@0052624a534f:/usr/src# env | grep -i data

"

2. Following the examples in:

bash compile.sh "580.126.09" "opensource" only sets a few variables, and doesn't do anything;

bash compile.sh "580.126.09" "opensource"

I added some echo statements

{ "branches": { "production": { "current": "580.126.09", "last_prb": "580.119.02" }, "newfeature": { "current": "590.48.01", "last_nfb": "575.64.05" }, "beta": { "current": "590.44.01" }, "legacy": { "current": "470.256.02" } }, "runtimes": { "containertoolkit": { "current": "1.18.1" }, "libnvidia": { "current": "1.18.1" } } }

lib and contv 1.18.1 and 1.18.1

I of course tried calling with just

bash compile.sh "580.126.09" and even "580", and "580.126" ... ?

No matter it quits, compile.sh has a function called nvidia_driver() inside, but it never gets called?

I manually called it at the bottom of the script which of course forced some action to happen, but not the expected.

I assume this isn't how its intended to be run?

Any hints?

thanks very much!

Edited by jc179

57 minutes ago, jc179 said:

OK, I was able to get the unraid-kernel docker setup, specified gcc_11.2.0.

I wasn't sure if need to run the installscript.sh, but tried with and without, both times ran into some issues with missing dependencies for cmake ( openssl-solibs, libarchive, libxml2). Manually installed them (from slackware 15), think is OK for now. I took the kernel ".config" file from 6.1.125, and copy into 6.1.126 and was able to "make modules" successfully !

Good start!

I cloned unraid-nvidia-driver to /usr/src, and ran into a few questions. I checked out the compile.sh, and noted the instructions and the bottom, but upon trying the example commands and even older versions, it doesn't seem to kick anything off. I see the wget looks like its designed to fetch the nvidia package and then run it with command line options you've figured out, I'd really love to use that if I can figure out how its intended to be run?

I am not sure what ${DATA_DIR} should be, variable not defined in the docker, can only assume there is some sort of setup I missed or inadvertently skipped?

1. compile.sh - what should DATA_DIR be defined as ? Assume /usr/src? The kernel helper docker by default doesn't have it defined and I've probably missed where that step somewhere?

"root@0052624a534f:/usr/src# echo $DATA_DIR

root@0052624a534f:/usr/src# set | grep -i data

root@0052624a534f:/usr/src# env | grep -i data

"

2. Following the examples in:

bash compile.sh "580.126.09" "opensource" only sets a few variables, and doesn't do anything;

bash compile.sh "580.126.09" "opensource"

I added some echo statements

{ "branches": { "production": { "current": "580.126.09", "last_prb": "580.119.02" }, "newfeature": { "current": "590.48.01", "last_nfb": "575.64.05" }, "beta": { "current": "590.44.01" }, "legacy": { "current": "470.256.02" } }, "runtimes": { "containertoolkit": { "current": "1.18.1" }, "libnvidia": { "current": "1.18.1" } } }

lib and contv 1.18.1 and 1.18.1

I of course tried calling with just

bash compile.sh "580.126.09" and even "580", and "580.126" ... ?

No matter it quits, compile.sh has a function called nvidia_driver() inside, but it never gets called?

I manually called it at the bottom of the script which of course forced some action to happen, but not the expected.

I assume this isn't how its intended to be run?

Any hints?

thanks very much!

You really should update to a newer unraid version, also here, i compiled it for you. I have not tested it tho but it installs!

The download will be valid for a week. https://clips.magnon.ovh/vUwo7/XUpILAvi10.zip

filename: /lib/modules/6.1.126-Unraid/kernel/drivers/video/nvidia.ko

import_ns: DMA_BUF

alias: char-major-195-*

version: 580.126.09

supported: external

license: Dual MIT/GPL

firmware: nvidia/580.126.09/gsp_tu10x.bin

firmware: nvidia/580.126.09/gsp_ga10x.bin

srcversion: E0E7373A37DB6AAC4C8D5BF

alias: of:N*T*Cnvidia,tegra264-displayC*

alias: of:N*T*Cnvidia,tegra264-display

alias: of:N*T*Cnvidia,tegra234-displayC*

alias: of:N*T*Cnvidia,tegra234-display

alias: pci:v000010DEd*sv*sd*bc06sc80i00*

alias: pci:v000010DEd*sv*sd*bc03sc02i00*

alias: pci:v000010DEd*sv*sd*bc03sc00i00*

depends: i2c-core,drm

retpoline: Y

name: nvidia

vermagic: 6.1.126-Unraid SMP preempt mod_unload

parm: NvSwitchRegDwords:NvSwitch regkey (charp)

parm: NvSwitchBlacklist:NvSwitchBlacklist=uuid[,uuid...] (charp)

parm: NVreg_ResmanDebugLevel:int

parm: NVreg_RmLogonRC:int

parm: NVreg_ModifyDeviceFiles:int

parm: NVreg_DeviceFileUID:int

parm: NVreg_DeviceFileGID:int

parm: NVreg_DeviceFileMode:int

parm: NVreg_InitializeSystemMemoryAllocations:int

parm: NVreg_UsePageAttributeTable:int

parm: NVreg_EnablePCIeGen3:int

parm: NVreg_EnableMSI:int

parm: NVreg_EnableStreamMemOPs:int

parm: NVreg_RestrictProfilingToAdminUsers:int

parm: NVreg_PreserveVideoMemoryAllocations:int

parm: NVreg_EnableS0ixPowerManagement:int

parm: NVreg_S0ixPowerManagementVideoMemoryThreshold:int

parm: NVreg_DynamicPowerManagement:int

parm: NVreg_DynamicPowerManagementVideoMemoryThreshold:int

parm: NVreg_EnableGpuFirmware:int

parm: NVreg_EnableGpuFirmwareLogs:int

parm: NVreg_OpenRmEnableUnsupportedGpus:int

parm: NVreg_EnableUserNUMAManagement:int

parm: NVreg_MemoryPoolSize:int

parm: NVreg_KMallocHeapMaxSize:int

parm: NVreg_VMallocHeapMaxSize:int

parm: NVreg_IgnoreMMIOCheck:int

parm: NVreg_NvLinkDisable:int

parm: NVreg_EnablePCIERelaxedOrderingMode:int

parm: NVreg_RegisterPCIDriver:int

parm: NVreg_RegisterPlatformDeviceDriver:int

parm: NVreg_EnableResizableBar:int

parm: NVreg_EnableDbgBreakpoint:int

parm: NVreg_EnableNonblockingOpen:int

parm: NVreg_CoherentGPUMemoryMode:charp

parm: NVreg_RegistryDwords:charp

parm: NVreg_RegistryDwordsPerDevice:charp

parm: NVreg_RmMsg:charp

parm: NVreg_GpuBlacklist:charp

parm: NVreg_TemporaryFilePath:charp

parm: NVreg_ExcludedGpus:charp

parm: NVreg_DmaRemapPeerMmio:int

parm: NVreg_RmNvlinkBandwidth:charp

parm: NVreg_RmNvlinkBandwidthLinkCount:int

parm: NVreg_ImexChannelCount:int

parm: NVreg_CreateImexChannel0:int

parm: NVreg_GrdmaPciTopoCheckOverride:int

parm: rm_firmware_active:charp





  • Author
2 hours ago, jc179 said:

Any hints?

thanks very much!

Sorry but compilation is not topic and out of scope from this thread. This is only the plugin support thread if something isn't working with the plugin.

5 hours ago, Mainfrezzer said:

You really should update to a newer unraid version, also here, i compiled it for you. I have not tested it tho but it installs!

The download will be valid for a week. https://clips.magnon.ovh/vUwo7/XUpILAvi10.zip

filename: /lib/modules/6.1.126-Unraid/kernel/drivers/video/nvidia.ko

import_ns: DMA_BUF

alias: char-major-195-*

version: 580.126.09

supported: external

license: Dual MIT/GPL

firmware: nvidia/580.126.09/gsp_tu10x.bin

firmware: nvidia/580.126.09/gsp_ga10x.bin

srcversion: E0E7373A37DB6AAC4C8D5BF

alias: of:N*T*Cnvidia,tegra264-displayC*

alias: of:N*T*Cnvidia,tegra264-display

alias: of:N*T*Cnvidia,tegra234-displayC*

alias: of:N*T*Cnvidia,tegra234-display

alias: pci:v000010DEd*sv*sd*bc06sc80i00*

alias: pci:v000010DEd*sv*sd*bc03sc02i00*

alias: pci:v000010DEd*sv*sd*bc03sc00i00*

depends: i2c-core,drm

retpoline: Y

name: nvidia

vermagic: 6.1.126-Unraid SMP preempt mod_unload

parm: NvSwitchRegDwords:NvSwitch regkey (charp)

parm: NvSwitchBlacklist:NvSwitchBlacklist=uuid[,uuid...] (charp)

parm: NVreg_ResmanDebugLevel:int

parm: NVreg_RmLogonRC:int

parm: NVreg_ModifyDeviceFiles:int

parm: NVreg_DeviceFileUID:int

parm: NVreg_DeviceFileGID:int

parm: NVreg_DeviceFileMode:int

parm: NVreg_InitializeSystemMemoryAllocations:int

parm: NVreg_UsePageAttributeTable:int

parm: NVreg_EnablePCIeGen3:int

parm: NVreg_EnableMSI:int

parm: NVreg_EnableStreamMemOPs:int

parm: NVreg_RestrictProfilingToAdminUsers:int

parm: NVreg_PreserveVideoMemoryAllocations:int

parm: NVreg_EnableS0ixPowerManagement:int

parm: NVreg_S0ixPowerManagementVideoMemoryThreshold:int

parm: NVreg_DynamicPowerManagement:int

parm: NVreg_DynamicPowerManagementVideoMemoryThreshold:int

parm: NVreg_EnableGpuFirmware:int

parm: NVreg_EnableGpuFirmwareLogs:int

parm: NVreg_OpenRmEnableUnsupportedGpus:int

parm: NVreg_EnableUserNUMAManagement:int

parm: NVreg_MemoryPoolSize:int

parm: NVreg_KMallocHeapMaxSize:int

parm: NVreg_VMallocHeapMaxSize:int

parm: NVreg_IgnoreMMIOCheck:int

parm: NVreg_NvLinkDisable:int

parm: NVreg_EnablePCIERelaxedOrderingMode:int

parm: NVreg_RegisterPCIDriver:int

parm: NVreg_RegisterPlatformDeviceDriver:int

parm: NVreg_EnableResizableBar:int

parm: NVreg_EnableDbgBreakpoint:int

parm: NVreg_EnableNonblockingOpen:int

parm: NVreg_CoherentGPUMemoryMode:charp

parm: NVreg_RegistryDwords:charp

parm: NVreg_RegistryDwordsPerDevice:charp

parm: NVreg_RmMsg:charp

parm: NVreg_GpuBlacklist:charp

parm: NVreg_TemporaryFilePath:charp

parm: NVreg_ExcludedGpus:charp

parm: NVreg_DmaRemapPeerMmio:int

parm: NVreg_RmNvlinkBandwidth:charp

parm: NVreg_RmNvlinkBandwidthLinkCount:int

parm: NVreg_ImexChannelCount:int

parm: NVreg_CreateImexChannel0:int

parm: NVreg_GrdmaPciTopoCheckOverride:int

parm: rm_firmware_active:charp





I understand I should upgrade but presently its missing some addons I need, and my dockers don't start automatically, and only manually start works. Of course eventually I will have no choice but to solve the problem and upgrade....

Appreciate you taking the time to do this for me, hopefully one day I can figure out how to do this.

4 hours ago, ich777 said:

Sorry but compilation is not topic and out of scope from this thread. This is only the plugin support thread if something isn't working with the plugin.

I understand - thank you .

On 1/16/2026 at 9:28 PM, deicist said:

Hi,

I've been running this plugin for ages and it's working great, I can use my GPUs (2*1080s and a 3070) in various containers, all peachy.

However, I'm trying to setup games on whales 'wolf': Quickstart :: Games On Whales and stuck at this line:

"One last final check: we have to make sure that the nvidia-drm module has been loaded and that the module is loaded with the flag modeset=1"

Is it possible to set that with this plugin? And if so, how? The quickstart talks about updating Grub which I'm not sure is applicable to unraid?


Sorry for quoting my own post in the hope of getting a reply. @ich777 is this something that's possible with this plugin?

  • Author
48 minutes ago, deicist said:

Sorry for quoting my own post in the hope of getting a reply. @ich777 is this something that's possible with this plugin?

Oh sorry I've overlooked your comment... :/

Yes, but this has nothing to do with the plugin, you have to either add an entry to your syslinux.config or you have to add a modprobe.d file to Unraid, please issue this command from a Unraid terminal and reboot afterwards:

mkdir -p /boot/config/modprobe.d
echo "options nvidia-drm modeset=1" > /boot/config/modprobe.d/nvidia-drm.conf

After the reboot you should be able to do this from an Unraid terminal to verify it was applied correctly:

cat /sys/module/nvidia_drm/parameters/modeset

and it should either revert Y IIRC.

Thanks @ich777 the time you take to answer questions like these even when not specifically the domain of your plugin is very much appreciated.

I am having issues trying to get my 5060ti working with 590 or production drivers. It just refuses to detect the GPU unless I use 580 open source drivers. I am trying to use this card for AI and it seems I might need 590 with CUDA 13.1 to enable features like MXFP4 quants.

Here are dmesg related to nvidia:

[ 53.783367] nvidia: loading out-of-tree module taints kernel.

[ 53.784393] nvidia: module license 'NVIDIA' taints kernel.

[ 53.785380] Disabling lock debugging due to kernel taint

[ 53.786380] nvidia: module license taints kernel.

[ 53.789893] atlantic: Detect ATL2FW 1030025

[ 53.897722] atlantic: Detect ATL2FW 1030025

[ 53.898530] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms ovfl timer

[ 53.899526] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules

[ 53.900515] RAPL PMU: hw unit of domain package 2^-14 Joules

[ 53.901483] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules

[ 53.904155] nvidia-nvlink: Nvlink Core is being initialized, major device number 238

[ 53.910461] nvidia 0000:02:00.0: enabling device (0000 -> 0003)

[ 53.912629] nvidia 0000:02:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none

[ 53.926592] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 590.48.01 Mon Dec 8 11:22:45 UTC 2025

[ 54.333462] cryptd: max_cpu_qlen set to 1000

[ 54.333828] i915 0000:00:02.0: [drm] Found ALDERLAKE_P (device ID 46a8) display version 13.00 stepping D0

[ 54.336174] i915 0000:00:02.0: [drm] VT-d active for gfx access

[ 54.336817] Console: switching to colour dummy device 80x25

[ 54.336845] i915 0000:00:02.0: vgaarb: deactivate vga console

[ 54.336901] i915 0000:00:02.0: [drm] Using Transparent Hugepages

[ 54.337326] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem

[ 54.338442] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 590.48.01 Mon Dec 8 12:50:27 UTC 2025

[ 54.338811] AES CTR mode by8 optimization enabled

[ 54.340218] [drm] [nvidia-drm] [GPU ID 0x00000200] Loading driver

[ 54.340351] [drm] Initialized nvidia-drm 0.0.0 for 0000:02:00.0 on minor 1

[ 126.681089] NVRM: The NVIDIA GPU 0000:02:00.0 (PCI ID: 10de:2d04)

NVRM: installed in this system requires use of the NVIDIA open kernel modules.

[ 126.681112] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:1001)

[ 126.682133] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

[ 126.686160] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.

[ 128.677050] NVRM: The NVIDIA GPU 0000:02:00.0 (PCI ID: 10de:2d04)

NVRM: installed in this system requires use of the NVIDIA open kernel modules.

[ 128.677071] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:1001)

[ 128.678182] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

[ 132.298419] NVRM: The NVIDIA GPU 0000:02:00.0 (PCI ID: 10de:2d04)

NVRM: installed in this system requires use of the NVIDIA open kernel modules.

[ 132.298441] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:1001)

[ 132.299501] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

[ 132.333543] NVRM: The NVIDIA GPU 0000:02:00.0 (PCI ID: 10de:2d04)

NVRM: installed in this system requires use of the NVIDIA open kernel modules.

[ 132.333563] NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:1001)

[ 132.334915] NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

Here is my diagnostics. nvidia-smi wont detect anything under production or new feature branches

ugreen-diagnostics-20260121-1607.zip

50 series need open source currently.

Just now, Kilrah said:

50 series need open source currently.

ah thanks for that confirmation. Are we waiting on an updated unraid kernel or nvidia to release the open source versions?

  • Author
5 hours ago, ranova said:

ah thanks for that confirmation. Are we waiting on an updated unraid kernel or nvidia to release the open source versions?

I don't understand?

Go into the settings from the plugin, select the Open Source driver, click on Update & Download, wait for the dialog to say it's okay to reboot, reboot your Server, done.

6 minutes ago, ich777 said:

I don't understand?

Go into the settings from the plugin, select the Open Source driver, click on Update & Download, wait for the dialog to say it's okay to reboot, reboot your Server, done.

Sorry, I meant when can we expect 590 drivers to work with blackwell/50 series cards? Are we waiting on nvidia or unraid to do updates?

590 brings the latest cuda features which is required for newer features such as MXFP4: https://huggingface.co/blog/RakshitAralimatti/learn-ai-with-me

  • Author
1 hour ago, ranova said:

Sorry, I meant when can we expect 590 drivers to work with blackwell/50 series cards? Are we waiting on nvidia or unraid to do updates?

I compile the Open Source drivers when a new Unraid version is released.

So to speak, when the next Unraid version is released you should see the Open Source 590.x series driver.

Apparently, the latest update failed to install. I'm showing my current version as 580.119.02 and in the available versions list, production is shown as 580.126.09. I tried downloading and installing from the plugin page, but it's telling me that the newest version is already downloaded. Will this just fix itself when the next version becomes available or should I go through whatever the process is to manually update?

Thanks,

Sam

  • Author
5 hours ago, SamDu said:

Apparently, the latest update failed to install.

What was the error message?

5 hours ago, SamDu said:

I tried downloading and installing from the plugin page, but it's telling me that the newest version is already downloaded. Will this just fix itself when the next version becomes available or should I go through whatever the process is to manually update?

If it tells you that it's already downloaded then it should be fine, you can try to select the driver version manually and click Update & Download, this will verify that the driver is installed.

hi everybody,

has anybody successfully installed an Nvidia Geforce RTX 5060 or do I need to wait for the drivers to be updated - since so long my system says no device :( although it is recognized under tools / system devices
[10de:2d05] 01:00.0 VGA compatible controller: NVIDIA Corporation GB206 [GeForce RTX 5060] (rev a1)
Nvidia Info:

Nvidia Driver Version: 590.48.01

Open Source Kernel Module: No

Installed GPU(s):
No devices were found

Driver Update Notification

Enabled
unraid version 7.2.3

Edited by christophl75

  • Author
21 minutes ago, christophl75 said:

Open Source Kernel Module: No

This is your issue, 50 series cards need the Open Source driver version on Linux.

from https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/210/#findComment-1594177

from 12/04/25 until about 1/16/26 everything was running fine. but a few days ago my unraid started randomly crashing.

I changed pcie from auto to 4.0 and that didn't do anything. but changing it to 3.0 appears to have made it slightly more stable but it will still crashes. going from every other hour to once a day or so. I tried setting it to 2.0 instead of 3.0 but that had the same results as 3.0.

both Above 4G Decoding is enabled and Resizable BAR Support is enabled.

ran the mem test and had no errors.

I have syslogs for the last few days but im not sure if those are safe to share. So I have included a screenshot of the error from right before the most recent crash.

attached are my driver info, nividia-smi, tower diagnostics, and my syslog error.

@ich777 if you say it's safe to include my syslogs I will add them.

Thank you for all the help and sorry to be back asking for more.

driver info.PNG

nvidia-smi.PNG

system log.PNG

On 1/22/2026 at 3:03 PM, ich777 said:

What was the error message?

If it tells you that it's already downloaded then it should be fine, you can try to select the driver version manually and click Update & Download, this will verify that the driver is installed.

Don't recall exactly, but it was something unhelpful along the lines of, "The update failed to install. Update the plugin manually."

Edit: Found it:

Notification

Found new Nvidia Driver v580.126.09 but a download error occurred! Please try to download the driver manually!

Screenshot 2026-01-23 171908.png

Screenshot 2026-01-23 171936.png

Edited by SamDu
Found error message.

  • Author
9 hours ago, SamDu said:

Don't recall exactly, but it was something unhelpful along the lines of, "The update failed to install. Update the plugin manually."

9 hours ago, SamDu said:

Notification

Found new Nvidia Driver v580.126.09 but a download error occurred! Please try to download the driver manually!

Download failed for some reason, can't tell what went wrong when the download failes, maybe a short disconnect, GitHub not responding or something else happened, download errors are really hard to track down.

9 hours ago, SamDu said:

Found new Nvidia Driver v580.126.09 but a download error occurred! Please try to download the driver manually!

The plugin has a lot of fail-safes built in so that it is really hard to mess up, even if the driver is not found on boot, the plugin tries to download it on boot time, of course the boot time will take a bit longer depending how much bandwidth do you have and how fast or slow GitHub is.

So to speak, if you the plugin tells you that driver version 580.126.09 is already downloaded and the Checksum is OK, then it is safe to reboot, since when the Checksum fails it will try to re-download the driver.

  • Author
11 hours ago, killercola said:

from 12/04/25 until about 1/16/26 everything was running fine. but a few days ago my unraid started randomly crashing.

I don't think that the Nvidia driver is the culprit since it seems that lsof is the cause of the issue.

Did you maybe install some other Docker/LXC/VM that could be the culprit?

The message lists just the modules which are linked in the Kernel and therefore it's listed first or at least somewhere at the beginning and the Kernel is always tainted because usually ZFS is there on Unraid and of course the Nvidia driver.

However I removed the Diagnostics since it seems SpaceEngineers is able to the write into the system log and there was some token included.

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.