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

10 minutes ago, ich777 said:

In your screenshot I see this:

grafik.thumb.png.a0219a8dc61e5384db5c41e5eb2f4966.png

 

This is a indication of a corrupt installation from the Nvidia Driver plugin, to fix this do the following:

  1. Uninstall the Nvidia Driver plugin
  2. Reboot
  3. Pull a fresh copy from the Nvidia Driver plugin from the CA App
  4. Reboot (or restart the Docker service)

Perfect TYVM

Looks good now

thank you for the swift response 

image.thumb.png.e8439f37f8608e0893672c24bf6f0339.png

Edited by Fiservedpi

  • 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

**Update** out of no where it just decided to work.... I tried it and it finally installed... didnt change anything.

 

I currently made a mistake and uninstalled my working version of Nvidia-driver 550.78.x because it told me to manually download 550.90.x and now i get this error message:

plugin: installing: nvidia-driver.plg Executing hook script: pre_plugin_checks plugin: downloading: nvidia-driver.plg ... done 
plugin: downloading: nvidia-driver-2024.01.19.txz ... done 

+============================================================================== | 
Skipping package nvidia-driver-2024.01.19 (already installed) 
+============================================================================== 
-----ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR - ERROR------ 
---Can't get latest Nvidia driver version and found no installed local driver--- 

plugin: run failed: '/bin/bash' returned 1
Executing hook script: gui_search_post_hook.sh
Executing hook script: post_plugin_checks

 

Edited by thesr5

  • Author
4 hours ago, thesr5 said:

now i get this error message

Please post a screenshot from the Nvidia Driver settings page.

  • Author
6 hours ago, thesr5 said:

**Update** out of no where it just decided to work.... I tried it and it finally installed... didnt change anything.

This is most certainly because your server was for whatever reason not able to communicate with the GitHub API, may I ask if you have PiAlert running on your server since it was (or maybe is still) known to cause issues because it uses all the free 60 GitHub API per hour in a really short amount of time.

Unable to call gpu using plex on unraid 7.0

21 minutes ago, Gouryella said:

Unable to call gpu using plex on unraid 7.0

very helpful ...

 

may at least some infos like hardware, wgich plex docker, lxc, vm, ... install ...

 

may also add your diagnostics ...

6 minutes ago, alturismo said:

very helpful ...

 

may at least some infos like hardware, wgich plex docker, lxc, vm, ... install ...

 

may also add your diagnostics ...

already done! problem solved!

Hello, i've just realized my gpu is not being recognized anymore in UNRAID, this is what i seeimage.thumb.png.5412edca9ec9feff608b20e503bbcfa9.png

 

If i click on "Update & Download" i get this message:

image.png.f121d77924ae86e5cba19a9fcff795d5.png

 

how can i solve it? I've tried restarting the server to see if it was going to dowload an update but nothing, if it matters my gpu is a P4000. 
Nedless to say i obviously have (had?) the nvidia drivers installed and everything was working fine.

Edited by Bahamut___

  • Author
1 hour ago, Bahamut___ said:

Hello, i've just realized my gpu is not being recognized anymore in UNRAID, this is what i see

Please post your Diagnostics.

  • Author
19 minutes ago, Bahamut___ said:

Here, i forgot to attach that

I think something with your network is wrong since Unraid even can't grab the latest versions from your plugins:

Could not download current plugin versions

community.applications.plg - 2024.06.08a
dynamix.unraid.net.plg - 2024.05.15.1138
fix.common.problems.plg - 2024.05.04
gpustat.plg - 2024.06.21
NerdTools.plg - 2024.02.17
nut-dw.plg - 2024.06.23
nvidia-driver.plg - 2024.01.19
rclone.plg - 2024.05.27
unbalanced.plg - 2024.03.26
unRAIDServer.plg - 6.12.10
user.scripts.plg - 2024.03.29

 

I see a lot of these messages in your syslog:

...
Jul  2 12:10:56 Tower kernel: eth0: renamed from vethe3bbea7
Jul  2 12:11:04 Tower kernel: vethe3bbea7: renamed from eth0
Jul  2 12:11:04 Tower kernel: eth0: renamed from veth5e7f227
Jul  2 12:11:06 Tower kernel: veth5e7f227: renamed from eth0
Jul  2 12:11:07 Tower kernel: eth0: renamed from vethb315cdc
Jul  2 12:11:08 Tower kernel: vethb315cdc: renamed from eth0
Jul  2 12:11:09 Tower kernel: eth0: renamed from veth6e05170
...

 

 

Have you yet tried to reboot?

I don't think that the Nvidia Driver plugin is the issue here.

Um I'm sure I'm not the frost but I did a thing then read this post after is there anyway to reset the hard lock I had gpu running dockers and then with a VM off decided to add it to the vm never started the vm and been going crazy as to why it's not working in my dockers anymore and seems like I must have hard locked it

  • Author
3 minutes ago, EvoX008 said:

Um I'm sure I'm not the frost but I did a thing then read this post after is there anyway to reset the hard lock I had gpu running dockers and then with a VM off decided to add it to the vm never started the vm and been going crazy as to why it's not working in my dockers anymore and seems like I must have hard locked it

I'm really not sure what the issue is, are you really sure that the GPU hard locked or did the server hard lock?

Did you maybe bound the card to VIFO?

 

Can you please post your Diagnostics?

I see the GPU under system devices

i see it as a option under VM 

i can also see it under GPU STATISTICS plugin

but it does not show up in the Nvidia Drivers plugin

cloud-diagnostics-20240703-0107.zip

  • Author
9 minutes ago, EvoX008 said:

but it does not show up in the Nvidia Drivers plugin

This is caused because the GPU doesn't initialize correctly (from your syslog) :

Jul  3 01:04:56 Cloud kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x65:2477)
Jul  3 01:04:56 Cloud kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

I would recommend the following steps:

  • Update your BIOS (your BIOS is from 2015 and the newest one is from 2018)
  • Enable Above 4G Decoding in your BIOS (some manufacturers also use something like: "Support for large address space" in the PCI options)
  • Enable (if your BIOS has the option) Resizabel BAR
  • Try to boot in Legacy Mode instead of UEFI

 

Sadly enough some older Motherboards are not fully compatible with new GPUs and have some Firmware (BIOS) issues that will prevent the card from properly working, however I would recommend to first try the steps from above and see if you can get it to work.

Just now, ich777 said:

This is caused because the GPU doesn't initialize correctly:

Jul  3 01:04:56 Cloud kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x62:0x65:2477)
Jul  3 01:04:56 Cloud kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

I would recommend the following steps:

  • Update your BIOS (your BIOS is from 2015 and the newest one is from 2018)
  • Enable Above 4G Decoding in your BIOS
  • Enable (if your BIOS has the option) Resizabel BAR
  • Try to boot in Legacy Mode instead of UEFI

 

lol i just updated the bios i was running a 2014 but wasn't sure about the 2018 because it says beta but ill go for it and check out those other things 

10 hours ago, ich777 said:

I think something with your network is wrong since Unraid even can't grab the latest versions from your plugins:

Could not download current plugin versions

community.applications.plg - 2024.06.08a
dynamix.unraid.net.plg - 2024.05.15.1138
fix.common.problems.plg - 2024.05.04
gpustat.plg - 2024.06.21
NerdTools.plg - 2024.02.17
nut-dw.plg - 2024.06.23
nvidia-driver.plg - 2024.01.19
rclone.plg - 2024.05.27
unbalanced.plg - 2024.03.26
unRAIDServer.plg - 6.12.10
user.scripts.plg - 2024.03.29

 

I see a lot of these messages in your syslog:

...
Jul  2 12:10:56 Tower kernel: eth0: renamed from vethe3bbea7
Jul  2 12:11:04 Tower kernel: vethe3bbea7: renamed from eth0
Jul  2 12:11:04 Tower kernel: eth0: renamed from veth5e7f227
Jul  2 12:11:06 Tower kernel: veth5e7f227: renamed from eth0
Jul  2 12:11:07 Tower kernel: eth0: renamed from vethb315cdc
Jul  2 12:11:08 Tower kernel: vethb315cdc: renamed from eth0
Jul  2 12:11:09 Tower kernel: eth0: renamed from veth6e05170
...

 

 

Have you yet tried to reboot?

I don't think that the Nvidia Driver plugin is the issue here.


Seems like a "double reboot" fixed the issue, don't know if the network stuff is related to some operations i was doing on a container but everything else was working fine that i could see. Thanks a lot for the help anyway 🙏

7 hours ago, EvoX008 said:

 

lol i just updated the bios i was running a 2014 but wasn't sure about the 2018 because it says beta but ill go for it and check out those other things 

Got it working did the BIOS update and 4G Decoding 

Didn't see a option for resize rebar but got it back working thanks for the quick response I really appreciate it I would have been beating my head against the wall all night it was already like 2pm

On 6/5/2024 at 10:39 PM, ich777 said:

I see that but I really don't know why it fails on your machine.

The way the check works is that it checks for updates between 8 and 10 am by getting the latest version for the branch that is selected and if a newer version is found what you are using it is pulled down and message is sent to the user that the new driver is download.

 

The message that you see is generated when the download from the driver fails.

 

Please note that the driver needs about 250MB of free space on your USB Boot device.

BTW, you have a lot of FSCK files on your boot device, this indicates an issue with your USB Boot device however this is out of the scope from this thread.

Updates are still failing to automatically download. Just happened again with v550.100. Works perfectly fine if I download manually. Should I try reinstalling the plugin?

Hi,

 

Hope you can help.

 

I have an Nvidia 1050 TI, but none of the drivers work, even though it is listed as supported.

 

Here is an extract from my logs:

Jul  9 21:23:58 Lofty kernel: nvidia: loading out-of-tree module taints kernel.
Jul  9 21:23:58 Lofty kernel: nvidia: module license 'NVIDIA' taints kernel.
Jul  9 21:23:58 Lofty kernel: Disabling lock debugging due to kernel taint
Jul  9 21:23:58 Lofty kernel: AES CTR mode by8 optimization enabled
Jul  9 21:23:58 Lofty kernel: [drm] Initialized mgag200 1.0.0 20110418 for 0000:01:00.1 on minor 0
Jul  9 21:23:58 Lofty kernel: fbcon: mgag200drmfb (fb0) is primary device
Jul  9 21:23:58 Lofty kernel: BTRFS: device fsid ab17ef47-9a14-4f2a-975b-53afb10fcaf5 devid 1 transid 15717 /dev/sdd1 scanned by udevd (888)
Jul  9 21:23:58 Lofty kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244
Jul  9 21:23:58 Lofty kernel: 
Jul  9 21:23:58 Lofty kernel: nvidia 0000:04:00.0: enabling device (0040 -> 0043)
Jul  9 21:23:58 Lofty kernel: nvidia 0000:04:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
Jul  9 21:23:58 Lofty kernel: NVRM: The NVIDIA GPU 0000:04:00.0 (PCI ID: 10de:1c82)
Jul  9 21:23:58 Lofty kernel: NVRM: installed in this system is not supported by the
Jul  9 21:23:58 Lofty kernel: NVRM: NVIDIA 470.239.06 driver release.
Jul  9 21:23:58 Lofty kernel: NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products'
Jul  9 21:23:58 Lofty kernel: NVRM: in this release's README, available on the operating system
Jul  9 21:23:58 Lofty kernel: NVRM: specific graphics driver download page at www.nvidia.com.
Jul  9 21:23:58 Lofty kernel: nvidia: probe of 0000:04:00.0 failed with error -1
Jul  9 21:23:58 Lofty kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).
Jul  9 21:23:58 Lofty kernel: NVRM: None of the NVIDIA devices were initialized.
Jul  9 21:23:58 Lofty kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 244
Jul  9 21:23:58 Lofty kernel: Console: switching to colour frame buffer device 128x48
Jul  9 21:23:58 Lofty kernel: mgag200 0000:01:00.1: [drm] fb0: mgag200drmfb frame buffer device
Jul  9 21:23:58 Lofty kernel: sr 5:0:0:0: [sr0] scsi3-mmc drive: 40x/12x writer dvd-ram cd/rw xa/form2 cdda tray
Jul  9 21:23:58 Lofty kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Jul  9 21:23:58 Lofty kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244
Jul  9 21:23:58 Lofty kernel: 
Jul  9 21:23:58 Lofty kernel: nvidia 0000:04:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none
Jul  9 21:23:58 Lofty kernel: NVRM: The NVIDIA GPU 0000:04:00.0 (PCI ID: 10de:1c82)
Jul  9 21:23:58 Lofty kernel: NVRM: installed in this system is not supported by the
Jul  9 21:23:58 Lofty kernel: NVRM: NVIDIA 470.239.06 driver release.
Jul  9 21:23:58 Lofty kernel: NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products'
Jul  9 21:23:58 Lofty kernel: NVRM: in this release's README, available on the operating system
Jul  9 21:23:58 Lofty kernel: NVRM: specific graphics driver download page at www.nvidia.com.
Jul  9 21:23:58 Lofty kernel: sr 5:0:0:0: Attached scsi CD-ROM sr0
Jul  9 21:23:58 Lofty kernel: nvidia: probe of 0000:04:00.0 failed with error -1
Jul  9 21:23:58 Lofty kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).
Jul  9 21:23:58 Lofty kernel: NVRM: None of the NVIDIA devices were initialized.

 

image.thumb.png.1179c9d4fdcb502d9d2b7cf59b508d1e.png

04:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1)
        Kernel modules: nvidia_drm, nvidia
04:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1)

The logs indicated that the GPU is not supported, but from what I can see the 1050 TI is supported still by these drivers?

Ive tried the latest Production and earliest drivers available in the plugin.

 

Any suggestions?

 

Thanks in advance

  • Author
1 hour ago, shiftylilbastrd said:

Should I try reinstalling the plugin?

No.

 

1 hour ago, shiftylilbastrd said:

Updates are still failing to automatically download. Just happened again with v550.100. Works perfectly fine if I download manually.

Are you sure that your sever time is correct? I will have to wait until tomorrow morning and see if my test server pulls the updated automatically (last time it did).

 

May I ask for what do you use the card in your server?

  • Author
48 minutes ago, Tom Sealey said:

I have an Nvidia 1050 TI, but none of the drivers work, even though it is listed as supported.

Please always include your Diagnostics.

 

However it seems I got bad news for you... Your card is based on:

48 minutes ago, Tom Sealey said:
GF116

And GF116 is a Fermi 2.0 based card (more information on Fermi here), so to speak GTS 4xx and 5xx series and not Pascal based like a GTX1050Ti should be, this means you got a counterfeit card.

 

How much did you pay for the card? I hope you have an option to return it.

 

I would recommend that you want to use the card for transcoding only you look into a Nvidia T400, it you should be able to get it for under $ 100,- , it is really power efficient (only a max. of 35W) and is enough for 3 to 4 simultaneous 4K transcodes (depending on bitrate and so on).

2 hours ago, ich777 said:

May I ask for what do you use the card in your server?

It's used for Plex transcoding. Just double checked server time and it's correct.

Edited by shiftylilbastrd
Adding info

  • Author
6 hours ago, shiftylilbastrd said:

It's used for Plex transcoding. Just double checked server time and it's correct.

TBH, if you got trouble with the update check disable it because if you just use the card fro transcoding the driver updates won't do much for you anyways.

 

You have to wait a bit longer until my Test Server checks for updates so that I can see if my Server pulls the update.

 

EDIT: I found and fixed a bug in the update check for Production and New Feature Branch, please update the plugin, it should work next time if Latest Production or New Feature Branch is selected.

Thanks @ich777.

 

I bought it on Ebay as new but unused...

 

8 hours ago, ich777 said:

Your card is based on: GF116

And GF116 is a Fermi 2.0 based card (more information on Fermi here), so to speak GTS 4xx and 5xx series and not Pascal based like a GTX1050Ti should be, this means you got a counterfeit card.

 

 

I did wonder if it was fake, but the pci id seemed right, and the line above says GP107, so I thought it was legit. Missed checking the audio driver line.

 

I'll complain to ebay, I might get my money back...

Thanks for the help.

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.