12 minutes ago, ich777 said:

Please install the Nvidia Driver plugin (and wait until the Done button is displayed in the installation pop up) as requested above and post your Diagnostics again.

im really sorry i forgot that... now after install

unraidtower-diagnostics-20230110-1230.zip

8 minutes ago, LittelD said:

im really sorry i forgot that... now after install

Here is the error:

Jan 10 12:28:22 UnraidTower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
Jan 10 12:28:22 UnraidTower kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:01:00.0)

 

This seems pretty much BIOS related, please double check that you've enabled Above 4G Decoding (this is surely called very differently on your Dell server in the BIOS) and check for a option about resizable BAR support and enable it.

 

The driver should work fine, the only thing what is preventing it from working is your BIOS currently, hope that helps.

 

Please let me know how that option is called on the Dell servers if you find it.

33 minutes ago, ich777 said:

Here is the error:

Jan 10 12:28:22 UnraidTower kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
Jan 10 12:28:22 UnraidTower kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:01:00.0)

 

This seems pretty much BIOS related, please double check that you've enabled Above 4G Decoding (this is surely called very differently on your Dell server in the BIOS) and check for a option about resizable BAR support and enable it.

 

The driver should work fine, the only thing what is preventing it from working is your BIOS currently, hope that helps.

 

Please let me know how that option is called on the Dell servers if you find it.

well sadly there is no option in the bios for this.... 

 

guess journey ends here for now

 

Thanks alot for your support

Edited January 10, 20233 yr by LittelD

12 minutes ago, LittelD said:

well sadly there is no option in the bios for this.... 

There is an option for that for sure because another user here enabled it successfully on his Dell server.

 

Something with large PCI address space or something like that.

2 minutes ago, ich777 said:

There is an option for that for sure because another user here enabled it successfully on his Dell server.

 

Something with large PCI address space or something like that.

well this is not a Dell Server , this just a Optiplex 7020 and nothing in the bios that sounded even far away like that, or anyhting i couldnt understand/knew what it did exactly. 

9 minutes ago, LittelD said:

well this is not a Dell Server

Oh, I thought this is some kind of Dell Server because I saw lots of Dell devices in your devices overview.

 

Anyways, maybe check if there is a newer BIOS available which enables this function, technically speaking this should be possible on nearly every motherboard which is capable of x86_64.

On 1/10/2023 at 6:31 AM, LittelD said:

well this is not a Dell Server , this just a Optiplex 7020 and nothing in the bios that sounded even far away like that, or anyhting i couldnt understand/knew what it did exactly. 

 

Any chance a BIOS setting was hardcoded that prohibits the BIOS from reading the card?  It could be worth a default reset.  I'd also check to see if there are any PCI settings that appear odd.

Hi I'm having trouble with this plugin. When I click on the nvidia-driver page in the settings I just get a blank screen (that seems to be trying to load then times out). I've disabled and enabled docker. I've rebooted. I've uninstalled the plugin. reinstalled the plugin, then disabled and renabled docker. no joy. 


Also when I first tried to get it working, I try to apply a GPU to a frigate docker container only to have the entire docker image corrupt itself. 

Logs show: 276 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.121, server: , request: "GET /Settings/nvidia-driver HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "LOCAL-IP", referrer: "http://LOCAL-IP/Plugins"

 

 

45 minutes ago, CallMeBeachy said:

When I click on the nvidia-driver page in the settings I just get a blank screen (that seems to be trying to load then times out).

With that little information I really can't do much, please post your Diagnostics.

 

45 minutes ago, CallMeBeachy said:

Also when I first tried to get it working, I try to apply a GPU to a frigate docker container only to have the entire docker image corrupt itself. 

This is most likely not caused by the plugin, maybe this was some kind of weird coincidence and I've never heard of something like that because the plugin doesn't touch the Docker image or anything else on the system, except for the directory on the boot drive where the plugin is stored.

 

How much RAM do you have installed in your system? Are you sure that you are not running out of memory?

What card are you using? Is this a new card or did you by it used? Have you yet tried to re-seat the card in the slot? Did you check if external power (if required) is connected properly and sufficient?

Hows the situation with using this to run a 2nd nvidia card? Would one just install a 2nd instance?

2 hours ago, ich777 said:

With that little information I really can't do much, please post your Diagnostics.

 

This is most likely not caused by the plugin, maybe this was some kind of weird coincidence and I've never heard of something like that because the plugin doesn't touch the Docker image or anything else on the system, except for the directory on the boot drive where the plugin is stored.

 

How much RAM do you have installed in your system? Are you sure that you are not running out of memory?

What card are you using? Is this a new card or did you by it used? Have you yet tried to re-seat the card in the slot? Did you check if external power (if required) is connected properly and sufficient?

Well... it turns out I needed to reseat the GPU... I can't believe that. I nearly didn't do it thinking.. the bloody thing can't move and I can see it in the systems interfaces..

Nvidia panel is opening now. Will attempt to attach it to the docker containers now. Appreciate your help and your patience.

1 hour ago, dopeytree said:

Hows the situation with using this to run a 2nd nvidia card? Would one just install a 2nd instance?

I don't fully understand...

Just install a second card in your system and it should show up in the Plugin, no need to install anything for a second card.

 

I know a few users who are running 3+ cards in their system with the plugin.

2 minutes ago, CallMeBeachy said:

Nvidia panel is opening now. Will attempt to attach it to the docker containers now. Appreciate your help and your patience.

Glad that everything is working now, the next time you experience an issue please include the Diagnostics.

Is there a way to control idle usage fan speed? my rtx a2000 seems to default to 30% which is whinny. 

I'm sure if I could tweak the idle fan to be either 20% or 40% it would change the whine.

It's a blower so no simple way to swap it to a noctua silent fan.

 

The card is idling in p8 power idle mode.

Edited January 18, 20233 yr by dopeytree

26 minutes ago, dopeytree said:

Is there a way to control idle usage fan speed? my rtx a2000 seems to default to 30% which is whinny. 

Sadly enough no, at least not without a Desktop environment and some libraries which are actually not available on Unraid.

The fan curve is set in the BIOS from the card.

 

28 minutes ago, dopeytree said:

The card is idling in p7 power idle mode.

I assume with nvidia-persistenced enabled correct?

yeah nvidia-persistenced is enabled on boot in go file. Sorry it's p8 not p7.

Its only 30° at idle so shouldn't need 30% fan usage.

It rises to 50% fan speed when in full use playing gaming like cyberpunk2077 with raytracing on at around 65°-75°.

 

I found this so will have a tinker https://www.techticity.com/howto/how-to-control-nvidia-graphics-card-fan-speed-in-linux/

 

Edited January 18, 20233 yr by dopeytree

13 minutes ago, dopeytree said:

I found this so will have a tinker https://www.techticity.com/howto/how-to-control-nvidia-graphics-card-fan-speed-in-linux/

This will not work because some libraries and a Desktop environment is missing.

Hello all.  I have two NVidia cards installed and followed the directions in the plugin with the Opensource driver.  I had tried the others but I still get 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." I rebooted as well.  I am using a Tesla P4 and a an NVS 310.  The 310 is the display card in the primary slot and the P4 is secondary.  Both show up in devices.  Thanks so much in advance!

 

 

diags.zip

4 hours ago, Trackpads said:

I have two NVidia cards installed and followed the directions in the plugin with the Opensource driver.

Are you sure that you've followed the directions from the Nvidia Driver plugin page for the Open Source Kernel Module?

I don't see the folder /boot/config/modprobe.d and the nvidia.config file is also missing.

 

If you really want to use the open source driver you have to follow like mentioned on the Nvidia Driver plugin page for the Open Source Kernel Module.

 

The next thing is that you've bound your P4 to VFIO and that wont work either, you have to unbind it from VFIO so that it can show up on the host and therefore in the plugin:

0b:00.0 3D controller [0302]: NVIDIA Corporation GP104GL [Tesla P4] [10de:1bb3] (rev a1)
    Subsystem: NVIDIA Corporation GP104GL [Tesla P4] [10de:11d8]
    Kernel driver in use: vfio-pci
    Kernel modules: nvidia_drm, nvidia

 

And last the NVS 310 isn't supported by the Open Source Kernel Module, or any other driver package because it is simply to old and needs the older legacy driver series 390 which isn't available through the plugin because you won't have much benefit because you simply can't use it in Docker containers.

As you can even see here the driver did also tell you that you card is not supported by the Open Source Kernel Module:

Jan 18 12:40:06 Executor kernel: NVRM: The NVIDIA GPU 0000:0a:00.0 (PCI ID: 10de:107d)
Jan 18 12:40:06 Executor kernel: NVRM: installed in this system is not supported by open
Jan 18 12:40:06 Executor kernel: NVRM: nvidia.ko because it does not include the required GPU
Jan 18 12:40:06 Executor kernel: NVRM: System Processor (GSP).

This is the card the driver is referring to:

0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1)
	Subsystem: Hewlett-Packard Company GF119 [NVS 310] [103c:1154]
	Kernel modules: nvidia_drm, nvidia

 

 

Please don't forget that if you want to use the Open Source Kernel Module it will only work if you create the file with the content described on the Nvidia Driver plugin page and reboot afterwards, but I would recommend that you stick to the latest available closed source driver.

Hi Ich777,

After my Plex docker failed to stop, and an unclean shutdown of my array, Nvidia-smi and the plugin cannot find my GPU (gtx1050ti). It appears under system hardware. Is there anything I can do to troubleshoot/reset? I have tried uninstalling/reinstalling different driver versions. Thanks!

 

Edited January 22, 20233 yr by wkipling

5 hours ago, ich777 said:

Are you sure that you've followed the directions from the Nvidia Driver plugin page for the Open Source Kernel Module?

I don't see the folder /boot/config/modprobe.d and the nvidia.config file is also missing.

 

If you really want to use the open source driver you have to follow like mentioned on the Nvidia Driver plugin page for the Open Source Kernel Module.

 

The next thing is that you've bound your P4 to VFIO and that wont work either, you have to unbind it from VFIO so that it can show up on the host and therefore in the plugin:

0b:00.0 3D controller [0302]: NVIDIA Corporation GP104GL [Tesla P4] [10de:1bb3] (rev a1)
    Subsystem: NVIDIA Corporation GP104GL [Tesla P4] [10de:11d8]
    Kernel driver in use: vfio-pci
    Kernel modules: nvidia_drm, nvidia

 

And last the NVS 310 isn't supported by the Open Source Kernel Module, or any other driver package because it is simply to old and needs the older legacy driver series 390 which isn't available through the plugin because you won't have much benefit because you simply can't use it in Docker containers.

As you can even see here the driver did also tell you that you card is not supported by the Open Source Kernel Module:

Jan 18 12:40:06 Executor kernel: NVRM: The NVIDIA GPU 0000:0a:00.0 (PCI ID: 10de:107d)
Jan 18 12:40:06 Executor kernel: NVRM: installed in this system is not supported by open
Jan 18 12:40:06 Executor kernel: NVRM: nvidia.ko because it does not include the required GPU
Jan 18 12:40:06 Executor kernel: NVRM: System Processor (GSP).

This is the card the driver is referring to:

0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [NVS 310] [10de:107d] (rev a1)
	Subsystem: Hewlett-Packard Company GF119 [NVS 310] [103c:1154]
	Kernel modules: nvidia_drm, nvidia

 

 

Please don't forget that if you want to use the Open Source Kernel Module it will only work if you create the file with the content described on the Nvidia Driver plugin page and reboot afterwards, but I would recommend that you stick to the latest available closed source driver.

Thanks!  I did as you asked.  I had left the .txt on the nvidia file and fixed it.  I also removed the vfio mapping. Still the same.  As for the NVS I have it as a basic card for the machine, a left over from my T320.  

 

I just want to use the P4 with a VM.  Is that going to be possible or am I wasting my time? That is the only reason I am trying the open source driver.  If I am going about this wrong please let me know.  I am using a Dell Precision T6710 so it doesnt have an onboard video.  I was told that If I pass through a GPU I could use it for the unraid output to a monitor. That is why I am using cards that are single slot only.  I have no spare slots.  Please correct me on this.  I just a vm to do video encoding for videos I work on.  

 

I really appreciate your assistance.  I uploaded the new diags. 

 

 

 

 

executor-diagnostics-20230118-2254.zip

13 minutes ago, Trackpads said:

I just want to use the P4 with a VM.  Is that going to be possible or am I wasting my time?

may  as note from Page 1

 

 

so as you are using 2 cards, this plugin could make sense for card 1 in docker(s) when i see this correctly (NVS310), but its useless for your VM Project if thats the question.

 

While the NVS310 is very old ...

3 hours ago, wkipling said:

Is there anything I can do to troubleshoot/reset?

You don't have to reset anything.

 

The only indication that I see is this in your syslog:

Jan 19 10:41:59 Rack720XD kernel: NVRM: GPU 0000:43:00.0: RmInitAdapter failed! (0x31:0xffff:2476)
Jan 19 10:41:59 Rack720XD kernel: NVRM: GPU 0000:43:00.0: rm_init_adapter failed, device minor number 0

 

What Plex container are you using? Did you already try to fully shutdown the server and start it again?

1 hour ago, Trackpads said:

That is the only reason I am trying the open source driver.

But why the open source one?

The Tesla P4 isn't supported by the Open Source Kernel Module...

 

Why don't you use the latest driver? Anyways, as @alturismo said, you don't need this plugin if you want to use it in a VM like mentioned on the first page.

9 hours ago, ich777 said:

You don't have to reset anything.

 

The only indication that I see is this in your syslog:

Jan 19 10:41:59 Rack720XD kernel: NVRM: GPU 0000:43:00.0: RmInitAdapter failed! (0x31:0xffff:2476)
Jan 19 10:41:59 Rack720XD kernel: NVRM: GPU 0000:43:00.0: rm_init_adapter failed, device minor number 0

 

What Plex container are you using? Did you already try to fully shutdown the server and start it again?

Thanks for your quick reply.

 

I have done multiple reboots, I tried reseating the card in the same slot.

I am using binhex plex pass. It has been working fine until a couple of days ago. One morning I saw plex pinning some cores, it didn't appear to be doing any scheduled tasks so I tried to restart the docker which failed. Upon eventual reboot i got no devices found.
Interestingly when this issue first occurred, a reboot fixed it but not the second time.

 

I'll look into that syslog message. Thanks again for your time and hard work.