[Plugin] Nvidia-Driver


ich777

Recommended Posts

On 4/25/2022 at 5:01 PM, ich777 said:

No, because there is no benefit of doing so...

What is your usecase? The @SpaceInvaderOne video to save power draw or do you want to use it for your Docker containers?

 

This card was released in 2009 from what I see and can't be used for Docker containers also nvidia-persistenced works completely different (it is part of nvidia-smi in those old drivers) on those old cards and won't save much power.

 

Also see this answer:

 

 

 

Hi,

forget my question! I bought a Nvidia GTX 1050TI! With it everything works!

I wanted to set hardware transcoding in Docker/Jellyfin! That works now!

Thanks anyway for the answers!

Greetings Bernd

 

  • Like 1
Link to comment

 
Hello All,

A few weeks ago after my server rebooted I have been unable to utilize the nvidia plugin. When ever I click on the plugin my gui gets stuck in a loading loop and eventually times out. Once this happens I either have to open the unraid gui in a new browser or restart my server. I have tried uninstalling the plug in as well as upgrading to version Version 6.10.0-rc5. I have also deleted the plugin from using the cli as well as using the following commands before installing 

mkdir -p /boot/config/plugins/nvidia-driver

echo 'first_installation=true driver_version=latest local_version=none disable_xconfig=false update_check=true' > "/boot/config/plugins/nvidia-driver/settings.cfg"

 

I can see my p2000 in my sys devices profile

 

 

Any help would greatly be appreciated. 

 

Capture.PNG

skynet-diagnostics-20220503-1639.zip

Link to comment
9 hours ago, johnconnor said:

Once this happens I either have to open the unraid gui in a new browser or restart my server.

You get a Kernel panic from what I see in the logs. Have you changed anything in the BIOS or did you do any hardware change?

 

Is it possible for you to put the card in another system, install the drivers and put some 3D load like Unigine Heaven or any other 3D benchmark?

Link to comment
10 hours ago, ich777 said:

You get a Kernel panic from what I see in the logs. Have you changed anything in the BIOS or did you do any hardware change?

 

Is it possible for you to put the card in another system, install the drivers and put some 3D load like Unigine Heaven or any other 3D benchmark?

 

The only change I've made was to install new ram but I have since put the old ram back in as I was having issues. I don't have access to any other machines to run a benchmark on it. I'm wondering if the card is dead then?

Link to comment
56 minutes ago, johnconnor said:

I'm wondering if the card is dead then?

It is maybe possible but if you can‘t test it in another machine it can get a bit difficult diagnosing this.

 

Do you have a second PCIe slot in your server? Maybe try to change the slot if possible.

Link to comment

Whenever the unraid os is updated I get a couple of emails I think from this plugin. First is to wait while the nvidia driver updates. Second is the "all done". Third has a subject line "output from your job 3".

Quote


/boot/config/plugin 0%[ ] 0 --.-KB/s 
/boot/config/plugin 1%[ ] 2.79M 13.9MB/s 
/boot/config/plugin 2%[ ] 6.86M 17.1MB/s 
/boot/config/plugin 4%[ ] 11.96M 18.4MB/s 
/boot/config/plugin 6%[> ] 16.61M 19.3MB/s 
/boot/config/plugin 8%[> ] 21.37M 20.2MB/s 
/boot/config/plugin 10%[=> ] 26.08M 20.7MB/s 
/boot/config/plugin 13%[=> ] 31.43M 21.5MB/s 
/boot/config/plugin 15%[==> ] 36.78M 22.1MB/s 
/boot/config/plugin 17%[==> ] 42.14M 22.6MB/s 
/boot/config/plugin 19%[==> ] 47.12M 22.8MB/s 
/boot/config/plugin 21%[===> ] 52.13M 23.0MB/s 
/boot/config/plugin 23%[===> ] 57.29M 23.2MB/s 
/boot/config/plugin 25%[====> ] 61.52M 23.1MB/s 
/boot/config/plugin 27%[====> ] 65.98M 23.0MB/s 
/boot/config/plugin 29%[====> ] 71.33M 23.3MB/s eta 7s 
/boot/config/plugin 31%[=====> ] 76.05M 23.9MB/s eta 7s 
/boot/config/plugin 33%[=====> ] 81.07M 24.2MB/s eta 7s 
/boot/config/plugin 33%[=====> ] 81.09M 18.2MB/s eta 9s 
/boot/config/plugin 40%[=======> ] 96.04M 21.0MB/s eta 9s 
/boot/config/plugin 42%[=======> ] 101.12M 20.9MB/s eta 9s 
/boot/config/plugin 44%[=======> ] 106.28M 21.4MB/s eta 9s 
/boot/config/plugin 45%[========> ] 110.33M 21.1MB/s eta 9s 
/boot/config/plugin 47%[========> ] 114.45M 20.8MB/s eta 6s 
/boot/config/plugin 49%[========> ] 119.53M 20.6MB/s eta 6s 
/boot/config/plugin 51%[=========> ] 123.62M 20.4MB/s eta 6s 
/boot/config/plugin 53%[=========> ] 128.34M 20.4MB/s eta 6s 
/boot/config/plugin 55%[==========> ] 132.76M 20.1MB/s eta 6s 
/boot/config/plugin 57%[==========> ] 137.26M 20.0MB/s eta 5s 
/boot/config/plugin 59%[==========> ] 141.99M 20.1MB/s eta 5s 
/boot/config/plugin 60%[===========> ] 145.66M 19.9MB/s eta 5s 
/boot/config/plugin 62%[===========> ] 150.10M 19.7MB/s eta 5s 
/boot/config/plugin 64%[===========> ] 155.39M 19.9MB/s eta 5s 
/boot/config/plugin 66%[============> ] 160.57M 26.3MB/s eta 4s 
/boot/config/plugin 68%[============> ] 164.63M 22.8MB/s eta 4s 
/boot/config/plugin 69%[============> ] 168.06M 22.2MB/s eta 4s 
/boot/config/plugin 71%[=============> ] 171.74M 21.7MB/s eta 4s 
/boot/config/plugin 73%[=============> ] 175.99M 21.7MB/s eta 4s 
/boot/config/plugin 75%[==============> ] 180.42M 21.8MB/s eta 3s 
/boot/config/plugin 76%[==============> ] 184.80M 21.6MB/s eta 3s 
/boot/config/plugin 79%[==============> ] 190.15M 22.0MB/s eta 3s 
/boot/config/plugin 81%[===============> ] 195.31M 22.2MB/s eta 3s 
/boot/config/plugin 83%[===============> ] 200.65M 22.5MB/s eta 3s 
/boot/config/plugin 85%[================> ] 205.64M 22.6MB/s eta 2s 
/boot/config/plugin 87%[================> ] 210.28M 22.7MB/s eta 2s 
/boot/config/plugin 89%[================> ] 214.39M 22.8MB/s eta 2s 
/boot/config/plugin 91%[=================> ] 218.86M 22.7MB/s eta 2s 
/boot/config/plugin 93%[=================> ] 224.18M 23.0MB/s eta 2s 
/boot/config/plugin 95%[==================> ] 229.25M 22.9MB/s eta 0s 
/boot/config/plugin 96%[==================> ] 232.32M 22.4MB/s eta 0s 
/boot/config/plugin 97%[==================> ] 235.21M 22.1MB/s eta 0s 
/boot/config/plugin 99%[==================> ] 237.82M 22.0MB/s eta 0s 
/boot/config/plugin 100%[===================>] 240.09M 21.7MB/s in 11s

 

I'm not sure if this is associated with the driver update or not? If it is would it be possible to not send this notification? I doubt it really matters but seems like a waste.

Link to comment
5 hours ago, wgstarks said:

Whenever the unraid os is updated I get a couple of emails I think from this plugin.

You should get about three messages (but not only from this plugin, depends on how many plugins you have installed that requires Kernel modules):

  1. To wait until everything is downloaded
  2. That the driver for the plugin is downloaded
  3. That it is now safe to reboot
5 hours ago, wgstarks said:

Third has a subject line "output from your job 3".

This message I can maybe hide or suppress so that you don't receive a mail.

 

 

I won't remove this feature because this is very helpful for people who doesn't have a active internet connection on boot because they run PfSense or some kind of firewall virtualized on Unraid or have some kind of AdBlocking DNS server also provided to Unraid so the driver won't download on boot.

 

However about what I can think of is to turn the Plugin Update Helper completely but keep in mind then the boot process will take much longer because the plugin(s) is/are downloaded on boot and I've already had some people pulling their USB Boot device because they thought something funky was going on because the Drive was blinking...

 

The next thing is that disabling the messages is also pretty bad because how will you know when the plugin is downloaded or how will you know when it has even started?

Imagine this, somebody clicks updated, and reboots instantly and the Plugin Update Helper is working in background, this could ultimately lead to further issues that the plugin will recognize that there is already a download for the new Kernel there but it is cut of because the reboot was initiated to early...

 

Hope that makes sense to you.

What are your opinions on that?

Link to comment
58 minutes ago, wgstarks said:

Was just complaining about the progress message.😁

Its really not an issue though. Just seems unnecessary.

I know this is a bit odd and I think you only get these messages when you‘ve enabled Email notifications.

A workaround would be to use Pushover or Discord but I will look into this.

 

@Squid is it possible that the ouptut from wget get‘s sent out to the user like in this case per Mail like the „at now“ messages?

Link to comment
1 hour ago, ich777 said:

is it possible that the ouptut from wget get‘s sent out to the user like in this case per Mail like the „at now“ messages?

you need to include -M on the at command to have it not send out a notification

  • Like 1
Link to comment

Anyone got an idea why my P400 is not recognized with the latest Production Branch driver v510.68.02?

The info section in the plugin screen remains empty and plex and tdarr won't see the card either (of course).

Rolling back to v470.94 and everything is working again.

Since this is a Pascal based card which still is fully supported by NVIDIA and the latest Linux drivers on their webpage are also the v510.68.02, I am wondering what the problem is?!

Link to comment
39 minutes ago, FEF said:

Had the same problem. Kernel panic related to the nvidia drivers after update them.

What issue?

Do you have a screenshot, Diagnostics, or anything?

I can't diagnose anything without anything, driver version, Kernel panic, Unraid version...?

 

EDIT: @disco4000 & @FEF Tested it now on my test machine and seems like there are no issues whatsoever:

image.thumb.png.288017d7b478cbbf0613a8ea322b5205.png

Link to comment
1 hour ago, ich777 said:

Do you have a screenshot, Diagnostics, or anything?

Sorry, didn't save any since I needed the problem fixed asap. just posted to share the issue.

 

The only thing that i saved from system logs is this:

Quote

kernel: CPU: 6 PID: 14293 Comm: nvidia-container Tainted: P O 5.10.28-Unraid #1

not sure if it helps tho.

 

EDITED: my graphics card is a nvidia P2000

Edited by FEF
Link to comment
16 minutes ago, FEF said:

kernel: CPU: 6 PID: 14293 Comm: nvidia-container Tainted: P O 5.10.28-Unraid #1

Not really. This can also be caused by a container but this is only a guess...

 

As said above, tested the driver and transcoding on my Nvidia T400 with three concurrent streams is working just fine.

Link to comment

Hey,

So I just saw in the news;

NVIDIA is now publishing Linux GPU kernel modules as open source with dual GPL/MIT license, starting with the R515 driver release. You can find the source code for these kernel modules in the NVIDIA Open GPU Kernel Modules repo on GitHub
Source: https://videocardz.com/press-release/nvidia-releases-open-source-gpu-kernel-for-linux

GitHub: https://github.com/NVIDIA/open-gpu-kernel-modules

Don't know how much it will help the unraid community but considering the amount of issues I have had with NVIDA & unraid over the years I hope it does :)

Link to comment

Trying to figure out why I am getting this SMI error.

I have tried to a uninstall of the plugin and reinstall of the plugin this did not help.  With reboot in between removal and adding  of th nvidia plugin

 

The tools system devices  list shows the card is there.

 

10de:128b] 03:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)

 

 

 

 

 

---------------------------------------------------

Results below

plugin: removing: nvidia-driver.plg
----------------------------------------
---Uninstalling Nvidia driver package---
----------------------------------------
Removing package: nvidia-driver-2022.05.06
Removing files:
--> Deleting /usr/local/emhttp/plugins/nvidia-driver/images/nvidia-driver.png
--> Deleting /usr/local/emhttp/plugins/nvidia-driver/include/download.sh
--> Deleting /usr/local/emhttp/plugins/nvidia-driver/include/exec.sh
--> Deleting /usr/local/emhttp/plugins/nvidia-driver/include/update-check.sh
--> Deleting /usr/local/emhttp/plugins/nvidia-driver/nvidia-driver.page
--> Deleting empty directory /usr/local/emhttp/plugins/nvidia-driver/include/
--> Deleting empty directory /usr/local/emhttp/plugins/nvidia-driver/images/
WARNING: Unique directory /usr/local/emhttp/plugins/nvidia-driver/ contains new files


/boot/config/plugins/nvidia-driver/nvidia-driver-2022.05.06.txz

plugin: installing: https://github.com/ich777/unraid-nvidia-driver/raw/master/nvidia-driver.plg
plugin: downloading https://github.com/ich777/unraid-nvidia-driver/raw/master/nvidia-driver.plg
plugin: downloading: https://github.com/ich777/unraid-nvidia-driver/raw/master/nvidia-driver.plg ... done
plugin: downloading: https://github.com/ich777/unraid-nvidia-driver/raw/master/packages/nvidia-driver-2022.05.06.txz ... done

+==============================================================================
| Installing new package /boot/config/plugins/nvidia-driver/nvidia-driver-2022.05.06.txz
+==============================================================================

Verifying package nvidia-driver-2022.05.06.txz.
Installing package nvidia-driver-2022.05.06.txz:
PACKAGE DESCRIPTION:
Package nvidia-driver-2022.05.06.txz installed.

+==============================================================================
| WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
|
| Don't close this window with the red 'X' in the top right corner until the 'DONE' button is displayed!
|
| WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
+==============================================================================

-----------------Downloading Nvidia Driver Package v515.43.04------------------
----------This could take some time, please don't close this window!------------

----Successfully downloaded Nvidia Driver Package v515.43.04, please wait!----

-----------------Installing Nvidia Driver Package v515.43.04-------------------

------------Installation of Nvidia driver v515.43.04 successful----------------

Please make sure to disable and enable Docker if you installed the Nvidia driver for the first time! Settings -> Docker -> Enable Docker 'No' -> Apply -> Enable Docker 'Yes' -> Apply
plugin: nvidia-driver.plg installed

Updating Support Links

Finished Installing. If the DONE button did not appear, then you will need to click the red X in the top right corner
 

 

 

nvidia-driver-pluggin-pic.png

nvidia-smi-pic-no-driver.png

bryunraid-diagnostics-20220513-1741.zip

Edited by whynot88
added diags
Link to comment
1 hour ago, whynot88 said:

10de:128b] 03:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)

Exactly as @alturismo said, your card is too old for this driver version...

You have to select driver version 470.94 (this is the last driver that supports this card), click Updated, click on the Download button, wait for it to finish and reboot.

Link to comment
4 hours ago, Raider_M said:

Don't know how much it will help the unraid community but considering the amount of issues I have had with NVIDA & unraid over the years I hope it does :)

There is not much benefit currently from this because this driver only supports Ampere and Turing cards.

On top of that you have to install the closed source software so that you can even use it in your Docker containers.

  • Thanks 1
Link to comment

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...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.