Hey, sorry if this has been answered already but I couldn't find an answer; does removing this plugin uninstall the drivers if I ever wanted at some point to use a GPU in a VM? If not, how could I go about doing that?

2 hours ago, KyleMcQueen said:

does removing this plugin uninstall the drivers if I ever wanted at some point to use a GPU in a VM?

Yes, but you have to reboot too to completely uninstall the plugin, this is also what the pop up tells you to when you remove it.

10 hours ago, Dbudd424 said:

I can leave the window up for hours and it never finishes installing. 

Something really strange is going on here and really can't tell what the cause of this issue is.

 

Please try this:

1. Remove the plugin
2. Execute: rm -rf /boot/config/plugins/nvidia-driver*
3. Reboot
4. Try to install the plugin again from the CA App - of course wait for the plugin window to display the Done button
5. Reboot again
6. Pull the Diagnostics and post them here

1 hour ago, ich777 said:

Something really strange is going on here and really can't tell what the cause of this issue is.

 

Please try this:

1. Remove the plugin
2. Execute: rm -rf /boot/config/plugins/nvidia-driver*
3. Reboot
4. Try to install the plugin again from the CA App - of course wait for the plugin window to display the Done button
5. Reboot again
6. Pull the Diagnostics and post them here

 

So the strange thing is If I close out of the installer and go to settings it will show the plugin there till I reboot and then it goes away.

 

I have rebooted and confirmed the plugin isn't in settings anymore.

Ran rm -rf /boot/config/plugins/nvidia-driver* and confirmed the folder no longer existed under flash\config\plugins

Rebooted again. 

Started my Array back up. 

Started the install from CA Apps at 8:52 am CT. 

 

Checking flash\config\plugins\nvidia-driver

 

\flash\config\plugins\nvidia-driver\packages\5.15.46

 

Waited 2 hours and here is where its at 10:52 am CT.

 

I'm going to give it another hour and I'll close reboot and pull the Diagnostics and post them here.

 

 

 

 

1 hour ago, Dbudd424 said:

\flash\config\plugins\nvidia-driver\packages\5.15.46

I seems that it has issues pulling the .md5 file for this driver.

 

What kind of USB Flash drive are you using?

 

Have now tried it and it worked flawlessly:

 

 

1 hour ago, Dbudd424 said:

So the strange thing is If I close out of the installer and go to settings it will show the plugin there till I reboot and then it goes away.

Yes, because it can't find the md5 file on reboot and thinks that the driver isn't valid and so it gets removed.

You can circumvent that by simply placing the .md5 file in this directory and it should work that way too.

Is there no support for the GT 730? 

What cards are you all using?

 

1 hour ago, ich777 said:

I seems that it has issues pulling the .md5 file for this driver.

 

What kind of USB Flash drive are you using?

 

Have now tried it and it worked flawlessly:

 

 

Yes, because it can't find the md5 file on reboot and thinks that the driver isn't valid and so it gets removed.

You can circumvent that by simply placing the .md5 file in this directory and it should work that way too.

 

Flash drive is a 2.0 16gb Model: ona16aa016

 

Place the files in the folder and booted the server back up.

 

\flash\config\plugins\nvidia-driver\packages\5.15.46

 

\flash\config\plugins\nvidia-driver

 

If I reboot with these files here Nvidia driver doesn't show up in settings so if I run the app give it an hour close it out and go to the nvidia driver under settings and run Update & Download I get 

 

If I reboot nvidia driver is no longer in settings but all the files still exist in the folder. 

 

I'm going to see if I can setup a new flash drive for unraid and give the install another go. 

 

41 minutes ago, gahhruuba said:

Is there no support for the GT 730?

The GT 730 is only supported by the legacy Nvidia 470 series driver.

 

For what do you want to use the card? This card isn‘t even capable of transcoding h265

 

I would recommend that upgrade to something like a NVIDIA T400, this card doesn‘t need external power, you can get it for about $120,- and it is low power, macimum TDP 35W

24 minutes ago, Dbudd424 said:

Flash drive is a 2.0 16gb Model: ona16aa016

Never heard of that I would recommend that you use something like a Transcend JetFlash 600 USB 2.0

 

26 minutes ago, Dbudd424 said:

I'm going to see if I can setup a new flash drive for unraid and give the install another go. 

After thinking again about it I think I had that issue oncex

 

The user solved this by changing the USB Boot device IIRC and never had that issue again.

On 6/24/2022 at 7:18 PM, 2Piececombo said:

No particular reason I didnt go to 6.9.2, a lack of time more than anything. I read a few random comments on YT videos and such that people had a few issues with 6.10, so I was going to upgrade eventually. I'll update over the weekend and post back if I still ahve issues.

Cheers

 

@ich777

So it's been two months since I last posted regarding my issues. I have since updated unraid to 6.10.3 as you suggested, but the problem persists. The problem being that unraid boots up and outputs display on the onboard display adapter, but as soon as it hits the login screen the display shows a blank page. The server is still accessible via the webui and everything seems to work fine. You mentioned previously that this would be resolved upon upgrading to 6.10, however this issue is still there.

Additionally, and possibly related, I have crashing/shutdown issues that only seem to occur while a GPU is connected to my system. I've documented the issue HERE. I have tested EVERY piece of hardware in my server. The crashing issue has happened with two different GPUs. I understand if the shut downs are not something you have any input on, I just figured I'd mention is in case it helps in some way.

 

Id really like to know why unraid will not display past the boot process with a GPU isntalled. (and no, the login is not showing while connected to the GPU display either) 

I've included diags, and can supply any other info if needed.

Cheers

diagnostics-20220821-1744.zip

12 minutes ago, 2Piececombo said:

 

@ich777

So it's been two months since I last posted regarding my issues. I have since updated unraid to 6.10.3 as you suggested, but the problem persists. The problem being that unraid boots up and outputs display on the onboard display adapter, but as soon as it hits the login screen the display shows a blank page. The server is still accessible via the webui and everything seems to work fine. You mentioned previously that this would be resolved upon upgrading to 6.10, however this issue is still there.

Additionally, and possibly related, I have crashing/shutdown issues that only seem to occur while a GPU is connected to my system. I've documented the issue HERE. I have tested EVERY piece of hardware in my server. The crashing issue has happened with two different GPUs. I understand if the shut downs are not something you have any input on, I just figured I'd mention is in case it helps in some way.

 

Id really like to know why unraid will not display past the boot process with a GPU isntalled. (and no, the login is not showing while connected to the GPU display either) 

I've included diags, and can supply any other info if needed.

Cheers

diagnostics-20220821-1744.zip 162.74 kB · 0 downloads

 

Follow up, booted the server up in safe mode (so no nvidia plugin) and the output is displaying properly.

515.65.01 driver doesn't detect my 1050TI to use with plex. Even reseated the gpu. But previous 515.57 does.

Edited August 22, 20224 yr by Duckers

4 hours ago, 2Piececombo said:

The problem being that unraid boots up and outputs display on the onboard display adapter, but as soon as it hits the login screen the display shows a blank page.

Please see this post:

 

2 hours ago, Duckers said:

515.65.01 driver doesn't detect my 1050TI to use with plex. Even reseated the gpu. But previous 515.57 does.

Can you please post your Diagnostics with the 515.65.01 driver installed?

On 8/18/2022 at 1:12 PM, ich777 said:

This (Above 4G decoding) has nothing to do with the memory size from add on cards, this is only the address space that a add on card can use in RAM.

I have the Quadro M2000 card installed and working now. Plex is able to see it and transcode!

On 8/21/2022 at 2:38 PM, ich777 said:

Never heard of that I would recommend that you use something like a Transcend JetFlash 600 USB 2.0

 

After thinking again about it I think I had that issue oncex

 

The user solved this by changing the USB Boot device IIRC and never had that issue again.

 

So I changed flash drive to a different one and moved my license to it. 

Tested it in a different usb port on the motherboard as well.

 

After 2 hours still stuck on this screen.

 

 

Looking at flash\config\plugins\nvidia-driver\packages\5.15.46 it still looks like its having an issue pulling the .md5 

 

I test installed 2 random apps without any issues just to make sure it wasn't some crazy read only issue on the flash drive. 

 

I'm going to play with it some more and see if I can get it to work.

1 hour ago, Dbudd424 said:

I test installed 2 random apps without any issues just to make sure it wasn't some crazy read only issue on the flash drive. 

This is really some funky stuff and I really can't explain what causes this on your system.

 

Are you willing to upgrade to 6.11.0-rc3 and try if it's the same there?

 

I've even now tried it on my production server where no Nvidia card is installed and it is working fine there too.

20 hours ago, ich777 said:

This is really some funky stuff and I really can't explain what causes this on your system.

 

Are you willing to upgrade to 6.11.0-rc3 and try if it's the same there?

 

I've even now tried it on my production server where no Nvidia card is installed and it is working fine there too.

 

Ok, So I upgraded to 6.11.0-rc3. And at first the close button almost tricked me into thinking it worked instantly but I left it alone for 5 minutes and it ran through and completed and changed from close to done. 

 

I'm going test it but it looks like upgrading the OS worked. Thank you for the help. 

On 8/19/2022 at 5:19 PM, ich777 said:

Without anything I can't help.

 

Can you please post your Diagnostics?

Will do! Sorry, forgetful last couple of days, plus was at a time when i needed the streaming start the same day, so had to jump to an older driver.

Interesting enough, now it's detected and running fine when i updated to the latest. Gonna throw in diagnostics either way if there's other issues/bugs not visible. 

 

tower-diagnostics-20220825-1720.zip

2 hours ago, Duckers said:

Interesting enough, now it's detected and running fine when i updated to the latest. Gonna throw in diagnostics either way if there's other issues/bugs not visible. 

Noting suspicious in this Diagnostics.

21 hours ago, ich777 said:

Noting suspicious in this Diagnostics.

Neato  then i will keep using it. If issue occurs with future drivers, i will down the diags as soon as it occurs.

Hi all,

a few months ago the transcoding gpu has stopped working properly, after about 6 months since I set up the transcoding the Nvidia driver stopped recognizing it.

I'm not getting the error message: " 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 everything, turning docker on and off, changing bios settings, reinstalling the plugin, testing a bunch of different driver versions and even downgrading unraid build but nothing seem to fix it.

Unraid is able to see the device connected as the Quadro P1000 (which is correct) and even booting directly into windows or passing it through works fine. I can benchmark it without any issues.
Just to make sure that the gpu wasn't an issue I also tried a different one and it behaved in exactly the same way.

I'm going to leave attached a part of the logs while the machine was turning on, it's clear that the driver is trying to communicate with the GPU however the connection doesn't work.

I'm not sure what else to try at this point, please give me a hand.

Thanks.

 

 

Aug 28 03:13:25 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241

Aug 28 03:13:25 Tower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Aug 28 03:13:25 Tower kernel: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:02:00.0)

Aug 28 03:13:25 Tower kernel: nvidia: probe of 0000:02:00.0 failed with error -1

Aug 28 03:13:25 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).

Aug 28 03:13:25 Tower kernel: NVRM: This can occur when a driver such as:

Aug 28 03:13:25 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv

Aug 28 03:13:25 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s).

Aug 28 03:13:25 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or

Aug 28 03:13:25 Tower kernel: NVRM: reconfigure your kernel without the conflicting

Aug 28 03:13:25 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module

Aug 28 03:13:25 Tower kernel: NVRM: again.

Aug 28 03:13:25 Tower kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).

Aug 28 03:13:25 Tower kernel: NVRM: None of the NVIDIA devices were initialized.

Aug 28 03:13:25 Tower kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 241

Aug 28 03:13:25 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241

Aug 28 03:13:25 Tower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Aug 28 03:13:25 Tower kernel: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:02:00.0)

Aug 28 03:13:25 Tower kernel: nvidia: probe of 0000:02:00.0 failed with error -1

Aug 28 03:13:25 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).

Aug 28 03:13:25 Tower kernel: NVRM: This can occur when a driver such as:

Aug 28 03:13:25 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv

Aug 28 03:13:25 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s).

Aug 28 03:13:25 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or

Aug 28 03:13:25 Tower kernel: NVRM: reconfigure your kernel without the conflicting

Aug 28 03:13:25 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module

Aug 28 03:13:25 Tower kernel: NVRM: again.

Aug 28 03:13:25 Tower kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).

Aug 28 03:13:25 Tower kernel: NVRM: None of the NVIDIA devices were initialized.

Aug 28 03:13:25 Tower kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 241

Aug 28 03:14:11 Tower webGUI: Successful login user root from 192.168.1.101

Aug 28 03:14:17 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241

Aug 28 03:14:17 Tower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Aug 28 03:14:17 Tower kernel: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:02:00.0)

Aug 28 03:14:17 Tower kernel: nvidia: probe of 0000:02:00.0 failed with error -1

Aug 28 03:14:17 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).

Aug 28 03:14:17 Tower kernel: NVRM: This can occur when a driver such as:

Aug 28 03:14:17 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv

Aug 28 03:14:17 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s).

Aug 28 03:14:17 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or

Aug 28 03:14:17 Tower kernel: NVRM: reconfigure your kernel without the conflicting

Aug 28 03:14:17 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module

Aug 28 03:14:17 Tower kernel: NVRM: again.

Aug 28 03:14:17 Tower kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).

Aug 28 03:14:17 Tower kernel: NVRM: None of the NVIDIA devices were initialized.

Aug 28 03:14:17 Tower kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 241

Aug 28 03:14:17 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 241

Aug 28 03:14:17 Tower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:

Aug 28 03:14:17 Tower kernel: NVRM: BAR0 is 0M @ 0x0 (PCI:0000:02:00.0)

Aug 28 03:14:17 Tower kernel: nvidia: probe of 0000:02:00.0 failed with error -1

Aug 28 03:14:17 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).

Aug 28 03:14:17 Tower kernel: NVRM: This can occur when a driver such as:

Aug 28 03:14:17 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv

Aug 28 03:14:17 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s).

Aug 28 03:14:17 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or

Aug 28 03:14:17 Tower kernel: NVRM: reconfigure your kernel without the conflicting

Aug 28 03:14:17 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module

Aug 28 03:14:17 Tower kernel: NVRM: again.

Aug 28 03:14:17 Tower kernel: NVRM: The NVIDIA probe routine failed for 1 device(s).

Aug 28 03:14:17 Tower kernel: NVRM: None of the NVIDIA devices were initialized.

Aug 28 03:14:17 Tower kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 241

24 minutes ago, Andrea Nizzola said:

I'm not sure what else to try at this point, please give me a hand.

Please post your Diagnostics.

Thank you for the reply, here is the diagnostic

tower-diagnostics-20220828-1815.zip

5 minutes ago, Andrea Nizzola said:

Thank you for the reply, here is the diagnostic

Have you maybe upgraded the BIOS at one point?

 

Please make sure that you have the following BIOS options enabled:

• Above 4G decoding
• Resizable BAR Support

 

This issue is usually caused by something miss configured in the BIOS or a hardware incompatibility issue.

Have you yet tried to re seat the card or put it in another PCIe slot?