[Plugin] Nvidia-Driver


ich777

1057 posts in this topic Last Reply

Recommended Posts

45 minutes ago, jtmoore81 said:

I am at a loss, here.

Can you try a different driver version?

 

Or at least are you able to perform a installation of the plugin and then go directly on the settings page for the Nvidia driver and choose for example the Production Branch press Update and after this Download?

 

EDIT: Have you changed any hardware or updated the BIOS or something else?

 

EDIT2: I only experience/know this issue if you have a custom build with the gnif/vendor-reset patch installed.

Link to post
  • Replies 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Nvidia-Driver (only Unraid 6.9.0beta35 and up) This Plugin is only necessary if you are planning to make use of your Nvidia graphics card inside Docker Containers. If you only want to use yo

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

Thanks @bytchslappa for the heads up. Everyone using a User Script for Nvidia GPU Power State just edit the script to: #!/bin/bash nvidia-persistenced fuser -v /dev/nvidia* and leave the s

Posted Images

Posted (edited)
11 minutes ago, ich777 said:

Can you try a different driver version?

 

Or at least are you able to perform a installation of the plugin and then go directly on the settings page for the Nvidia driver and choose for example the Production Branch press Update and after this Download?

It doesn't look like I can. I go to the settings and it's just a blank screen.

 

Is there a way to go into the config files and manually set a older version?

Edited by jtmoore81
Link to post
26 minutes ago, ich777 said:

Can you try a different driver version?

 

Or at least are you able to perform a installation of the plugin and then go directly on the settings page for the Nvidia driver and choose for example the Production Branch press Update and after this Download?

 

EDIT: Have you changed any hardware or updated the BIOS or something else?

 

EDIT2: I only experience/know this issue if you have a custom build with the gnif/vendor-reset patch installed.

The only hardware I changed was adding the P2000 and it's been a while since I updated the bios. This is a custom build with new hardware and I'm not sure what gnif/vnedor-reset patch is so I'm assuming I don't have it.

Link to post
1 minute ago, jtmoore81 said:

gnif/vnedor-reset patch is so I'm assuming I don't have it.

I also think so... :)

 

I will try to install the latest driver on my server please give me a few minutes to try...

Link to post
7 minutes ago, jtmoore81 said:

The only hardware I changed was adding the P2000 and it's been a while since I updated the bios.

Definitely not a driver problem:

grafik.thumb.png.96b560ab22b5ad4db41c959c3517d14c.png

 

Can you try to reset the BIOS eventually (but only if you know what you are doing).

Eventually something messed up the system...

Link to post
13 minutes ago, ich777 said:

Definitely not a driver problem:

grafik.thumb.png.96b560ab22b5ad4db41c959c3517d14c.png

 

Can you try to reset the BIOS eventually (but only if you know what you are doing).

Eventually something messed up the system...

ok, I'll try doing a BIOS update first to see if there any bugs that an update might fix.

 

I appreciate your help on this! If I ever figure it out I'll let you know.

Link to post
Posted (edited)

I'm having issues getting my 1050 Ti working. I see it in my system devices but in my syslog I see it try to initialize a few times with the message "The NVIDIA GPU -device id- installed in this system is not supported by the NVIDIA 465.27 driver release, etc, etc, None of the NVIDIA devices were initialized.

 

According to the supported devices list on Nvidia's site for this driver version, the 1050 Ti should be supported. I've also tried the production branch with the same results.

 

So far I've added "video=efifb:off" to my syslinux.cfg and verified I don't have it bound to vfio.

 

Any help would be appreciated!

 

Edit: I also just tried with driver 465.24.02 without luck.

tower-diagnostics-20210502-1444.zip

Edited by AlaskanBeard
Link to post
12 hours ago, AlaskanBeard said:

I'm having issues getting my 1050 Ti working. I see it in my system devices but in my syslog I see it try to initialize a few times with the message "The NVIDIA GPU -device id- installed in this system is not supported by the NVIDIA 465.27 driver release, etc, etc, None of the NVIDIA devices were initialized.

Is this a new card or where did you buy it?

I came across such messages in the past and this seems like it's been a counterfeit card, can you post a picture of the card itself?

Also here is a reference from Nvidia: Click

(From the audio controller identifier it looks more like a GTX550Ti)

 

5 hours ago, Dazog said:

Could you add the Vulkan dev branch for people who need it also?

I'm maybe wrong about that but isn't Vulkan built into every driver from 455.50.14 upwards on Linux?

 

EDIT: What would be the benefit on Unraid? Also keep in mind that Nvidia defines only the Production Branch and the New Feature Branch even on their download page:

grafik.png.604ab8b461042886c73a4d5d235fabde.png

Link to post
Posted (edited)
54 minutes ago, ich777 said:

Is this a new card or where did you buy it?

I came across such messages in the past and this seems like it's been a counterfeit card, can you post a picture of the card itself?

Also here is a reference from Nvidia: Click

(From the audio controller identifier it looks more like a GTX550Ti)

 

I'm maybe wrong about that but isn't Vulkan built into every driver from 455.50.14 upwards on Linux?

 

I actually had the same thought but I haven't had a chance to shut my sever down to verify. I'll report back when I can check (hopefully tomorrow). Thanks for the response!

 

EDIT: I went ahead and pulled the card and it's a GTS 450

Edited by AlaskanBeard
Link to post
10 hours ago, ich777 said:

Is this a new card or where did you buy it?

I came across such messages in the past and this seems like it's been a counterfeit card, can you post a picture of the card itself?

Also here is a reference from Nvidia: Click

(From the audio controller identifier it looks more like a GTX550Ti)

 

I'm maybe wrong about that but isn't Vulkan built into every driver from 455.50.14 upwards on Linux?

 

EDIT: What would be the benefit on Unraid? Also keep in mind that Nvidia defines only the Production Branch and the New Feature Branch even on their download page:

grafik.png.604ab8b461042886c73a4d5d235fabde.png

 

Vulkan branch has latest extensions NOT in the branches on consumer site.

 

It's meant for people testing upcoming Vulkan versions.

 

I don't use it, but some may find it useful.

Link to post
2 hours ago, Dazog said:

Vulkan branch has latest extensions NOT in the branches on consumer site.

You mean the Vulkan 1.2 API where the others only have 1.0 and 1.1?

 

2 hours ago, Dazog said:

It's meant for people testing upcoming Vulkan versions.

But do you really think it's usefull on Unraid?

 

Anyways, I will not support that branch because it's not even a "real" branch because it's nowhere listed which versions numbers these drivers with the new API are and also I don't think that game developers will use Unraid as a platform to test such things or even develop games for the new API.

The next thing is I don't have a way to read the version numbers from anywhere automated which are Vulkan DEV drivers...

 

Also think twice about it, the users now can choose between 3 or better speaking 2 different branches and you can also choose between 8 recent driver versions, I will not bloat the plugin page anymore especially with DEV drivers...

 

13 hours ago, AlaskanBeard said:

EDIT: I went ahead and pulled the card and it's a GTS 450

Oh no... :/

Link to post
1 minute ago, ich777 said:

You mean the Vulkan 1.2 API where the others only have 1.0 and 1.1?

 

But do you really think it's usefull on Unraid?

 

Anyways, I will not support that branch because it's not even a "real" branch because it's nowhere listed which versions numbers these drivers with the new API are and also I don't think that game developers will use Unraid as a platform to test such things or even develop games for the new API.

The next thing is I don't have a way to read the version numbers from anywhere automated which are Vulkan DEV drivers...

 

Also think twice about it, the users now can choose between 3 or better speaking 2 different branches and you can also choose between 8 recent driver versions, I will not bloat the plugin page anymore especially with DEV drivers...

 

Oh no... :/

No worries, I thought I would ask.

 

 

Link to post

Does anyone have issues with the GPU memory? My M4000 floods and won't empty. Transcoding movies freeze for a couple of seconds and then resume. Re-freeze within 20 seconds and repeat. 

 

Just stopped my movie and it took about a minute before the GPU started to flush the memory. 

 

In my opinion this shouldn't happen when there's only one stream playing. Especially when you realize the M4K can handle at least 20 streams

Screenshot_20210504-145621.jpg

Link to post
11 minutes ago, XisoP said:

n my opinion this shouldn't happen when there's only one stream playing. Especially when you realize the M4K can handle at least 20 streams

This has nothing to do with the Driver itself.

 

This is more a Plex "thing" since it also shows that Plex is using the GPU (I think the picture is after you stopped the playback) and what I can think of is that Plex uses the card a little longer after you stopped the playback.

From my experience the memory usage is pretty normal if you transcode a 1080p file.

Link to post

Done some testing, and indeed seems to be some kind of plex issue. Direct play freezes even more 🤔

Thanks for your quick response. I'll take this issue to linuxserver 

Link to post
18 minutes ago, XisoP said:

I'll take this issue to linuxserver 

This is more a direct Plex issue and linuxserver can do nothing about it I think.

Link to post

Hi! I'm hoping you guys can help me out:

 

Background: I'm trying to get the nvidia drivers to work in order to get the power consumption of the server in idle down.
I only use the GPU for some casual gaming, but would like it to lower poweruse when not.. I got this working up to certain extent,
Last time however when I rebooted it wouldn't load the web-gui. I had to fall back to an older flash image...

 

GPU: NVIDIA Corporation GM204 [GeForce GTX 970]
CPU: i7-8700k
mobo: MSI B360M PRO-VDH

 

Now I'm trying to figure out how I can get it working but still have trouble:

After installing Nvidia drivers (tried latest and production) and rebooting. The GPU is not recognized in the "system devices".


Syslog:
 

May  4 21:18:14 Tower root: plugin: libvirtwol.plg installed
May  4 21:18:14 Tower root: plugin: installing: /boot/config/plugins/nvidia-driver.plg
May  4 21:18:14 Tower root: plugin: running: anonymous
May  4 21:18:14 Tower root: plugin: skipping: /boot/config/plugins/nvidia-driver/nvidia-driver-2021.04.29.txz already exists
May  4 21:18:14 Tower root: plugin: running: /boot/config/plugins/nvidia-driver/nvidia-driver-2021.04.29.txz
May  4 21:18:14 Tower root:
May  4 21:18:14 Tower root: +==============================================================================
May  4 21:18:14 Tower root: | Installing new package /boot/config/plugins/nvidia-driver/nvidia-driver-2021.04.29.txz
May  4 21:18:14 Tower root: +==============================================================================
May  4 21:18:14 Tower root:
May  4 21:18:14 Tower root: Verifying package nvidia-driver-2021.04.29.txz.
May  4 21:18:14 Tower root: Installing package nvidia-driver-2021.04.29.txz:
May  4 21:18:14 Tower root: PACKAGE DESCRIPTION:
May  4 21:18:14 Tower root: Package nvidia-driver-2021.04.29.txz installed.
May  4 21:18:14 Tower root: plugin: creating: /usr/local/emhttp/plugins/nvidia-driver/README.md - from INLINE content
May  4 21:18:14 Tower root: plugin: running: anonymous
May  4 21:18:15 Tower root:
May  4 21:18:15 Tower root: --------------------Nvidia driver v460.73.01 found locally---------------------
May  4 21:18:15 Tower root:
May  4 21:18:15 Tower root: -----------------Installing Nvidia Driver Package v460.73.01-------------------
May  4 21:18:15 Tower kernel: device br0 entered promiscuous mode
May  4 21:18:34 Tower kernel: nvidia: loading out-of-tree module taints kernel.
May  4 21:18:34 Tower kernel: nvidia: module license 'NVIDIA' taints kernel.
May  4 21:18:34 Tower kernel: Disabling lock debugging due to kernel taint
May  4 21:18:34 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245
May  4 21:18:34 Tower kernel: NVRM: No NVIDIA GPU found.
May  4 21:18:34 Tower kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 245
May  4 21:18:34 Tower root:
May  4 21:18:34 Tower root: --------------Installation of Nvidia driver v460.73.01 successful--------------
May  4 21:18:34 Tower root: plugin: nvidia-driver.plg installed
May  4 21:18:34 Tower root: plugin: installing: /boot/config/plugins/tips.and.tweaks.plg
May  4 21:18:34 Tower root: plugin: running: anonymous
May  4 21:18:34 Tower root: plugin: skipping: /boot/config/plugins/tips.and.tweaks/tips.and.tweaks-2021.03.09.tgz already exists
May  4 21:18:34 Tower root: plugin: running: anonymous
May  4 21:18:34 Tower root: plugin: skipping: /boot/config/plugins/tips.and.tweaks/tips.and.tweaks.cfg already exists
May  4 21:18:34 Tower root: plugin: running: anonymous
May  4 21:18:34 Tower root:


Only after shutting down and removing and starting again will de GPU show op again.
However, when I look at the driver plugin, it will say no devices are found.

Can someone point me into the direction of a solution?


*update
after a few times restarting, it seems to have loaded the GPU again and it recognizes the GPU again.
 

May  4 21:54:39 Tower root: plugin: libvirtwol.plg installed
May  4 21:54:39 Tower root: plugin: installing: /boot/config/plugins/nvidia-driver.plg
May  4 21:54:39 Tower root: plugin: running: anonymous
May  4 21:54:39 Tower root: plugin: skipping: /boot/config/plugins/nvidia-driver/nvidia-driver-2021.04.29.txz already exists
May  4 21:54:39 Tower root: plugin: running: /boot/config/plugins/nvidia-driver/nvidia-driver-2021.04.29.txz
May  4 21:54:39 Tower root:
May  4 21:54:39 Tower root: +==============================================================================
May  4 21:54:39 Tower root: | Installing new package /boot/config/plugins/nvidia-driver/nvidia-driver-2021.04.29.txz
May  4 21:54:39 Tower root: +==============================================================================
May  4 21:54:39 Tower root:
May  4 21:54:39 Tower root: Verifying package nvidia-driver-2021.04.29.txz.
May  4 21:54:39 Tower root: Installing package nvidia-driver-2021.04.29.txz:
May  4 21:54:39 Tower root: PACKAGE DESCRIPTION:
May  4 21:54:39 Tower root: Package nvidia-driver-2021.04.29.txz installed.
May  4 21:54:39 Tower root: plugin: creating: /usr/local/emhttp/plugins/nvidia-driver/README.md - from INLINE content
May  4 21:54:39 Tower root: plugin: running: anonymous
May  4 21:54:40 Tower kernel: device br0 entered promiscuous mode
May  4 21:54:40 Tower root:
May  4 21:54:40 Tower root: --------------------Nvidia driver v460.73.01 found locally---------------------
May  4 21:54:40 Tower root:
May  4 21:54:40 Tower root: -----------------Installing Nvidia Driver Package v460.73.01-------------------
May  4 21:55:00 Tower kernel: nvidia: loading out-of-tree module taints kernel.
May  4 21:55:00 Tower kernel: nvidia: module license 'NVIDIA' taints kernel.
May  4 21:55:00 Tower kernel: Disabling lock debugging due to kernel taint
May  4 21:55:00 Tower kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245
May  4 21:55:00 Tower kernel:
May  4 21:55:00 Tower kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
May  4 21:55:00 Tower kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
May  4 21:55:00 Tower kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  460.73.01  Thu Apr  1 21:40:36 UTC 2021
May  4 21:55:00 Tower kernel: Linux agpgart interface v0.103
May  4 21:55:00 Tower root:
May  4 21:55:00 Tower root: --------------Installation of Nvidia driver v460.73.01 successful--------------
May  4 21:55:00 Tower root: plugin: nvidia-driver.plg installed
May  4 21:55:00 Tower root: plugin: installing: /boot/config/plugins/tips.and.tweaks.plg
May  4 21:55:00 Tower root: plugin: running: anonymous
May  4 21:55:00 Tower root: plugin: skipping: /boot/config/plugins/tips.and.tweaks/tips.and.tweaks-2021.03.09.tgz already exists
May  4 21:55:00 Tower root: plugin: running: anonymous
May  4 21:55:00 Tower kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  460.73.01  Thu Apr  1 21:32:31 UTC 2021
May  4 21:55:00 Tower kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
May  4 21:55:00 Tower kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
May  4 21:55:00 Tower root: plugin: skipping: /boot/config/plugins/tips.and.tweaks/tips.and.tweaks.cfg already exists
May  4 21:55:00 Tower root: plugin: running: anonymous

 

 

*Update2
After rebooting and taking the power off the GPU is visible but the driver does not recognize it, no devices were found (production driver)

May  4 22:08:20 Tower kernel: DMAR: DRHD: handling fault status reg 3
May  4 22:08:20 Tower kernel: DMAR: [DMA Read] Request device [01:00.0] PASID ffffffff fault addr 4dd400f000 [fault reason 06] PTE Read access is not set
May  4 22:08:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:28 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:28 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:32 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:32 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:37 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:37 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:41 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:41 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:45 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:45 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:49 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:49 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:54 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:54 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:08:58 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:08:58 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:02 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:02 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:07 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:07 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:11 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:11 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:15 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:15 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:19 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:19 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:28 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:28 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:32 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:32 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:37 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:37 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:41 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:41 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:45 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:45 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:50 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:50 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0
May  4 22:09:54 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)
May  4 22:09:54 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

 

So is the trouble my GPU (why does it needs shutting down every time to be recognized?) and why can't I get the driver stable in running? I've attached diagnostics..

 

 

tower-diagnostics-20210504-2211 - GPU visible but driver not recognized.zip

Link to post
8 hours ago, Madfox said:

Last time however when I rebooted it wouldn't load the web-gui. I had to fall back to an older flash image...

Have you got a active internet connection on boot?

Was the server reachable through ssh?

The Nvidia-Driver downloads the driver on each reboot if a new driver was found, Unraid was upgraded or you changed the driver version.

 

8 hours ago, Madfox said:

May 4 22:08:24 Tower kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x26:0x65:1290)

May 4 22:08:24 Tower kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

From what I've found online and read this seems to be more like a hardware or BIOS issue.

 

The card is working in a passed through VM I think?

Do you boot with UEFI or Legacy Mode? If you are booting with UEFI try to boot in Legacy Mode.

 

Eventually try to reset the BIOS or better speaking search if a BIOS update for your motherboard is available (only if you know what you are doing) and see if that helps.

Link to post

Thanks for the suggestions!

 

6 hours ago, ich777 said:

Have you got a active internet connection on boot?

Yes, it was active

 

6 hours ago, ich777 said:

Was the server reachable through ssh?

SSH was disabled so didn't check - I did hook up an external monitor and it was booted and could logon there.

 

6 hours ago, ich777 said:

The card is working in a passed through VM I think?

Yes, incl vbios. Its not bound to VFIO at boot.

 

7 hours ago, ich777 said:

Do you boot with UEFI or Legacy Mode? If you are booting with UEFI try to boot in Legacy Mode.

 

Eventually try to reset the BIOS or better speaking search if a BIOS update for your motherboard is available (only if you know what you are doing) and see if that helps.

Not sure how its booting, I think it accepts both- I'll change it in the bios to legacy.

 

If that doesn't work, there is a beta bios available for this board:

Quote

7B24vAC1(Beta version)

Release Date

2021-02-17

Support Resizable BAR (Re-Size BAR) function to enhance GPU performance including the Nvidia GeForce RTX 3000 series and others.

I'll update that if the above doesn't work out.

 

One thing I'll say is that it's weird that the problem of the GPU not being recognized after reboot only seems to happen with the drivers installed..

Link to post
Just now, Madfox said:

Yes, it was active

The reason behind my question is because the plugin tries to download a newer version if a newer version is found on boot and the boot can take longer than usual if that happens.

 

1 minute ago, Madfox said:

SSH was disabled so didn't check - I did hook up an external monitor and it was booted and could logon there.

Oh then this seems some other kind of problem not strictly related to the plugin.

 

2 minutes ago, Madfox said:

Its not bound to VFIO at boot.

Also seen that from your Diagnostics otherwise the plugin can't detect your card.

 

3 minutes ago, Madfox said:

I'll change it in the bios to legacy.

Legacy often helps.

 

4 minutes ago, Madfox said:

I'll update that if the above doesn't work out.

I don't think that this will solve the issue and a beta BIOS is never really the way to go.

 

4 minutes ago, Madfox said:

One thing I'll say is that it's weird that the problem of the GPU not being recognized after reboot only seems to happen with the drivers installed..

I don't completely understand what you mean exactly with this.

Have you set the VM to autostart?

Link to post
Posted (edited)
7 hours ago, ich777 said:

Legacy often helps.

I found out UNRAID is set to boot in legacy already - would UEFI be something to try?

 

7 hours ago, ich777 said:

I don't completely understand what you mean exactly with this.

I mean that its weird that when I normally reboot the system, the GPU is recognized in "system devices" but when using the drivers it seem like the only way to get the GPU to be recognized after bootup is by turning off the system and starting it (complete shutdown).

Its almost as if the GPU gets in a state and needs to be reset or something - and the only way to do this is by removing the power...

 

7 hours ago, ich777 said:

Have you set the VM to autostart?

No - its startup up using a WOL request - but off most of the time.

 

I guess the only thing left now is resetting the bios - so that will be my next move.

 

*update - resetting bios settings did also not change the situation. I'm out of ideas!

 

btw, I've had the situation now that the driver was loaded and the GPU recognized by Unraid, but the driver did not see the GPU. Only after starting and stopping the VM did the driver actually work. The situation did not survive a reboot unfortunately..

 

Any suggestions are very welcome!

 

Edited by Madfox
Link to post
Posted (edited)

Hey All,

Is there a list of known-compatible video cards anywhere?

 

I pulled the old MSI GeForce GTS 450 out of my Mac Pro (server way back) and thought I'd pop it into my unRAID box to give Plex docker whatever help a 1gig card can provide but I don't want to bork anything or spend tomorrow fighting something that will never work.

 

Thanks,
~ Aaron 

Edited by DrPeril
Link to post
1 hour ago, DrPeril said:

Is there a list of known-compatible video cards anywhere?

Please look at the first post (in the Troubleshooting section) I've linked a page from Nvidia where you can check which cards are compatible with the drivers.

Link to post

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.