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

  • Author
1 hour ago, Zeze21 said:

I updated to 6.12.3 and the server showed initally all 4 GPUs.

The driver sees 3 GPUs:

Attached GPUs                             : 3
...
GPU 00000000:08:00.0
    Product Name                          : NVIDIA GeForce RTX 2070 SUPER
...
GPU 00000000:09:00.0
    Product Name                          : NVIDIA GeForce GT 1030
...
GPU 00000000:44:00.0
    Product Name                          : NVIDIA GeForce GT 1030

 

1 hour ago, Zeze21 said:

(i had one vm running)

Is one GPU passed through to the VM or are more GPUs passed through to VMs?

Please don't forget that if you pass a GPU through to the VM and the VM is running that it doesn't show on the plugin page...

 

However I see this in your lspci:

08:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1)
	Subsystem: NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84]
	Kernel driver in use: nvidia
	Kernel modules: nvidia_drm, nvidia
08:00.1 Audio device [0403]: NVIDIA Corporation TU104 HD Audio Controller [10de:10f8] (rev a1)
	Subsystem: NVIDIA Corporation TU104 HD Audio Controller [10de:1e84]
08:00.2 USB controller [0c03]: NVIDIA Corporation TU104 USB 3.1 Host Controller [10de:1ad8] (rev a1)
	Subsystem: NVIDIA Corporation TU104 USB 3.1 Host Controller [10de:1e84]
	Kernel driver in use: xhci_hcd
08:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller [10de:1ad9] (rev a1)
	Subsystem: NVIDIA Corporation TU104 USB Type-C UCSI Controller [10de:1e84]
09:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1)
	Subsystem: ASUSTeK Computer Inc. GP108 [GeForce GT 1030] [1043:85f4]
	Kernel driver in use: nvidia
	Kernel modules: nvidia_drm, nvidia
09:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1)
	Subsystem: ASUSTeK Computer Inc. GP108 High Definition Audio Controller [1043:85f4]
...
43:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1)
	Subsystem: Gigabyte Technology Co., Ltd GA106 [GeForce RTX 3060 Lite Hash Rate] [1458:4096]
	Kernel driver in use: vfio-pci
	Kernel modules: nvidia_drm, nvidia
43:00.1 Audio device [0403]: NVIDIA Corporation GA106 High Definition Audio Controller [10de:228e] (rev a1)
	Subsystem: Gigabyte Technology Co., Ltd Device [1458:4096]
	Kernel driver in use: vfio-pci
44:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] GP108 [GeForce GT 1030] [1462:8c98]
	Kernel driver in use: nvidia
	Kernel modules: nvidia_drm, nvidia
44:00.1 Audio device [0403]: NVIDIA Corporation GP108 High Definition Audio Controller [10de:0fb8] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] GP108 High Definition Audio Controller [1462:8c98]

 

Nvidia RTX2070 Super: nvidia driver loaded

Nvidia GT1030: nvidia driver loaded

Nvidia RTX3060: bound to VFIO

Nvidia GT1030: nvidia driver loaded

 

So to speak, everything seems completely fine and the Nvidia Driver plugin lists the cards correctly.

 

In this Diagnostics I see that you have bound the RTX3060 to VFIO so to speak the Nvidia Driver plugin can't see it.

I don't know how you've bound it to VFIO because I don't see any indication why it should be bound to VFIO in your Diagnostics but the syslog shows that it was bound to VFIO on boot:

Aug 10 12:19:48 Server kernel: vfio-pci 0000:43:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=io+mem:owns=none

 

Again, please note that you're RTX 2070 Super won't show up if you've use it in a running VM, that is the default behaviour.

  • 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

I have a T600 and the plugin was working great until I upgraded to unraid 6.12.X. Along with my CPU fan dying a slow death, macvlan errors that triggered a cache drive failure and restoring my appdata, and some other "joys," I was also seeing my T600 "disappear" and getting GPU errors in my logs similar to what others have posted.

 

Oddly, I tried turning off the netdata docker, and also uninstalled/reinstalled the GPU Stats plugin, and so far my T600 seems more stable. Previously it would fail and "disappear" from unraid until a reboot if I ran Plex or something that hit the GPU. It's only been 24 hours but wanted to share in case this helps users and/or the plugin dev.

  • Author
27 minutes ago, Slappy said:

Previously it would fail and "disappear" from unraid until a reboot if I ran Plex or something that hit the GPU. It's only been 24 hours but wanted to share in case this helps users and/or the plugin dev.

Please always pull Diagnostics from your system if you encounter an error before you reboot and always include them in the Diagnostics.

54 minutes ago, ich777 said:

Please always pull Diagnostics from your system if you encounter an error before you reboot and always include them in the Diagnostics.

Usually some combination of my problems would completely destablize and/or hang the system, so I haven't been able to pull diagnostics. If it happens again (which I hope it will not) I'll pull diags.

I just upgraded to 6.12.3 from 6.12.2 and as soon as I did, my Plex container wouldn't start because of `--runtime=nvidia`. I checked my GPU stats and Nvidia driver and saw that it is showing no GPU. I have a RTX 3050 and a GT 1030 installed. Neither are showing up. Any ideas?

unraid-diagnostics-20230811-2352.zip

1 hour ago, robertpaolella said:

Neither are showing up. Any ideas?

your pcie device 41.... is vfio bound (GT 1030 Card), so thats normal like described on page 1 and already mentioned several times in this thread ;)

 

and you may dont use the other card in a VM too ?

I have an older card, I'd love to use it for transcoding in plex. 

it says it needs 390.xx Legacy drivers.

Do you have a quick set of commands to install this?

Why does it change driver version to "latest" after a system update, even if I had previously chosen "Production Branch"?

  • Author
4 hours ago, thankful-gown8633 said:

Do you have a quick set of commands to install this?

Why do you want to even do that?

The 390.xx series drivers are not capable to be used in Docker containers.

  • Author
16 minutes ago, erak said:

Why does it change driver version to "latest" after a system update, even if I had previously chosen "Production Branch"?

A bit more insight would be better.

Can you post your Diagnostics after this happened? What have you done exactly, are you on the legacy 470.xx series driver?

Did you wait for the Plugin Update Helper to finish before rebooting to the new version?

 

I really can't tell anything without more information.

  • Author
7 hours ago, robertpaolella said:

I just upgraded to 6.12.3 from 6.12.2 and as soon as I did

Please uninstall the Nvidia Driver plugin, reboot, install the Nvidia Driver Plugin again and reboot.

 

The driver package or better speaking the plugin is not installed correctly because I think you also didn't wait until the Plugin Update Helper told you that it's now safe to reboot (these are Notifications which are showing up after you trigger the update).

-rw------- 1 root root 132200960 Aug 11 16:32 nvidia-535.98-6.1.38-Unraid-1.txz

The above shows that the package was partially downloaded but not completely.

3 hours ago, ich777 said:

A bit more insight would be better.

Can you post your Diagnostics after this happened? What have you done exactly, are you on the legacy 470.xx series driver?

Did you wait for the Plugin Update Helper to finish before rebooting to the new version?

 

I really can't tell anything without more information.

I've been running unraid for about a year and I think this has happened almost every time, therefore I thought it was by design for some reason. Not using legacy, T600. Updated today from 6.12.2 to 6.12.3. I think I waited for the ok, but now I can't say for certain. But I usually do, and the version type change has happened anyway.

server-diagnostics-20230812-1909.zip

  • Author
43 minutes ago, erak said:

Updated today from 6.12.2 to 6.12.3. I think I waited for the ok, but now I can't say for certain.

I think you where waiting for the message which Unraid itself gives you to reboot but that changed in the last versions a bit.

After the download and everything from Unraid itself finished you should get messages that the Plugin Update Helper kicked in and it will notify when it's safe to reboot <- the Plugin Update Helper is my take on how to update third party plugins but since the messages now fading out with the new Unraid versions it's a little bit hard to catch them for the user.

 

The Plugin Update Helper also does account for the selected branch btw. ;)

 

The driver was not downloaded for the new Unraid version properly by the Plugin Update Helper that's why it falls back to the latest branch:

Aug 12 14:26:56 Micro-8 root: -----------------Downloading Nvidia Driver Package v535.98------------------
Aug 12 14:26:56 Micro-8 root: ----------This could take some time, please don't close this window!------------
Aug 12 14:27:25 Micro-8 root:
Aug 12 14:27:25 Micro-8 root: ----Successfully downloaded Nvidia Driver Package v535.98, please wait!----
Aug 12 14:27:27 Micro-8 root:
Aug 12 14:27:27 Micro-8 root: -----------------Installing Nvidia Driver Package v535.98-------------------

 

Sorry about that but maybe now that you are aware of the Plugin Update Helper you'll catch it next time. :)

 

The Nvidia Driver download will usually take about 30 seconds to the USB Flash device after the Plugin Update Helper kicked in (about 200MB).

 

Hope that explains it a bit better.

Hi, probably been brought up before but I think the lower power state would be a good thing to be built into the plugin when possible:

 

PS. Great work on this as usual!

 

Edited by Necrotic

  • Author
4 hours ago, Necrotic said:

but I think the lower power state would be a good thing to be built into the plugin when possible

Thanks for the recommendation but I won‘t do that because this can be also be quite dangerous since if one is using a card for Docker and a VM this would crash the server and it would be really hard for me to detect if one is doing that.

 

The simplest way of enabling persistemced mode is putting this line in the go file:

nvidia-persistenced


If you want to end the process do something like that:

kill $(pidof nvidia-persistenced)

 

31 minutes ago, ich777 said:

Thanks for the recommendation but I won‘t do that because this can be also be quite dangerous since if one is using a card for Docker and a VM this would crash the server and it would be really hard for me to detect if one is doing that.

 

The simplest way of enabling persistemced mode is putting this line in the go file:

nvidia-persistenced


If you want to end the process do something like that:

kill $(pidof nvidia-persistenced)

 

I get it, maybe not a default setting but an option with a giant warning all over it would be enough.

In any case, great job with this and the other stuff, I still use the gameservers :P

  • Author
5 hours ago, Necrotic said:

maybe not a default setting but an option with a giant warning all over it would be enough.

Sorry but no, I don't think that I want to integrate that because there will be too many variables. For example when a user does enable this and forget about this and then he tries to boot a VM with the GPU passed through the server will ultimately crash and then nobody will know why that happens, even if he uploads Diagnostics no one will be able to see it what was the cause of this issue.

 

I think one line in the go file is even for a Linux newbie doable. :)

This is for an RTX 4060.  I am having an issue where my GPU is stating I have persistenced enabled but it appears to not be working.  I followed spaceinvaderone's video and as you can see the script is working.  The GPU works when transcoding in plex. However before and after running persistenced the GPU shows a wattage of 50w/115w.  It does not appear to be doing anything for the GPU even thought the GPU shows a state of P8.  It should be much lower on the wattage.  I'm currently using the latest driver. Does this sound like a bad driver issue? Is there a driver we know that works better or could it be because of how new the rtx 4060 is?

Screenshot 2023-08-12 at 12.07.56 PM.png

Screenshot 2023-08-12 at 12.08.58 PM.png

Screenshot 2023-08-13 at 7.46.51 AM.png

1 hour ago, FlyingTexan said:

This is for an RTX 4060.  I am having an issue where my GPU is stating I have persistenced enabled but it appears to not be working.  I followed spaceinvaderone's video and as you can see the script is working.  The GPU works when transcoding in plex. However before and after running persistenced the GPU shows a wattage of 50w/115w.  It does not appear to be doing anything for the GPU even thought the GPU shows a state of P8.  It should be much lower on the wattage.  I'm currently using the latest driver. Does this sound like a bad driver issue? Is there a driver we know that works better or could it be because of how new the rtx 4060 is?

Screenshot 2023-08-12 at 12.07.56 PM.png

Screenshot 2023-08-12 at 12.08.58 PM.png

Screenshot 2023-08-13 at 7.46.51 AM.png

Is there a reason why you are using the open source driver not latest?

 

image.png

 

Also have you followed

 

image.png

9 minutes ago, SimonF said:

Is there a reason why you are using the open source driver not latest?

 

image.png

 

Also have you followed

 

image.png

 

It doesn't show that as open source for me. It shows that as the latest.   I checked under plugins and it says the plugin is up-to-date as of 07-02-2023. Why would it show differently then what you are seeing?1609501965_Screenshot2023-08-13at9_23_31AM.thumb.png.7e4edaeb150ada1b6bd3af3aa67a2411.png

 

Edited by FlyingTexan

  • Author
1 hour ago, FlyingTexan said:

RTX 4060.  I am having an issue where my GPU

Have you yet measured how much it draws from the wall?

RTX 40 series are known to report the wrong power draw in nvidia-smi.

 

Please, please don't trust software readings they might be off by a lot in some cases.

 

Also please use nvidia-persistenced instead of the script since if you put nvidia-persistenced in the go file it is enough and doesn't need to be ran in intervals, the reason why I recommend nvidia-persistenced is because the documentation from Nvidia states that persistence mode from nvidia-smi is soon to be removed <- who knows how long the leave it in...

2 minutes ago, ich777 said:

Have you yet measured how much it draws from the wall?

RTX 40 series are known to report the wrong power draw in nvidia-smi.

 

Please, please don't trust software readings they might be off by a lot in some cases.

 

Also please use nvidia-persistenced instead of the script since if you put nvidia-persistenced in the go file it is enough and doesn't need to be ran in intervals, the reason why I recommend nvidia-persistenced is because the documentation from Nvidia states that persistence mode from nvidia-smi is soon to be removed <- who knows how long the leave it in...

My system idle seems to support the measurement. With the dockers off and array down I still draw around 120w.  I don't understand your next statement about the user script.  If nvidia-persistenced is in the script what does it matter? It doesn't hurt to run the command again does it? I'm confused on what it is that should be done differenlty.

  • Author
10 minutes ago, FlyingTexan said:

Why would it show differently then what you are seeing?

@SimonF or I can tell more without your Diagnostics, but as already mentioned in the previous post don't trust software readouts:

 

12 minutes ago, FlyingTexan said:

 

It doesn't show that as open source for me. It shows that as the latest.   I checked under plugins and it says the plugin is up-to-date as of 07-02-2023. Why would it show differently then what you are seeing?1609501965_Screenshot2023-08-13at9_23_31AM.thumb.png.7e4edaeb150ada1b6bd3af3aa67a2411.png

 

My plugin vers is 2023.07.06 Also maybe OS level related, currently I am on 6.12.3

  • Author
1 minute ago, FlyingTexan said:

My system idle seems to support the measurement. With the dockers off and array down I still draw around 120w.

Again, I don't know anything about your system without the Diagnostics. :)

 

1 minute ago, FlyingTexan said:

I'm confused on what it is that should be done differenlty.

Remove the script and just put nvidia-persistenced in your go file. ;)

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.