"

Nouveau is open-source, but it may not offer the same level of performance as the NVIDIA proprietary driver,

Nouveau may have limited support for certain NVIDIA features. 

"

 

Edited May 8, 20251 yr by fredf

45 minutes ago, fredf said:

no .... as Sander0542

I‘m not following, what do you mean with that?

Do you mean a user you always have to tag a user with @ and after that you have to click on the user name.

 

However what you‘ve linked won‘t help the user since he want‘s to utilze his GPU in a Docker container and this is not possible with nouveau at least not as it is with the official Nvidia driver.

I just installed a ASUS TUF GeForce RTX 5070 Ti 16GB GDDR7 OC Edition GPU. and updated nvidia drivers, but its not being detected in the nvidia driver section, but with this prompt it shows its there just not initiated?

 

Seems like the latest driver wont work with this GPU ?

 

 

2 hours ago, Maximo101 said:

I just installed a ASUS TUF GeForce RTX 5070 Ti 16GB GDDR7 OC Edition GPU. and updated nvidia drivers, but its not being detected in the nvidia driver section, but with this prompt it shows its there just not initiated?

 

Seems like the latest driver wont work with this GPU ?

 

On 4/23/2025 at 9:52 AM, ich777 said:

Diagnostics would help a lot for such specific questions and to diagnose the issue properly.

 

However 5000 Series cards only work with the Open Source drivers, please select the Open Source driver, wait for the Download to finish and reboot your server.

9 hours ago, Maximo101 said:

Seems like the latest driver wont work with this GPU ?

As @Mainfrezzer already pointed out, only the Open Source driver works with 5000series cards

I think everything worked for me, I don't know what happened. I haven't used transcoding for a long time. And now I wanted to try something. Maybe the cause is changing the MB. I don't know. I have NVIDIA GTX 960, tried all driver versions. It gives me the error "NVIDIA-SMI has failed because it could not communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."

 

nebanas-diagnostics-20250518-1439.zip

1 hour ago, neba said:

I think everything worked for me, I don't know what happened.

Your card is bound to VFIO as you can see from your syslog:

May 18 14:36:34 nebanas kernel: NVRM: GPU 0000:01:00.0 is already bound to vfio-pci.
May 18 14:36:34 nebanas kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
May 18 14:36:34 nebanas kernel: NVRM: This can occur when another driver was loaded and 
May 18 14:36:34 nebanas kernel: NVRM: obtained ownership of the NVIDIA device(s).
May 18 14:36:34 nebanas kernel: NVRM: Try unloading the conflicting kernel module (and/or
May 18 14:36:34 nebanas kernel: NVRM: reconfigure your kernel without the conflicting
May 18 14:36:34 nebanas kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module
May 18 14:36:34 nebanas kernel: NVRM: again.
May 18 14:36:34 nebanas kernel: NVRM: No NVIDIA devices probed.

 

and also here in your PCI devices:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:854d]
	Kernel driver in use: vfio-pci
	Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device [0403]: NVIDIA Corporation GM206 High Definition Audio Controller [10de:0fba] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:854d]
	Kernel driver in use: vfio-pci

 

Please unbind the card from VFIO and reboot, after that the card should work as usual.

 

And please remove that script, that isn't working anymore with the newer drivers:

May 18 14:37:29 nebanas emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/Unlock Nvidia/script" >/dev/null 2>&1/usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/01 Nvidia Powersafe/script" >/dev/null 2>&1

 

Yes, that's it. Thank you. As soon as something is not used for a long time, it is forgotten. Is there a way to use one graphics card for both transcoding and VM.

1 minute ago, neba said:

Is there a way to use one graphics card for both transcoding and VM.

Nope…

 

Maybe look out for a second card that you can use for transcoding, something like a Nvidia T400 will do the job just fine.

 

However I just saw that you have a 12400F maybe try to get a 12400 (without F) because these chip have a iGPU and these are capable of transcoding neraly everything and will exceed what you can currently transcode with your GTX960, so to speak use the iGPU for transcoding and your dGPU for the VM.

Thanks guys, i thought the latest was the open source one as the driver version matched. i re-downloaded the 'open source' driver, rebooted and still showing no GPU.

 

Diagnostics attached.

 

rossiserver-diagnostics-20250519-0847.zip.crdownload

4 hours ago, Maximo101 said:

rebooted and still showing no GPU.

and you are sure its eated properly, has enough power supply (also power cables checked), ...

 

from the syslog (while your diags zip is mailformatted named ...)

 

May 18 18:03:59 RossiServer kernel: NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus.
May 18 18:03:59 RossiServer kernel: NVRM: GPU 0000:02:00.0: GPU has fallen off the bus.
May 18 18:03:59 RossiServer kernel: NVRM: kgspRcAndNotifyAllChannels_IMPL: RC all channels for critical error 79.
May 18 18:03:59 RossiServer kernel: NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 78!
May 18 18:03:59 RossiServer kernel: NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from nvdEngineDumpCallbackHelper(pGpu, pPrbEnc, pNvDumpState, pEngineCallback) @ nv_debug_dump.c:274
May 18 18:03:59 RossiServer kernel: NVRM: RmLogGpuCrash: RmLogGpuCrash: failed to save GPU crash data
...
..
.

 

may take another closer look at

 

BIOS - RBAR activated (above 4g ...) check your BIOS manual

Hardware - seated properly, enough power supply, wiring ... may test another pcie slot ...

 

if nothing works, boot another OS (Windows as sample) and test if the card is actually fine ...

I appreciate the response alturismo.

BIOS rBar is active already.

The PSU is new 850 watt, and its 8pin is firmly connected to the psu and gpu. GPU light is on.

The gpu is too big for my cs380 case so i am using  a PCIe 5 riser, i unplugged it from both ends and re seated it. It was a cheaper riser cable, but it is pcie5....

 

I dont want to use another pcie slot as that main one is the pcie5 one while the others are 4.

New diagnositics attached, does it show the same issue still? Still not showing in nvida drivers plug page.

 

Quote

May 19 15:41:20 RossiServer kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
May 19 15:41:20 RossiServer kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
May 19 15:41:20 RossiServer kernel: NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:742)
May 19 15:41:20 RossiServer kernel: NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0
May 19 15:41:20 RossiServer kernel: nvidia-uvm: Loaded the UVM driver, major device number 237.
May 19 15:41:20 RossiServer kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
May 19 15:41:20 RossiServer kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
May 19 15:41:20 RossiServer kernel: NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:742)
May 19 15:41:20 RossiServer kernel: NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0

 

rossiserver-diagnostics-20250519-1542.zip

11 minutes ago, Maximo101 said:

does it show the same issue still?

Yes:

May 19 15:37:42 RossiServer kernel: NVRM: GPU at PCI:0000:02:00: GPU-b929ec99-7a23-84fc-6748-5ce8e5230fb7
May 19 15:37:42 RossiServer kernel: NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus.
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: GPU has fallen off the bus.
May 19 15:37:42 RossiServer kernel: NVRM: kgspRcAndNotifyAllChannels_IMPL: RC all channels for critical error 79.
May 19 15:37:42 RossiServer kernel: NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 78!
May 19 15:37:42 RossiServer kernel: NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from nvdEngineDumpCallbackHelper(pGpu, pPrbEnc, pNvDumpState, pEngineCallback) @ nv_debug_dump.c:274
May 19 15:37:42 RossiServer kernel: NVRM: RmLogGpuCrash: RmLogGpuCrash: failed to save GPU crash data
May 19 15:37:42 RossiServer kernel: NVRM: nvAssertFailedNoLog: Assertion failed: expectedFunc == pHistoryEntry->function @ kernel_gsp.c:2005
May 19 15:37:42 RossiServer kernel: NVRM: _kgspLogRpcSanityCheckFailure: GPU0 sanity check failed 0xf waiting for RPC response from GSP. Expected function 4097 (GSP_INIT_DONE) (0x0 0x0).
May 19 15:37:42 RossiServer kernel: NVRM: GPU0 GSP RPC buffer contains function 78 (DUMP_PROTOBUF_COMPONENT) and data 0x0000000000000000 0x0000000000000000.
May 19 15:37:42 RossiServer kernel: NVRM: GPU0 RPC history (CPU -> GSP):
May 19 15:37:42 RossiServer kernel: NVRM:     entry function                   data0              data1              ts_start           ts_end             duration actively_polling
May 19 15:37:42 RossiServer kernel: NVRM:      0    73   SET_REGISTRY          0x0000000000000000 0x0000000000000000 0x0006357687d77036 0x0000000000000000          y
May 19 15:37:42 RossiServer kernel: NVRM:     -1    72   GSP_SET_SYSTEM_INFO   0x0000000000000000 0x0000000000000000 0x0006357687d77033 0x0000000000000000           
May 19 15:37:42 RossiServer kernel: NVRM: GPU0 RPC event history (CPU <- GSP):
May 19 15:37:42 RossiServer kernel: NVRM:     entry function                   data0              data1              ts_start           ts_end             duration during_incomplete_rpc
May 19 15:37:42 RossiServer kernel: NVRM:      0    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e55811 0x0006357687e55811          y
May 19 15:37:42 RossiServer kernel: NVRM:     -1    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000001 0x0000000000000000 0x0006357687e5478a 0x0006357687e5478a          y
May 19 15:37:42 RossiServer kernel: NVRM:     -2    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e54691 0x0006357687e54691          y
May 19 15:37:42 RossiServer kernel: NVRM:     -3    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000001 0x0000000000000000 0x0006357687e54367 0x0006357687e54367          y
May 19 15:37:42 RossiServer kernel: NVRM:     -4    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e40b54 0x0006357687e40b54          y
May 19 15:37:42 RossiServer kernel: NVRM:     -5    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000001 0x0000000000000000 0x0006357687e40ad5 0x0006357687e40ad5          y
May 19 15:37:42 RossiServer kernel: NVRM:     -6    4128 GSP_POST_NOCAT_RECORD 0x0000000000000002 0x0000000000000027 0x0006357687e406c9 0x0006357687e406ca      1us y
May 19 15:37:42 RossiServer kernel: NVRM:     -7    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e3f9ff 0x0006357687e3f9ff          y

 

At least similar, you have the XID error 79 which indicates a Bus error, maybe try to set the link gen for this specific PCIe interface to Gen4 or even Gen3 <- won't matter much if you are using the card only for transcoding, you can get more information about XID errors here and what they mean.

 

However I don't recommend using a riser at all because timing needs to be very precise and only a minimal interference can cause such an issue.

5 minutes ago, Maximo101 said:

I dont want to use another pcie slot as that main one is the pcie5 one while the others are 4.

 

for testing purpose and exclude pcie slot, riser cable, ... issues, i would recommend to try it to exclude ...

 

also may the test run with a different OS, like mentioned.

 

and about pcie4 or 5 concerning some docker usage ... it really wont matter anyhow

wont even in Gaming performance high end ... may RTX 70xx will profit ... may ...

 

about pcie devices, yes, your card is there, but not really recognized ... usually there is also a model nr.

 

02:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:2c05] (rev a1)
	Subsystem: ASUSTeK Computer Inc. Device [1043:89f4]
	Kernel driver in use: nvidia
	Kernel modules: nvidia_drm, nvidia
02:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:22e9] (rev a1)
	Subsystem: NVIDIA Corporation Device [10de:0000]

 

and as the failure is the same, here now the "big" version ...

 

May 19 15:37:41 RossiServer kernel: ACPI Warning: \_SB.PC00.RP01.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20230628/nsarguments-61)
May 19 15:37:42 RossiServer kernel: NVRM: GPU at PCI:0000:02:00: GPU-b929ec99-7a23-84fc-6748-5ce8e5230fb7
May 19 15:37:42 RossiServer kernel: NVRM: Xid (PCI:0000:02:00): 79, GPU has fallen off the bus.
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: GPU has fallen off the bus.
May 19 15:37:42 RossiServer kernel: NVRM: kgspRcAndNotifyAllChannels_IMPL: RC all channels for critical error 79.
May 19 15:37:42 RossiServer kernel: NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 78!
May 19 15:37:42 RossiServer kernel: NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from nvdEngineDumpCallbackHelper(pGpu, pPrbEnc, pNvDumpState, pEngineCallback) @ nv_debug_dump.c:274
May 19 15:37:42 RossiServer kernel: NVRM: RmLogGpuCrash: RmLogGpuCrash: failed to save GPU crash data
May 19 15:37:42 RossiServer kernel: NVRM: nvAssertFailedNoLog: Assertion failed: expectedFunc == pHistoryEntry->function @ kernel_gsp.c:2005
May 19 15:37:42 RossiServer kernel: NVRM: _kgspLogRpcSanityCheckFailure: GPU0 sanity check failed 0xf waiting for RPC response from GSP. Expected function 4097 (GSP_INIT_DONE) (0x0 0x0).
May 19 15:37:42 RossiServer kernel: NVRM: GPU0 GSP RPC buffer contains function 78 (DUMP_PROTOBUF_COMPONENT) and data 0x0000000000000000 0x0000000000000000.
May 19 15:37:42 RossiServer kernel: NVRM: GPU0 RPC history (CPU -> GSP):
May 19 15:37:42 RossiServer kernel: NVRM:     entry function                   data0              data1              ts_start           ts_end             duration actively_polling
May 19 15:37:42 RossiServer kernel: NVRM:      0    73   SET_REGISTRY          0x0000000000000000 0x0000000000000000 0x0006357687d77036 0x0000000000000000          y
May 19 15:37:42 RossiServer kernel: NVRM:     -1    72   GSP_SET_SYSTEM_INFO   0x0000000000000000 0x0000000000000000 0x0006357687d77033 0x0000000000000000           
May 19 15:37:42 RossiServer kernel: NVRM: GPU0 RPC event history (CPU <- GSP):
May 19 15:37:42 RossiServer kernel: NVRM:     entry function                   data0              data1              ts_start           ts_end             duration during_incomplete_rpc
May 19 15:37:42 RossiServer kernel: NVRM:      0    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e55811 0x0006357687e55811          y
May 19 15:37:42 RossiServer kernel: NVRM:     -1    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000001 0x0000000000000000 0x0006357687e5478a 0x0006357687e5478a          y
May 19 15:37:42 RossiServer kernel: NVRM:     -2    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e54691 0x0006357687e54691          y
May 19 15:37:42 RossiServer kernel: NVRM:     -3    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000001 0x0000000000000000 0x0006357687e54367 0x0006357687e54367          y
May 19 15:37:42 RossiServer kernel: NVRM:     -4    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e40b54 0x0006357687e40b54          y
May 19 15:37:42 RossiServer kernel: NVRM:     -5    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000001 0x0000000000000000 0x0006357687e40ad5 0x0006357687e40ad5          y
May 19 15:37:42 RossiServer kernel: NVRM:     -6    4128 GSP_POST_NOCAT_RECORD 0x0000000000000002 0x0000000000000027 0x0006357687e406c9 0x0006357687e406ca      1us y
May 19 15:37:42 RossiServer kernel: NVRM:     -7    4124 GSP_LOCKDOWN_NOTICE   0x0000000000000000 0x0000000000000000 0x0006357687e3f9ff 0x0006357687e3f9ff          y
May 19 15:37:42 RossiServer kernel: CPU: 1 PID: 4554 Comm: nvidia-xconfig Tainted: G           O       6.6.68-Unraid #1
May 19 15:37:42 RossiServer kernel: Hardware name: ASUS System Product Name/PRIME Z890M-PLUS WIFI, BIOS 1404 01/09/2025
May 19 15:37:42 RossiServer kernel: Call Trace:
May 19 15:37:42 RossiServer kernel: <TASK>
May 19 15:37:42 RossiServer kernel: dump_stack_lvl+0x38/0x4a
May 19 15:37:42 RossiServer kernel: _kgspRpcRecvPoll+0x33a/0x620 [nvidia]
May 19 15:37:42 RossiServer kernel: ? kgspWaitForRmInitDone_IMPL+0x34/0x102 [nvidia]
May 19 15:37:42 RossiServer kernel: ? kgspBootstrap_GH100+0x21d/0x9c3 [nvidia]
May 19 15:37:42 RossiServer kernel: ? kgspInitRm_IMPL+0xbf9/0x1580 [nvidia]
May 19 15:37:42 RossiServer kernel: ? rm_get_uefi_console_status+0x32/0x40 [nvidia]
May 19 15:37:42 RossiServer kernel: ? RmInitAdapter+0x1132/0x1c00 [nvidia]
May 19 15:37:42 RossiServer kernel: ? preempt_latency_start+0x2b/0x46
May 19 15:37:42 RossiServer kernel: ? _raw_spin_lock_irqsave+0x1f/0x29
May 19 15:37:42 RossiServer kernel: ? rm_init_adapter+0xad/0xc0 [nvidia]
May 19 15:37:42 RossiServer kernel: ? nv_open_device+0x4da/0x7b6 [nvidia]
May 19 15:37:42 RossiServer kernel: ? nvidia_open+0x210/0x39c [nvidia]
May 19 15:37:42 RossiServer kernel: ? chrdev_open+0x15d/0x19a
May 19 15:37:42 RossiServer kernel: ? __pfx_chrdev_open+0x10/0x10
May 19 15:37:42 RossiServer kernel: ? do_dentry_open+0x1aa/0x349
May 19 15:37:42 RossiServer kernel: ? path_openat+0x8cd/0x9dc
May 19 15:37:42 RossiServer kernel: ? slab_post_alloc_hook+0x7f/0x191
May 19 15:37:42 RossiServer kernel: ? do_filp_open+0xae/0x10f
May 19 15:37:42 RossiServer kernel: ? __kmem_cache_alloc_node+0x118/0x149
May 19 15:37:42 RossiServer kernel: ? getname_flags+0x32/0x187
May 19 15:37:42 RossiServer kernel: ? kmem_cache_alloc+0x107/0x150
May 19 15:37:42 RossiServer kernel: ? kmem_cache_alloc+0x125/0x150
May 19 15:37:42 RossiServer kernel: ? _raw_spin_unlock+0x14/0x29
May 19 15:37:42 RossiServer kernel: ? do_sys_openat2+0x6d/0xbd
May 19 15:37:42 RossiServer kernel: ? do_sys_open+0x3a/0x5c
May 19 15:37:42 RossiServer kernel: ? do_syscall_64+0x57/0x7b
May 19 15:37:42 RossiServer kernel: ? entry_SYSCALL_64_after_hwframe+0x78/0xe2
May 19 15:37:42 RossiServer kernel: </TASK>
May 19 15:37:42 RossiServer kernel: NVRM: nvCheckOkFailedNoLog: Check failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from rpcRecvPoll(pGpu, pRpc, NV_VGPU_MSG_EVENT_GSP_INIT_DONE) @ kernel_gsp.c:4737
May 19 15:37:42 RossiServer kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: GPU lost from the bus [NV_ERR_GPU_IS_LOST] (0x0000000F) returned from kgspWaitForRmInitDone(pGpu, pKernelGsp) @ kernel_gsp_gh100.c:928
May 19 15:37:42 RossiServer kernel: NVRM: RmInitAdapter: Cannot initialize GSP firmware RM
May 19 15:37:42 RossiServer kernel: NVRM: iovaspaceDestruct_IMPL: 1 left-over mappings in IOVAS 0x200
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x62:0xf:1860)
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0
May 19 15:37:42 RossiServer kernel: ------------[ cut here ]------------
May 19 15:37:42 RossiServer kernel: ioremap on RAM at 0x00000001840bfff8 - 0x00000001840c7ff7
May 19 15:37:42 RossiServer kernel: WARNING: CPU: 1 PID: 4554 at arch/x86/mm/ioremap.c:216 __ioremap_caller.isra.0+0xbb/0x296
May 19 15:37:42 RossiServer kernel: Modules linked in: hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls nvidia_drm(O) nvidia_modeset(O) x86_pkg_temp_thermal intel_powerclamp nvidia(O) coretemp btusb drm_kms_helper btrtl kvm_intel btbcm kvm btintel bluetooth crct10dif_pclmul crc32_pclmul crc32c_intel input_leds ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 mei_me i2c_i801 ecdh_generic aesni_intel crypto_simd cryptd i2c_smbus wmi_bmof drm ahci r8125(O) led_class ecc libahci mei thunderbolt nvme i2c_core nvme_core vmd thermal acpi_tad video tpm_crb fan tpm_tis tpm_tis_core tpm wmi int3400_thermal backlight acpi_pad acpi_thermal_rel button
May 19 15:37:42 RossiServer kernel: CPU: 1 PID: 4554 Comm: nvidia-xconfig Tainted: G           O       6.6.68-Unraid #1
May 19 15:37:42 RossiServer kernel: Hardware name: ASUS System Product Name/PRIME Z890M-PLUS WIFI, BIOS 1404 01/09/2025
May 19 15:37:42 RossiServer kernel: RIP: 0010:__ioremap_caller.isra.0+0xbb/0x296
May 19 15:37:42 RossiServer kernel: Code: 20 01 74 2a 80 3d 88 4c 55 01 00 75 cf 48 8d 54 24 28 48 c7 c7 bc 58 23 82 c6 05 73 4c 55 01 01 48 8d 74 24 18 e8 4d 15 01 00 <0f> 0b eb ae 4c 8b 64 24 18 48 8d 4c 24 24 89 ea 48 bf 00 f0 ff ff
May 19 15:37:42 RossiServer kernel: RSP: 0018:ffffc90001407ae0 EFLAGS: 00010286
May 19 15:37:42 RossiServer kernel: RAX: 0000000000000000 RBX: ffff888101864000 RCX: 0000000000000027
May 19 15:37:42 RossiServer kernel: RDX: 0000000082440630 RSI: ffffffff822451fd RDI: 00000000ffffffff
May 19 15:37:42 RossiServer kernel: RBP: 0000000000000002 R08: 0000000000000000 R09: ffffffff82440630
May 19 15:37:42 RossiServer kernel: R10: 00007fffffffffff R11: 0000000000000031 R12: 0000000000000008
May 19 15:37:42 RossiServer kernel: R13: 00000001840bfff8 R14: 0000000000000008 R15: 00000000000007ff
May 19 15:37:42 RossiServer kernel: FS:  0000153ef78c5740(0000) GS:ffff889040240000(0000) knlGS:0000000000000000
May 19 15:37:42 RossiServer kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 19 15:37:42 RossiServer kernel: CR2: 000000000040f3e8 CR3: 00000001b4a08001 CR4: 0000000000770ee0
May 19 15:37:42 RossiServer kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 19 15:37:42 RossiServer kernel: DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400
May 19 15:37:42 RossiServer kernel: PKRU: 55555554
May 19 15:37:42 RossiServer kernel: Call Trace:
May 19 15:37:42 RossiServer kernel: <TASK>
May 19 15:37:42 RossiServer kernel: ? __warn+0x99/0x11a
May 19 15:37:42 RossiServer kernel: ? report_bug+0xd9/0x153
May 19 15:37:42 RossiServer kernel: ? __ioremap_caller.isra.0+0xbb/0x296
May 19 15:37:42 RossiServer kernel: ? handle_bug+0x53/0x7c
May 19 15:37:42 RossiServer kernel: ? exc_invalid_op+0x13/0x60
May 19 15:37:42 RossiServer kernel: ? asm_exc_invalid_op+0x16/0x20
May 19 15:37:42 RossiServer kernel: ? __ioremap_caller.isra.0+0xbb/0x296
May 19 15:37:42 RossiServer kernel: ? _raw_spin_lock_irqsave+0x1f/0x29
May 19 15:37:42 RossiServer kernel: ? __pci_enable_msix_range+0x225/0x3b9
May 19 15:37:42 RossiServer kernel: __pci_enable_msix_range+0x225/0x3b9
May 19 15:37:42 RossiServer kernel: ? nv_init_msix+0x103/0x212 [nvidia]
May 19 15:37:42 RossiServer kernel: nv_init_msix+0x155/0x212 [nvidia]
May 19 15:37:42 RossiServer kernel: nv_open_device+0x2cf/0x7b6 [nvidia]
May 19 15:37:42 RossiServer kernel: nvidia_open+0x210/0x39c [nvidia]
May 19 15:37:42 RossiServer kernel: chrdev_open+0x15d/0x19a
May 19 15:37:42 RossiServer kernel: ? __pfx_chrdev_open+0x10/0x10
May 19 15:37:42 RossiServer kernel: do_dentry_open+0x1aa/0x349
May 19 15:37:42 RossiServer kernel: path_openat+0x8cd/0x9dc
May 19 15:37:42 RossiServer kernel: ? slab_post_alloc_hook+0x7f/0x191
May 19 15:37:42 RossiServer kernel: do_filp_open+0xae/0x10f
May 19 15:37:42 RossiServer kernel: ? __kmem_cache_alloc_node+0x118/0x149
May 19 15:37:42 RossiServer kernel: ? getname_flags+0x32/0x187
May 19 15:37:42 RossiServer kernel: ? kmem_cache_alloc+0x107/0x150
May 19 15:37:42 RossiServer kernel: ? kmem_cache_alloc+0x125/0x150
May 19 15:37:42 RossiServer kernel: ? _raw_spin_unlock+0x14/0x29
May 19 15:37:42 RossiServer kernel: do_sys_openat2+0x6d/0xbd
May 19 15:37:42 RossiServer kernel: do_sys_open+0x3a/0x5c
May 19 15:37:42 RossiServer kernel: do_syscall_64+0x57/0x7b
May 19 15:37:42 RossiServer kernel: entry_SYSCALL_64_after_hwframe+0x78/0xe2
May 19 15:37:42 RossiServer kernel: RIP: 0033:0x153ef79dce7e
May 19 15:37:42 RossiServer kernel: Code: 83 e2 40 75 37 89 f0 f7 d0 a9 00 00 41 00 74 2c 80 3d d5 13 0f 00 00 74 50 89 da 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7a 48 83 c4 68 5b 5d c3 0f 1f 00 48 8d 84 24
May 19 15:37:42 RossiServer kernel: RSP: 002b:00007fffad9c6b70 EFLAGS: 00000202 ORIG_RAX: 0000000000000101
May 19 15:37:42 RossiServer kernel: RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 0000153ef79dce7e
May 19 15:37:42 RossiServer kernel: RDX: 0000000000000002 RSI: 00007fffad9c6c10 RDI: 00000000ffffff9c
May 19 15:37:42 RossiServer kernel: RBP: 00007fffad9c6c10 R08: 0000000000000001 R09: 0000000000000000
May 19 15:37:42 RossiServer kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000
May 19 15:37:42 RossiServer kernel: R13: 00007fffad9c6d5c R14: 0000000000000002 R15: 0000153ef7862320
May 19 15:37:42 RossiServer kernel: </TASK>
May 19 15:37:42 RossiServer kernel: ---[ end trace 0000000000000000 ]---
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: Failed to enable MSI-X.
May 19 15:37:42 RossiServer kernel: NVRM: osInitNvMapping: *** Cannot attach gpu
May 19 15:37:42 RossiServer kernel: NVRM: RmInitAdapter: osInitNvMapping failed, bailing out of RmInitAdapter
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: RmInitAdapter failed! (0x22:0x56:742)
May 19 15:37:42 RossiServer kernel: NVRM: GPU 0000:02:00.0: rm_init_adapter failed, device minor number 0
May 19 15:37:42 RossiServer plugin-manager: nvidia-driver.plg installed
May 19 15:37:43 RossiServer rc.local: plugin: installing: nvidia-driver.plg
May 19 15:37:43 RossiServer rc.local: Executing hook script: pre_plugin_checks
May 19 15:37:43 RossiServer rc.local: +==============================================================================
May 19 15:37:43 RossiServer rc.local: | Installing new package /boot/config/plugins/nvidia-driver/nvidia-driver-2025.03.25.txz
May 19 15:37:43 RossiServer rc.local: +==============================================================================
May 19 15:37:43 RossiServer rc.local: Verifying package nvidia-driver-2025.03.25.txz.
May 19 15:37:43 RossiServer rc.local: Installing package nvidia-driver-2025.03.25.txz:
May 19 15:37:43 RossiServer rc.local: PACKAGE DESCRIPTION:
May 19 15:37:43 RossiServer rc.local: Package nvidia-driver-2025.03.25.txz installed.
May 19 15:37:43 RossiServer rc.local: --------------------Nvidia Open Source driver v570.86.16 found locally---------------------
May 19 15:37:43 RossiServer rc.local: --------------Installation of Nvidia Open Source driver v570.86.16 successful--------------
May 19 15:37:43 RossiServer rc.local: plugin: nvidia-driver.plg installed
May 19 15:37:43 RossiServer rc.local: Executing hook script: post_plugin_checks

 

crash and looks really like some pcie issue

thanks, i can see a newer Bios from may (mine was from feb) so i might try updating that too and the Pci was set to x16, so i guess i set that to x8 to make it pcie 4 ?

 

Just now, Maximo101 said:

Pci was set to x16, so i guess i set that to x8 to make it pcie 4 ?

You can still leave it at x16 but I recommend trying PCIe gen4 or even gen3, as said above, that won't matter much if you are using it only for transcoding, for LLMs it's kind of a different story.

Just now, Maximo101 said:

so i guess i set that to x8 to make it pcie 4 ?

nope, pcie4, 5, ... is the "protocol", x8, x16 the "lanes" given

i had a feeling the cheap pcie riser might be an issue when i bought it, but may need to look at a more premium one.

 

yer i wanted to use this gpu for LLM's and AI models.

i appreciate both your responses, ill have a bit of a look into what you both mention and research a little bit since im a noob when it comes to hardware

 

Just now, Maximo101 said:

i had a feeling the cheap pcie riser might be an issue when i bought it, but may need to look at a more premium one.

It could be possible, but first I would recommend that you try to set the PCIe generation to gen4 instead of 5.

Such adapters can always cause trouble but they don't have to as long as the signal integrity is okay, however that is nearly impossible to test without proper equipment.

 

I would not recommend to use risers at all since this is always some kind of hit and miss, in addition to that it was reported that 5000 series cards often times have issues with Motherboards and PCIe gen5.

 

2 minutes ago, Maximo101 said:

yer i wanted to use this gpu for LLM's and AI models.

Update your BIOS, then set the link speed to gen4 and then see if it's working, if you get the same error then it's probably the riser, it's always a bit of hit and miss with risers.

I'm experiencing the same issue as @Maximo101

 

I have an Inno3D RTX 5070Ti and a Quadro P4000 installed in an Asus Pro-WS-X570-ACE motherboard with an AMD 5950 CPU.

My Quadro P4000 is recognized with Nvidia driver v570.144, but my 5070Ti is not.

Both GPUs are visible in the system devices.

 

The Quadro P4000 is currently used for transcoding, and I would like to utilize the 5070Ti in a Windows 11 VM.

 

I'm unsure what BIOS settings need to be changed to make this work.

server-diagnostics-20250519-1624.zip

Hello,

 

I am having an issue trying to install the Nvidia-Driver plugin. I am new to Unraid so go easy on me.

 

I have looked through the forum and on the internet and could not find how to fix this.

 

I am running on unraid 7.1.2, 3060 GPU.

1 hour ago, mrkwkns said:

and I would like to utilize the 5070Ti in a Windows 11 VM.

then just vfio bind and pass it to a VM ... no need for the driver for a VM.

3 minutes ago, alturismo said:

then just vfio bind and pass it to a VM ... no need for the driver for a VM.

Ok, thanks for your reply.
I'd either like to use a vm for gaming or Steam headless. What do i need to do if decide to use Steam headless?

2 minutes ago, mrkwkns said:

What do i need to do if decide to use Steam headless?

if its a docker, sort your issue

 

from your logs it looks like rbar, above 4g ... not activated ?

seat is correct

Power supply is sufficient

...

 

May 19 16:10:30 server kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 239
May 19 16:10:30 server kernel: 
May 19 16:10:30 server kernel: nvidia 0000:04:00.0: enabling device (0000 -> 0003)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR1 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR2 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR3 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
May 19 16:10:30 server kernel: NVRM: BAR4 is 0M @ 0x0 (PCI:0000:04:00.0)
May 19 16:10:30 server kernel: nvidia 0000:04:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
May 19 16:10:30 server kernel: nvidia 0000:0b:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
May 19 16:10:30 server kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  570.144  Thu Apr 10 20:33:29 UTC 2025
May 19 16:10:30 server kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  570.144  Thu Apr 10 20:03:03 UTC 2025
May 19 16:10:30 server kernel: [drm] [nvidia-drm] [GPU ID 0x00000400] Loading driver
May 19 16:10:30 server kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:04:00.0 on minor 0
May 19 16:10:30 server kernel: [drm] [nvidia-drm] [GPU ID 0x00000b00] Loading driver
May 19 16:10:30 server kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:0b:00.0 on minor 1

 

also, with a 50 series card you have to use the open source driver, like mentioned many times

and looks to me you are using the regular one.

 

May 19 16:11:00 server rc.local: plugin: installing: nvidia-driver.plg
May 19 16:11:00 server rc.local: Executing hook script: pre_plugin_checks
May 19 16:11:00 server rc.local: +==============================================================================
May 19 16:11:00 server rc.local: | Installing new package /boot/config/plugins/nvidia-driver/nvidia-driver-2025.03.25.txz
May 19 16:11:00 server rc.local: +==============================================================================
May 19 16:11:00 server rc.local: Verifying package nvidia-driver-2025.03.25.txz.
May 19 16:11:00 server rc.local: Installing package nvidia-driver-2025.03.25.txz:
May 19 16:11:00 server rc.local: PACKAGE DESCRIPTION:
May 19 16:11:00 server rc.local: Package nvidia-driver-2025.03.25.txz installed.
May 19 16:11:00 server rc.local: --------------------Nvidia driver v570.144 found locally---------------------
May 19 16:11:00 server rc.local: --------------Installation of Nvidia driver v570.144 successful--------------
May 19 16:11:00 server rc.local: plugin: nvidia-driver.plg installed
May 19 16:11:00 server rc.local: Executing hook script: post_plugin_checks

 

may also check pcie slots, assignments, free pcie lanes on your board, etc etc ...

as you are running an AMD System which is may not the best option cfor virtualising (personal oppinion, likely having issues), may alot trial & error, cant help too much here as its not the best combo overall.

2 hours ago, Dsopinka said:

I am running on unraid 7.1.2, 3060 GPU.

Do you have Diagnostics?

How long did you wait until you got the error? It seems that you installed the plugin already once, please remove the plugin (go to the Plugins page and make sure it's not listed there anymore) reboot and try to reinstall it and wait for the dialogue to display the DONE button.