1 hour ago, ConnerVT said:

I believe that the GTX1660 can now do 8 concurrent transcodes. Back when SpaceInvader One posted that video, NVidia drivers had it throttled to only 2 transcodes at a time.

Thanks, that should be more than enough for 95% of the time. At the very least, Plex can fall back to the iGPU.

1 hour ago, ConnerVT said:

You put ich777 in a bad spot. If you read the opening posts in this thread, he clearly states that he cannot assist anyone using this patch. It violates the Terms of Agreement from Nvidia, whom take their ToA very seriously. Which could actually put both him and Limetech at legal and financial risk.

I apologize and that's not my intention. If anything, I'm asking on advice in removing the patch. Now that I know the information above, I can do this confidently.

1 hour ago, ConnerVT said:

Regarding power supplies - Your supply may be more than enough for your system if it is functioning correctly. They do fail over time

I understand this, although since replacing a PSU is a major job (especially in the cramped case my system is in), I want to rule out software fixes first beforehand.

My only two cents to throw my hand into some of this....

Look into system Linux grub commands that turn off and affect ASPM.

Things like:

nvidia.NVreg_ResmanDebugLevel=255 modprobe.blacklist=nouveau

pci=noaer pcie_aspm=off

As usual find it to be ASPM power related due to sleep states...

More from eol device, new Linux kernel hardening and v550 Nvidia LTS 16 set reaching EOL....

So I'm not sure 10000 series cards will be available past kernel 6.14 with EOL or v500 coming up...

https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://www.nvidia.com/en-us/networking/products/lts-releases/&ved=2ahUKEwi-jbGdheORAxXK1fACHSWHPdcQFnoECBgQAQ&usg=AOvVaw2CEpbS-yawfaoAt8LsFcB6

The NVIDIA GTX 16-series GPUs have been completely discontinued from production as of early 2024, and remaining market inventory is being exhausted. However, official driver support is ongoing.

Driver and Software End of Life (EOL)

GeForce GTX 16-series (Consumer GPUs): These cards are still receiving regular Game Ready driver updates. NVIDIA has shifted its focus to the RTX brand, but the 16-series (Turing architecture without RT/Tensor cores) is not yet in a legacy support phase like the older GTX 10-series.

NVIDIA vGPU Software 16 Releases (Enterprise Software): The specific vGPU Software 16 Long-Term Support (LTS) branch is supported until July 2026.

Key Dates for Related Products

Product/Software Branch Status/Action End of Life (EOL) Date

GTX 16-series GPUs Production discontinued Early 2024

vGPU Software 16 LTS Branch Supported branch July 2026

GTX 10-series (Pascal), 900-series (Maxwell) GPUs Transitioning to legacy/quarterly security updates Regular driver support ends October 2025

NVIDIA Data Center GPU Drivers 550 family EOL reached June 2025

For the latest official information on specific software lifecycles, you can refer to the NVIDIA Long-Term Support Releases page or the NVIDIA Driver End of Life tracker.

NVIDIA Virtual GPU (vGPU) Software

Aug 4, 2025 — NVIDIA vGPU Software 16 Releases. Branch status: Long-Term Support Branch supported until July 2026.

Sources in NVIDIA Docs...

NVIDIA to End GeForce Regular Driver Support for Maxwell, Volta, and Pascal ...

Jul 30, 2025 — NVIDIA is planning to retire regular driver updates for its older, pre-RTX GPU generations after October 2025, the company announced. These include ...

Sources in TechPowerUp

Per following Nvidia I would expect 10 series and 20 series to end drivers support in future kernel past 6.14 come July 2026 with v16 LTS leaving the Nvidia Enterprise space... (Similar thing happens wo the gyx 780 series. Nothing wrong with hardware software to new and doesn't complie and latest kerenl

1 hour ago, bmartino1 said:

Look into system Linux grub commands that turn off and affect ASPM.

Please can you not give wrong advice, most of the users have disabled ASPM if you look through the last diagnostics.

1 hour ago, bmartino1 said:

nvidia.NVreg_ResmanDebugLevel=255

Why would you set this to 255? This parameter usually allows an integer between 0-3 and IIRC -1 for complete verbosity.

1 hour ago, bmartino1 said:

modprobe.blacklist=nouveau

This should be done via a modprobe file, however nouveau should by default be blacklisted on Unraid.

1 hour ago, bmartino1 said:

pci=noaer

Please only disable this if you have issues with Advance Error Reporting.

1 hour ago, bmartino1 said:

https://www.google.com/url?sa=t&source=web&rct=j&opi=89978449&url=https://www.nvidia.com/en-us/networking/products/lts-releases/&ved=2ahUKEwi-jbGdheORAxXK1fACHSWHPdcQFnoECBgQAQ&usg=AOvVaw2CEpbS-yawfaoAt8LsFcB6

Sorry but is this AI generated? This talks about Networking LTS support from Nvidia, not Graphics.

1 hour ago, bmartino1 said:

The NVIDIA GTX 16-series GPUs have been completely discontinued from production as of early 2024, and remaining market inventory is being exhausted. However, official driver support is ongoing.

Driver and Software End of Life (EOL)

GeForce GTX 16-series (Consumer GPUs): These cards are still receiving regular Game Ready driver updates. NVIDIA has shifted its focus to the RTX brand, but the 16-series (Turing architecture without RT/Tensor cores) is not yet in a legacy support phase like the older GTX 10-series.

NVIDIA vGPU Software 16 Releases (Enterprise Software): The specific vGPU Software 16 Long-Term Support (LTS) branch is supported until July 2026.

Key Dates for Related Products

Product/Software Branch Status/Action End of Life (EOL) Date

GTX 16-series GPUs Production discontinued Early 2024

vGPU Software 16 LTS Branch Supported branch July 2026

GTX 10-series (Pascal), 900-series (Maxwell) GPUs Transitioning to legacy/quarterly security updates Regular driver support ends October 2025

NVIDIA Data Center GPU Drivers 550 family EOL reached June 2025

For the latest official information on specific software lifecycles, you can refer to the NVIDIA Long-Term Support Releases page or the NVIDIA Driver End of Life tracker.

NVIDIA Virtual GPU (vGPU) Software

Aug 4, 2025 — NVIDIA vGPU Software 16 Releases. Branch status: Long-Term Support Branch supported until July 2026.

It would be way easier to write:
GTX16 series and up will still receive regular driver updates

GTX10 and GTX900 series will be converted to legacy branch and will be supported for at least a year or two (the last legacy driver, 470 driver series, supported Kepler and Maxwell for about 4 years)

You always have to take into consideration if you write EOL, most users would think they have to immediately have to buy a new GPU which is most of the times not true.

1 hour ago, bmartino1 said:

Jul 30, 2025 — NVIDIA is planning to retire regular driver updates for its older, pre-RTX GPU generations after October 2025, the company announced. These include ...

The key word is regular driver updates, they will still receive driver updates (security patches and compatibility updates) in the legacy branch.

Again, you can't know what Nvidia ever does, first they said they will not support GTX10 series in 580 driver but now it seems that Nvidia makes the 580 driver series to the new legacy branch for these cards.

Time will tell.

I've been struggling with this for literal days now, and I'm losing my mind trying to get nvidia support in docker. It worked fine for several weeks, and then I rebooted after (I believe) it automatically downloaded the "latest" 590 updated driver, which broke compatibility with my GTX 1050 Ti. I would prefer to keep using this card for transcoding and similar...

Now whenever I try and run any container that requires the GPU, I get the following error(s):

# docker run --rm --runtime=nvidia -e NVIDIA_VISIBLE_DEVICES=GPU-c96d3b5a-bdb2-4b41-b817-22755b00d28d -e NVIDIA_DRIVER_CAPABILITIES=all ubuntu nvidia-smi
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #1: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: permission denied: unknown.

# nvidia-container-cli -d /dev/tty info
-- WARNING, the following logs are for debugging purposes only --
I1230 04:18:39.723995 107649 nvc.c:396] initializing library context (version=1.17.9~1.17.9, build=e78456a41c71d73eabf7a85d1e531a108789349b)
I1230 04:18:39.724072 107649 nvc.c:367] using root /
I1230 04:18:39.724080 107649 nvc.c:368] using ldcache /etc/ld.so.cache
I1230 04:18:39.724098 107649 nvc.c:369] using unprivileged user 65534:65534
I1230 04:18:39.724165 107649 nvc.c:413] attempting to load dxcore to see if we are running under Windows Subsystem for Linux (WSL)
I1230 04:18:39.724260 107649 nvc.c:415] dxcore initialization failed, continuing assuming a non-WSL environment
I1230 04:18:39.724480 107650 rpc.c:71] starting driver rpc service
I1230 04:18:39.724951 107649 rpc.c:135] driver rpc service terminated with signal 15
nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: permission denied
I1230 04:18:39.724997 107649 nvc.c:455] shutting down library context

However nvidia-smi works fine on the unraid host, and the GPU is detected and loaded by the driver. GPU stats shows the card on the dashboard, and as far as I can tell, everything should be working.

/usr/lib/libnvidia-ml.so.1 exists and has 0755 permissions

/usr/lib64/libnvidia-ml.so.1 exists and has 0755 permissions

But as soon as I try and run it in a container... load library failed: libnvidia-ml.so.1: permission denied: unknown

Things I've tried:

• Downgrading the driver to all 580.* versions and the single listed 575.* version

• Downgrading Unraid to 7.2.0 (where it did seem to be working for a while)

• Removing the plugin entirely, rebooting, reinstalling the plugin and driver

• Adjusting various settings in /etc/nvidia-container-toolkit/config.toml (including no-cgroups=true/false), debug logging, ldstore/ldconfig settings, etc.

• Running containers with various combinations of --runtime=nvidia and --gpus=all flags, as well as visible devices and driver capabilities environment variables

• Various permissions on the libraries (0777/0644, etc)

• Various users:groups for nvidia-container-runtime (65564:65564)

• nvidia-ctk runtime configure

• Adding nvidia-persistenced to startup scripts

• Full path/implicit path to the runtime in /etc/docker/daemon.json

• Rebooting, rebooting, rebooting

• restarting the docker service over and over and over

I would appreciate any insight into the issue that anyone can provide. I'm about to give up entirely.

vault-diagnostics-20251229-2006.zip

2 hours ago, t3rminus said:

I've been struggling with this for literal days now, and I'm losing my mind trying to get nvidia support in docker. It worked fine for several weeks

First of all in which containers do you try to run your GPU?

2 hours ago, t3rminus said:

then I rebooted after (I believe) it automatically downloaded the "latest" 590 updated driver, which broke compatibility with my GTX 1050 Ti

Exactly, Pascal, so to speak GTX 10 series isn't supported anymore with the 590 driver series, please use the 580 driver version.

2 hours ago, t3rminus said:

/usr/lib/libnvidia-ml.so.1 exists and has 0755 permissions

/usr/lib64/libnvidia-ml.so.1 exists and has 0755 permissions

Please don't change that.

However from what I see, one container is definitely working since you get this in your logs:

Dec 29 19:59:30 Vault kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.

Are you really sure that the ubuntu container that you are trying to use supports Nvidia at all?

Not all containers work with Nvidia or at least can cause trouble.

Please also use a more recent driver than 575.x for testing.

I would also recommend that you do the following:

1. Remove the Nvidia Driver plugin

2. Reboot

3. Install the Nvidia Driver plugin

4. Got to the plugin page and select Driver version 590.x

5. Click "Update & Download"

6. Reboot

7. Test it in a container which is known to work like Jellyfin or Plex

2 hours ago, t3rminus said:

1. Adjusting various settings in /etc/nvidia-container-toolkit/config.toml (including no-cgroups=true/false), debug logging, ldstore/ldconfig settings, etc.

2. Running containers with various combinations of --runtime=nvidia and --gpus=all flags, as well as visible devices and driver capabilities environment variables

3. Various permissions on the libraries (0777/0644, etc)

4. Various users:groups for nvidia-container-runtime (65564:65564)

5. nvidia-ctk runtime configure

6. Adding nvidia-persistenced to startup scripts

7. Full path/implicit path to the runtime in /etc/docker/daemon.json

8. Rebooting, rebooting, rebooting

9. restarting the docker service over and over and over

To all of that, please don't do anything manually, the plugin does everything for you.

The plugin is working for at least 10k users if not more, I don't have the exact numbers in my head.

Just as a precaution, please also make sure that Resizable BAR support and Above 4G Decoding is enabled in your BIOS.

19 minutes ago, ich777 said:

First of all in which containers do you try to run your GPU?

Ultimately, I will be using Jellyfin, and beszel-agent-nvidia to monitor the system. Both were confirmed working prior to this.

19 minutes ago, ich777 said:

Exactly, Pascal, so to speak GTX 10 series isn't supported anymore with the 590 driver series, please use the 580 driver version.

Noted. I will use the v580

19 minutes ago, ich777 said:

Please don't change that.

I wouldn't, other than as a sanity check. I'm mostly trying to demonstrate it's not actually a permissions issue, despite the logs saying "Permission denied"

19 minutes ago, ich777 said:

However from what I see, one container is definitely working since you get this in your logs:

Dec 29 19:59:30 Vault kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.

Are you really sure that the ubuntu container that you are trying to use supports Nvidia at all?

Not all containers work with Nvidia or at least can cause trouble.

The ubuntu docker container is the documented way to test nvidia-container-toolkit, per NVidia's documentation:
https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/1.17.6/sample-workload.html

19 minutes ago, ich777 said:

Please also use a more recent driver than 575.x for testing.

I would also recommend that you do the following:

1. Remove the Nvidia Driver plugin

2. Reboot

3. Install the Nvidia Driver plugin

4. Got to the plugin page and select Driver version 590.x

5. Click "Update & Download"

6. Reboot

7. Test it in a container which is known to work like Jellyfin or Plex

I assume you mean v580.x considering my card wouldn't be supported on v590.x?

I have completed the following steps:

1. Remove the Nvidia Driver plugin

2. Reboot

3. Install the Nvidia Driver plugin

4. Go to the plugin page and select Driver version v580.119.02

5. Click "Update & Download"

6. Reboot

7. Configure Jellyfin per the first post:

   docker run
     -d
     --name='Jellyfin'
     --net='bridge'
     --pids-limit 2048
     -e TZ="America/Los_Angeles"
     -e HOST_OS="Unraid"
     -e HOST_HOSTNAME="Vault"
     -e HOST_CONTAINERNAME="Jellyfin"
     -e 'NVIDIA_VISIBLE_DEVICES'='GPU-c96d3b5a-bdb2-4b41-b817-22755b00d28d'
     -e 'NVIDIA_DRIVER_CAPABILITIES'='all'
     -e 'PUID'='99'
     -e 'PGID'='100'
     -e 'UMASK'='022'
     -l net.unraid.docker.managed=dockerman
     -l net.unraid.docker.webui='http://[IP]:[PORT:8096]'
     -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/jellyfin-logo.png'
     -p '8096:8096/tcp'
     -p '7359:7359/udp'
     -v '/mnt/user/TV/':'/data/tvshows':'rw'
     -v '/mnt/user/Movies/':'/data/movies':'rw'
     -v '/mnt/cache/appdata/Jellyfin/cache':'/cache':'rw'
     -v '/mnt/user/appdata/Jellyfin':'/config':'rw'
     --runtime=nvidia 'jellyfin/jellyfin:latest'
   
   7fba60687a82316ca2dcb78868ea64ac4f3f6a16a8c8f41306278774d3df934c
   docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #1: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
   nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: permission denied: unknown.
   
   The command failed.

19 minutes ago, ich777 said:

To all of that, please don't do anything manually, the plugin does everything for you.

The plugin is working for at least 10k users if not more, I don't have the exact numbers in my head.

Just as a precaution, please also make sure that Resizable BAR support and Above 4G Decoding is enabled in your BIOS.

I updated my BIOS/Firmware in the process of troubleshooting, entirely to add options for Resizable BAR and Above 4G Decoding. I can confirm they are both enabled.

1 hour ago, t3rminus said:

I assume you mean v580.x considering my card wouldn't be supported on v590.x?

Sorry my bad.

1 hour ago, t3rminus said:

I updated my BIOS/Firmware in the process of troubleshooting, entirely to add options for Resizable BAR and Above 4G Decoding. I can confirm they are both enabled.

Please post your Diagnostics again so that I can see what's going on and what the Nvidia driver does.

Here are my current diagnostics.

vault-diagnostics-20251230-0912.zip

54 minutes ago, t3rminus said:

Here are my current diagnostics.

Please try to disable you iGPU from your Ryzen CPU.

The Nvidia Driver, at least it seems from the Diagnostics, works just fine.

The error message is very strange since the library is basically there but why it fails is unknown, this is a really strange issue.

I really don't know what causes this on your system.

49 minutes ago, ich777 said:

Please try to disable you iGPU from your Ryzen CPU.

The Nvidia Driver, at least it seems from the Diagnostics, works just fine.

I've tried disabling the iGPU, with the same result.

The NVidia driver is loaded, and does appear to work fine from the host. I have GPU Statistics plugin installed, and it correctly recognizes the GPU and shows the live stats on the dashboard.

It's just the nvidia-container-toolkit/docker usage that fails.

docker run
  -d
  --name='Jellyfin'
  --net='bridge'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Vault"
  -e HOST_CONTAINERNAME="Jellyfin"
  -e 'JELLYFIN_PublishedServerUrl'='vault.d3rg.tech'
  -e 'NVIDIA_VISIBLE_DEVICES'='GPU-c96d3b5a-bdb2-4b41-b817-22755b00d28d'
  -e 'NVIDIA_DRIVER_CAPABILITIES'='all'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8096]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/jellyfin-logo.png'
  -p '8096:8096/tcp'
  -p '7359:7359/udp'
  -v '/mnt/user/TV/':'/data/tvshows':'rw'
  -v '/mnt/user/Movies/':'/data/movies':'rw'
  -v '/mnt/cache/appdata/Jellyfin/cache':'/cache':'rw'
  -v '/mnt/user/appdata/Jellyfin':'/config':'rw'
  --runtime=nvidia
  --gpus all 'jellyfin/jellyfin:latest'

9985f38b1bc250975d10e97c9ba1af1b7e5ea916a030ab9b1ab1fd62d1b593f0
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: permission denied: unknown.

Here's the latest diagnostics.

vault-diagnostics-20251230-1104.zip

1 hour ago, t3rminus said:

I've tried disabling the iGPU, with the same result.

What is this in your go file and what does it:

/bin/bash /boot/config/startup

I can only assume that something is modifying the driver otherwise it won't work for anyone.

I've spent hours working on the "NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running" error. This worked for me (yes it is an output from an LLM), I hope this works for someone else and I am by no mean trying to step on the developer (you can remove this if you see it fit), it's just hard to read through 216 pages of issues.

Issue

After installing an NVIDIA GPU (RTX 3060 / 5070 Ti) in Unraid, nvidia-smi failed with:

NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver

dmesg showed that the nouveau driver was binding to the GPU during early boot:

nouveau 0000:xx:xx.x: NVIDIA GA106
NVRM: No NVIDIA devices probed

This caused the NVIDIA kernel module to load but find no devices, resulting in modprobe: No such device.

---

Root Cause

Unraid was loading the nouveau driver at boot before the NVIDIA driver, even though the NVIDIA plugin was installed. Blacklisting nouveau via modprobe.d alone was not sufficient, because nouveau was loaded during early kernel initialization.

---

Fix

Disable nouveau at the kernel boot level using Syslinux:

1. Go to Main → Flash → Syslinux Configuration

2. Under Unraid OS, modify the append line:

Before:

append initrd=/bzroot

After:

append modprobe.blacklist=nouveau nouveau.modeset=0 initrd=/bzroot

3. Apply changes and reboot.

After reboot:

• lsmod | grep nouveau → no output

• lspci -nnk shows Kernel driver in use: nvidia

• nvidia-smi works correctly

---

Result

GPU is properly claimed by the NVIDIA driver, CUDA is available, and both proprietary and open-source NVIDIA drivers work as expected (confirmed with RTX 5070 Ti on Open Source driver).

1 hour ago, ich777 said:

What is this in your go file and what does it:

/bin/bash /boot/config/startup

I can only assume that something is modifying the driver otherwise it won't work for anyone.

#!/bin/sh
echo "Reticulating Splines..."

# Load persistant files
mkdir -p /opt/persist
mount -o loop /boot/config/persist.img /opt/persist
rm -rf /opt/persist/lost+found
cp -a /opt/persist/* /
# umount /opt/persist
# rmdir /opt/persist

Loads some persisted files onto the root file system, mostly some little scripts I wrote to do cleanup and archival:

root@Vault:/opt/persist# tree
.
└── usr
    └── local
        └── bin
            ├── appledouble
            ├── cleardot
            ├── cleards
            └── tgz

4 directories, 4 files

I am not modifying the driver in any way.

I just installed a Tesla P4 and have tried 3 drivers

Latest, open source and production and each time it complains the card is not supported by that version of the driver and I need to try an older driver.

4 hours ago, perfessor101 said:

I just installed a Tesla P4 and have tried 3 drivers

Latest, open source and production and each time it complains the card is not supported by that version of the driver and I need to try an older driver.

Do you have any Diagnostics?

8 hours ago, Quiver said:

Disable nouveau at the kernel boot level using Syslinux

Can you please open up a bug report? Nouveau should be disabled by default in Unraid.

However I would recommend to do that via a modprobe.d file not via syslinux.

2 hours ago, ich777 said:

Can you please open up a bug report? Nouveau should be disabled by default in Unraid.

However I would recommend to do that via a modprobe.d file not via syslinux.

@Quiver This is a clean install where the driver is blacklisted by default.

Check that you don't have a file in /boot/config/modprobe.d for nouveau as this will override the default.

root@UnraidTest:~# cat /etc/modprobe.d/nouveau.conf

# limetech - blacklist by default since most users will install the nvidia vendor driver

blacklist nouveau

root@UnraidTest:~#

root@UnraidTest:~# ls /boot/config/modprobe.d/

root@UnraidTest:~#

@ich777 @SimonF
I am sorry. It turns out I was mislead to remove the blacklist whilst troubleshooting the GPU issue earlier. That still doesn't tell me why the GPU didn't work with the open source driver in the first place, but is probably not common for others experiencing this issue.

With AI and other forums and boards out there, I do believe that the potential for others to be mislead like me would exist, so it may still be relevant to mention here.

Edited December 31, 2025Dec 31 by Quiver

On 12/22/2025 at 4:54 PM, treos33 said:

Just to reiterate, for anyone who missed the edit above...

The v590.x NVidia drivers drop support for the pascal architecture, that's Quadro P Series (i.e. P2000, P1000) and the GTX 10XX (i.e. 1060, 1080). If you have one of these cards, make sure to stay on the v580.x drivers.

This fixed my issue (Quadro P card), thanks.

On 12/22/2025 at 12:33 AM, ich777 said:

Please read this post:
https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/211/#comment-1593815

Is it possible that you have those two lines on your plugins settings page like in this post:
https://forums.unraid.net/topic/98978-plugin-nvidia-driver/page/178/#findComment-1487703

If yes please read the next post to fix your issue.

If you don't have those two lines in your plugins settings page then please make sure that nothing is blocking access to GitHub and also make sure to disable AdBlocking if you have it in place, your server needs exclusive access to the Internet without any AdBlocking.

If you have Unifi Network gear please also check the logs if it's blocking access to GitHub for your server.

Thanks for the response. Had been travelling for the holidays - just got back to the server.
I did not have those two line and I rolled back the driver and restarted and everything is good now. Screenshot below.

Does this mean that I am stuck on version 580 until I change this card?

Edited January 2Jan 2 by abhi.ko

36 minutes ago, abhi.ko said:

Does this mean that I am stuck on version 580 until I change this card?

Yes.

If you are using it only for transcoding then this driver version will still be fine.

Just keep in mind to upgrade it somewhere in the next few years.

Good day

i am new to unraid i just have one issue i have a gtx 670 card but i see the app only goes to v575.64.05 and the maximum supported NVIDIA driver version for the GeForce GTX 670 on Linux is 470.256.02 (or other versions in the 470 series). This is the highest branch that provides full support for the Kepler architecture (GTX 600 series) GPUs.

Key details regarding drivers for the GTX 670 on Linux:

Kepler Architecture: The GTX 670 is based on the Kepler architecture. NVIDIA has moved these older GPUs to legacy support.

Legacy Driver Branch: The 470 driver series is the most recent legacy branch that fully supports your card. Newer driver branches (e.g., 500 series and above) dropped support for the Kepler architecture

and i am running unraid v 7.2.3 must i downgrade on the versoin or what to make this card work

as i get this Installed GPU(s):
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

i have tried all versoins listed on the app

26 minutes ago, unraid.admin said:

GeForce GTX 670

Did you read that recommended post on top:

so what you are teling is i must other sotfware then unraid as they dont support 600 series cards and was looking forward to it for my plex sever with few other docket severs

5 minutes ago, unraid.admin said:

so what you are teling is i must other sotfware then unraid as they dont support 600 series cards and was looking forward to it for my plex sever with few other docket severs

I don't think that you can easily use another OS so that you can make use of that card since the old legacy driver v470.x doesn't support newer Kernels anymore and wont even compile against newer Kernels and Nvidia basically deprecated these cards since the new legacy driver seems to be v580.x which basically supports Maxwell and Pascal architectures (no official confirmation however).

The GTX670 is basically not the best choice nowadays for transcoding since it can only transcode h264 (AVC) and is not capable of transcoding h265 (HEVC).

Even if you use another OS you will be stuck on an older Kernel and can't upgrade to something recent because of your Nvidia card.

May I ask what system you have? Do you have Diagnostics for me so that I can go through them?

A new or used card is not an option for you?

Something like a Nvidia T400 would be more than enough for a few simultaneous transcodes these days and is supported by all driver versions since it's Turing based and you can get it for a pretty cheap price IIRC.