2 minutes ago, ich777 said:

Please report that in the Steam Headless container.
Also other users where reporting that the Steam container from Linuxserver.io was working just fine.

I can't tell you why the container is crashing, in terms of the driver everything seems perfectly fine and I think now that this isn't a driver issue anymore.

And by the love of god, can you please hide such long posts behind a spoiler and avoid double and triple posting, this is not a chat like Discord.

You are completely bloating this thread.

Ok, sorry for the mess, I can remove the postings. But what about Xorg failing to initialize a screen on the host itself?

Sadly, the linuxserver.io-image is not moonlight capable, "just" web-accessible. Furthermore: it only supports 580+ full proprietary drivers, which is not an option for my blackwell gpu...

Edited April 28Apr 28 by anticholium

2 minutes ago, anticholium said:

Ok, sorry for the mess, I can remove the postings. But what about Xorg failing to initialize on the host itself?

Sorry but do you boot Unraid in GUI mode?
As far as I can see you are just trying to run Xorg without anything configured, did your run nvidia-xconfig or anything like that?
Did you configure Xorg to use your Nvidia card? Did you configure a Window manager?

I think you are getting that wrong how that works, if not everything is installed on the host (in terms of Xorg and dependencies) than it won't work properly and cause issues.

However did you yet try the Steam container from Linuxserver.io?

As said above it seems like you are the only one who has currently an issue like that, sure there where issues because I upgraded the container runtime and made a mistake in that process, but that is now all fixed.

3 minutes ago, ich777 said:

Sorry but do you boot Unraid in GUI mode?
As far as I can see you are just trying to run Xorg without anything configured, did your run nvidia-xconfig or anything like that?
Did you configure Xorg to use your Nvidia card? Did you configure a Window manager?

I think you are getting that wrong how that works, if not everything is installed on the host (in terms of Xorg and dependencies) than it won't work properly and cause issues.

However did you yet try the Steam container from Linuxserver.io?

As said above it seems like you are the only one who has currently an issue like that, sure there where issues because I upgraded the container runtime and made a mistake in that process, but that is now all fixed.

No, I'm not running Unraid in GUI mode. I configured Xorg:

cat > /tmp/xorg-nvidia-test.conf <<'EOF'

Section "ServerLayout"

Identifier "Layout0"

Screen 0 "Screen0"

EndSection

Section "Monitor"

Identifier "Monitor0"

EndSection

Section "Device"

Identifier "Device0"

Driver "nvidia"

BusID "PCI:1:0:0"

Option "AllowEmptyInitialConfiguration" "true"

Option "UseDisplayDevice" "DFP-0"

EndSection

Section "Screen"

Identifier "Screen0"

Device "Device0"

Monitor "Monitor0"

DefaultDepth 24

SubSection "Display"

Depth 24

Modes "1920x1080" "1600x900"

Virtual 1920 1080

EndSubSection

EndSection

Section "ServerFlags"

Option "AutoAddGPU" "false"

EndSection

EOF

/usr/libexec/Xorg -config /tmp/xorg-nvidia-test.conf -logfile /tmp/Xorg-nvidia-test.log -noreset -novtswitch -sharevts -nolisten tcp -verbose vt7 :77

Sadly the linuxserver.io image isn't a moonlight compatible replacement...

Edited April 28Apr 28 by anticholium

2 minutes ago, anticholium said:

No, I'm not running Unraid in GUI mode. I configured Xorg:

But wouldn't it be way easier to run Unraid in GUI mode since this would also start Xorg...?

However you still didn't answer, have you yet tried the Steam container from Linxuserver.io?
Do you have other container which are using the Nvidia driver, if yes do this containers work, like for example transcoding container, Plex, Emby, Jellyfin, Unmanic, Tadarr,...?

If one of the containers is working then it's not the driver who's at fault usually.

I also don't like the config:

Option "UseDisplayDevice" "DFP-0"

Modes "1920x1080" "1600x900"

Virtual 1920 1080

since these can cause trouble.

This is not the correct way to test things.

I didn't try the linuxserver.io image, since it doesn't have moonlight/sunshine support implemented, it's "only" web accessible... – Maybe I should try it nontheless. – Concerning the xorg test on the host itself: how would a window manager or a desktop session help without an initialized/initializable display? I thougt its roughly this: xorg starts, loads the driver, gpu/display/screen is initialized, x display is provided, then the window manager!? No? But the host xorg logs show that it's already failing at step 3, initializing the display, like in the steam-headless container. I just thought, that even a full blown desktop environment would fail also with high probability because of that? But I will try to run unraid in GUI mode and run the test again. Thank you for your efforts, I really appreciate your answers!

from the logs:
NVIDIA dlloader X Driver 595.58.03

NVIDIA GLX Module 595.58.03

NVIDIA GPU NVIDIA GeForce RTX 5060 Ti (GB206-A) at PCI:1:0:0

Option "UseDisplayDevice" "DFP-0"
...
NVIDIA(GPU-0): Failed to acquire modesetting permission.

NVIDIA(0): Failing initialization of X screen

PS: yes, Plex for eg successfully uses the gpu for transcoding
PPS: linuxserver.io: "Nvidia support only works on 580 and up full proprietary drivers (no MIT/GPL)" so not suitable for me at all (blackwell architecture, open source, you know that way better than me).

Edited April 28Apr 28 by anticholium

another unraid user was able to resolve the same bug by rolling back to 580.142, since he has a RTX 3060, so not dependent on open source kernel modules. 590.48.01 did only work partially... Any thougts on that? the linuxserver image, as expected, didn't work because of not supporting open source driver... – any "clean" option to manually downgrade to https://github.com/unraid/unraid-nvidia-driver/releases/download/6.12.54-Unraid/nvos-580.95.05-6.12.54-Unraid-1.txz ?

https://github.com/Steam-Headless/docker-steam-headless/issues/224

Edited April 30Apr 30 by anticholium

On 4/28/2026 at 9:43 PM, ich777 said:

And if you redownload the driver, does it say the checksum matches?

59 minutes ago, anticholium said:

https://github.com/Steam-Headless/docker-steam-headless/issues/224

Sorry but this was 28 days ago and with the old Nvidia Driver and the driver was compiled 5 days ago:

30 minutes ago, anticholium said:

That's the correct checksum yes:

https://github.com/unraid/unraid-nvidia-driver/releases/download/6.12.54-Unraid/nvos-595.58.03-6.12.54-Unraid-1.txz.md5

I don't know what to do else sorry.

Oh, that's weird, I obviously didn't realize that before. Thank you nontheless.

Honestly i dont know what is going on now if the configuration is the issue or the plugin itself. when you turn off the auto gpu toggle and manually selectthe drive package you want it gets the driver package but never gets the open source flag/tag along with it. I never had issues before the gpu driver auto select thing was added. Even when the auto package select chooses the open source or recommended driver i never get the open source flag/tag. RTX Blackwell 6000.

On 4/27/2026 at 10:05 PM, ich777 said:

Do you have Diagnostics or anything?

Please post your Diagnostics if something is not working.

node804-diagnostics-20260430-2206.zip I attached my diagnostics. I'm trying to fall back to 580.142, which should be supported according to the plugin's list of supported candidates but I think it still downloads the proprietary ones instead of the open modules. Is it possible to fall back to the open kernel modules for 580?

12 minutes ago, 123marvin123 said:

I attached my diagnostics. I'm trying to fall back to 580.142

No, because it isn't the OpenSource driver. Your syslog even mentions that:

Apr 30 22:04:56 Node804 kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:2d04)

Apr 30 22:04:56 Node804 kernel: NVRM: installed in this system requires use of the NVIDIA open kernel modules.

Apr 30 22:04:56 Node804 kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x56:897)

Apr 30 22:04:56 Node804 kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Why do you want to install the old driver?

Can you please also share your Diagnostics with the OpenSource driver installed?

Where does it mention that the 580 driver is compatible, do you have a screenshot?

23 minutes ago, Shadowars said:

Honestly i dont know what is going on now if the configuration is the issue or the plugin itself. when you turn off the auto gpu toggle and manually selectthe drive package you want it gets the driver package but never gets the open source flag/tag along with it. I never had issues before the gpu driver auto select thing was added. Even when the auto package select chooses the open source or recommended driver i never get the open source flag/tag. RTX Blackwell 6000.

Can you please share Diagnostics or at least a screenshot or a animation from what doesn't work or what are you exactly selecting?

Just now, ich777 said:

No, because it isn't the OpenSource driver. Your syslog even mentions that:

Apr 30 22:04:56 Node804 kernel: NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:2d04)

Apr 30 22:04:56 Node804 kernel: NVRM: installed in this system requires use of the NVIDIA open kernel modules.

Apr 30 22:04:56 Node804 kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x22:0x56:897)

Apr 30 22:04:56 Node804 kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0

Why do you want to install the old driver?

Can you please also share your Diagnostics with the OpenSource driver installed?

Where does it mention that the 580 driver is compatible, do you have a screenshot?

I want to fall back to 580.142 because the 595.58.03 driver crashes when I turn off my virtual machine and the GPU control gets passed back to Unraid:

Apr 27 16:53:57 Node804 kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver

Apr 27 16:53:59 Node804 kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1

Apr 27 16:53:59 Node804 kernel: BUG: kernel NULL pointer dereference, address: 000000000000001c

Apr 27 16:53:59 Node804 kernel: #PF: supervisor read access in kernel mode

Apr 27 16:53:59 Node804 kernel: #PF: error_code(0x0000) - not-present page

Apr 27 16:53:59 Node804 kernel: PGD 0 P4D 0

Apr 27 16:53:59 Node804 kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI

Apr 27 16:53:59 Node804 kernel: CPU: 10 UID: 0 PID: 29120 Comm: rpc-libvirtd Tainted: P           O       6.12.54-Unraid #1

Apr 27 16:53:59 Node804 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE

Apr 27 16:53:59 Node804 kernel: Hardware name: BIOSTAR Group B760MX2-E PRO D4/B760MX2-E PRO D4, BIOS 5.27 05/08/2025

Apr 27 16:53:59 Node804 kernel: RIP: 0010:nv_audio_dynamic_power+0x8f/0x110 [nvidia]

Apr 27 16:53:59 Node804 kernel: Code: c0 74 7c f6 80 a4 01 00 00 10 75 73 48 8b 80 40 01 00 00 48 85 c0 74 67 48 8b 90 a8 01 00 00 48 05 a0 01 00 00 48 39 c2 74 55 <83> 7a 1c 03 75 10 48 8b 7a 20 48 83 bf 40 03 00 00 00 75 08 eb 3f

Apr 27 16:53:59 Node804 kernel: RSP: 0018:ffffc90002146718 EFLAGS: 00010207

Apr 27 16:53:59 Node804 kernel: RAX: ffff8881043f21a0 RBX: 0000000000000000 RCX: ffff888101e103b8

Apr 27 16:53:59 Node804 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888101ffd100

Apr 27 16:53:59 Node804 kernel: RBP: ffffc90002146730 R08: ffff888101ffc000 R09: 00000000ffffffff

Apr 27 16:53:59 Node804 kernel: R10: 00000000ffffffff R11: ffffffffa1542778 R12: ffffc90002146810

Apr 27 16:53:59 Node804 kernel: R13: ffffffffa0d10f80 R14: ffff8889ea559020 R15: ffffc90002146940

Apr 27 16:53:59 Node804 kernel: FS:  000014cdb0e466c0(0000) GS:ffff88903fc80000(0000) knlGS:0000000000000000

Apr 27 16:53:59 Node804 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Apr 27 16:53:59 Node804 kernel: CR2: 000000000000001c CR3: 00000001d958e001 CR4: 0000000000772ef0

Apr 27 16:53:59 Node804 kernel: PKRU: 55555554

Apr 27 16:53:59 Node804 kernel: Call Trace:

Apr 27 16:53:59 Node804 kernel: <TASK>

Apr 27 16:53:59 Node804 kernel: subdeviceCtrlCmdOsUnixAudioDynamicPower_IMPL+0x27/0x2b [nvidia]

Apr 27 16:53:59 Node804 kernel: ? resControl_IMPL+0x1b1/0x1c0 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? gpuresControl_IMPL+0x4c/0xa0 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? serverControl+0x47e/0x590 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? rawspin_lock_irqsave+0x1f/0x30

Apr 27 16:53:59 Node804 kernel: ? _rmapiRmControl+0x4f2/0x820 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? rmapiControlWithSecInfo+0x79/0x140 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? rmapiControlWithSecInfoTls+0x8f/0xf0 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? _nv04ControlWithSecInfo+0x8d/0xa0 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? _nv04ControlWithSecInfo+0x8d/0xa0 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? Nv04ControlKernel+0x63/0x70 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? nvkms_call_rm+0x44/0x80 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvRmApiControl+0x46/0x50 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? RmSetELDAudioCaps+0xac/0x170 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvHdmiDpEnableDisableAudio+0xdc/0x420 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? KickoffProposedModeSetHwState+0x528/0xeb0 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvSetDispModeEvo+0x3162/0x40b0 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? Flip+0xf0/0xf0 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvKmsIoctl+0xf2/0x240 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvkms_ioctl_common+0x49/0x70 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvkms_ioctl_from_kapi_try_pmlock+0x47/0x70 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? ApplyModeSetConfig+0x357/0xba0 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nv_drm_atomic_apply_modeset_config+0x41a/0x570 [nvidia_drm]

Apr 27 16:53:59 Node804 kernel: ? nv_drm_atomic_commit+0x1c4/0x430 [nvidia_drm]

Apr 27 16:53:59 Node804 kernel: ? drm_atomic_check_only+0x6f3/0x820 [drm]

Apr 27 16:53:59 Node804 kernel: ? drm_atomic_commit+0xa8/0xd0 [drm]

Apr 27 16:53:59 Node804 kernel: ? pfx_drm_printfn_info+0x10/0x10 [drm]

Apr 27 16:53:59 Node804 kernel: ? pfx_drm_printfn_info+0x10/0x10 [drm]

Apr 27 16:53:59 Node804 kernel: ? drm_client_modeset_commit_atomic+0x155/0x1e0 [drm]

Apr 27 16:53:59 Node804 kernel: ? drm_client_modeset_commit_locked+0x3a/0x130 [drm]

Apr 27 16:53:59 Node804 kernel: ? drm_client_modeset_commit+0x28/0x40 [drm]

Apr 27 16:53:59 Node804 kernel: ? __drm_fb_helper_restore_fbdev_mode_unlocked+0x4a/0x90 [drm_kms_helper]

Apr 27 16:53:59 Node804 kernel: ? drm_fb_helper_set_par+0x29/0x40 [drm_kms_helper]

Apr 27 16:53:59 Node804 kernel: ? fbcon_init+0x34f/0x430

Apr 27 16:53:59 Node804 kernel: ? visual_init+0xbd/0x120

Apr 27 16:53:59 Node804 kernel: ? do_bind_con_driver.isra.0+0x1aa/0x2b0

Apr 27 16:53:59 Node804 kernel: ? do_take_over_console+0x158/0x170

Apr 27 16:53:59 Node804 kernel: ? do_fbcon_takeover+0x5c/0xa0

Apr 27 16:53:59 Node804 kernel: ? fbcon_fb_registered+0x15a/0x180

Apr 27 16:53:59 Node804 kernel: ? register_framebuffer+0x1f9/0x210

Apr 27 16:53:59 Node804 kernel: ? __drm_fb_helper_initial_config_and_unlock+0x393/0x490 [drm_kms_helper]

Apr 27 16:53:59 Node804 kernel: ? drm_fbdev_client_hotplug+0x6c/0xa0 [drm_kms_helper]

Apr 27 16:53:59 Node804 kernel: ? drm_client_register+0x5a/0x90 [drm]

Apr 27 16:53:59 Node804 kernel: ? drm_fbdev_client_setup+0x135/0x150 [drm_kms_helper]

Apr 27 16:53:59 Node804 kernel: ? drm_client_setup+0xe/0x40 [drm_kms_helper]

Apr 27 16:53:59 Node804 kernel: ? nv_drm_register_drm_device+0x180/0x1e0 [nvidia_drm]

Apr 27 16:53:59 Node804 kernel: ? nvKmsKapiProbe+0x41/0x60 [nvidia_modeset]

Apr 27 16:53:59 Node804 kernel: ? nvidia_modeset_probe+0x85/0xb0 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? nv_pci_probe+0xd21/0xe50 [nvidia]

Apr 27 16:53:59 Node804 kernel: ? mutex_lock+0xe/0x30

Apr 27 16:53:59 Node804 kernel: ? pfx_device_attach_driver+0x10/0x10

Apr 27 16:53:59 Node804 kernel: ? local_pci_probe+0x3a/0x90

Apr 27 16:53:59 Node804 kernel: ? pci_device_probe+0x192/0x1f0

Apr 27 16:53:59 Node804 kernel: ? sysfs_do_create_link_sd+0x7e/0xb0

Apr 27 16:53:59 Node804 kernel: ? pfx_device_attach_driver+0x10/0x10

Apr 27 16:53:59 Node804 kernel: ? really_probe+0x10a/0x250

Apr 27 16:53:59 Node804 kernel: ? __driver_probe_device+0xbe/0xf0

Apr 27 16:53:59 Node804 kernel: ? driver_probe_device+0x1f/0x80

Apr 27 16:53:59 Node804 kernel: ? __device_attach_driver+0x7f/0xa0

Apr 27 16:53:59 Node804 kernel: ? bus_for_each_drv+0x91/0xc0

Apr 27 16:53:59 Node804 kernel: ? __device_attach+0xa5/0x130

Apr 27 16:53:59 Node804 kernel: ? bus_rescan_devices_helper+0x3a/0x70

Apr 27 16:53:59 Node804 kernel: ? drivers_probe_store+0x34/0x50

Apr 27 16:53:59 Node804 kernel: ? kernfs_fop_write_iter+0x101/0x150

Apr 27 16:53:59 Node804 kernel: ? vfs_write+0x13b/0x1e0

Apr 27 16:53:59 Node804 kernel: ? __pfx_kernfs_fop_write_iter+0x10/0x10

Apr 27 16:53:59 Node804 kernel: ? ksys_write+0x71/0xc0

Apr 27 16:53:59 Node804 kernel: ? do_syscall_64+0x68/0xe0

Apr 27 16:53:59 Node804 kernel: ? entry_SYSCALL_64_after_hwframe+0x76/0x7e

Apr 27 16:53:59 Node804 kernel: </TASK>

Apr 27 16:53:59 Node804 kernel: Modules linked in: xt_set xt_pkttype nft_compat ip_set_hash_net ip_set nft_ct nft_masq nft_chain_nat nvidia_uvm(O) xt_CHECKSUM ipt_REJECT nf_reject_ipv4 vhost_net vhost vhost_iotlb tap macvlan br_netfilter veth nf_conntrack_netlink xt_nat xfrm_user xfrm_algo xt_addrtype af_packet dm_crypt dm_mod md_mod algif_hash algif_skcipher af_alg cmac bnep zfs(PO) spl(O) xt_connmark xt_conntrack ip6table_mangle iptable_mangle xt_MASQUERADE xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls xe drm_gpuvm drm_exec gpu_sched drm_suballoc_helper intel_rapl_msr intel_rapl_common iwlmvm x86_pkg_temp_thermal intel_powerclamp mac80211 coretemp kvm_intel nvidia_drm(O) libarc4 nvidia_modeset(O) mei_pxp i915 mei_hdcp kvm wmi_bmof iwlwifi iosf_mbi drm_buddy i2c_algo_bit nvidia(O) drm_display_helper btusb crct10dif_pclmul crc32_pclmul drm_ttm_helper

Apr 27 16:53:59 Node804 kernel: crc32c_intel ghash_clmulni_intel btrtl ttm sha512_ssse3 btbcm sha256_ssse3 btintel sha1_ssse3 ch341 drm_kms_helper bluetooth usbserial cdc_acm cfg80211 aesni_intel crypto_simd drm cryptd rapl intel_cstate joydev input_leds led_class r8125(O) intel_uncore mei_me i2c_i801 intel_gtt tpm_crb agpgart i2c_smbus tpm_tis mei rfkill tpm_tis_core i2c_core tpm thermal fan button video libaescfb wmi ecdh_generic ecc backlight acpi_tad acpi_pad [last unloaded: md_mod]

Apr 27 16:53:59 Node804 kernel: CR2: 000000000000001c

Apr 27 16:53:59 Node804 kernel: ---[ end trace 0000000000000000 ]---

Full log in attachments.

The issue might be fixed in nvos-595.71.05.

kernel-log.txt

Edited April 30Apr 30 by 123marvin123

just upgrade unraid to 7.2.5 docker that use --gpus all failed to start

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

/sbin/ldconfig

/sbin/ldconfig: /usr/lib64/libOpenGL.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib64/libGLdispatch.so.0 is not a symbolic link

/sbin/ldconfig: /usr/lib64/libGLX.so.0 is not a symbolic link

switch driver version and reinstall plugin won't help (each step reboot)

10 hours ago, 123marvin123 said:

The issue might be fixed in nvos-595.71.05.

Please upgrade to Unraid 7.2.5 since the open source driver version 595.71.05 is available there.

Please also note that you can only use the Open Source driver with your 50 series card, no other driver will work.

1 hour ago, Gvon said:

switch driver version and reinstall plugin won't help (each step reboot)

Diagnostics and your docker run command from the container would be also be interesting.

Hey, I have issues with the combination of update helper plugin + nvidia drivers + owning an old "unsupported GPU" like the GTX 1060. I updated to 7.2.5 and the update helper plugin installed the latest driver.

This forced me to reinstall the latest supported driver for this GPU and reboot.
Is it possible to configure the plugin to not auto update the drivers on Pascal GPUs?
Also for some reason I can't find the update helper plugin in the "Plugin" tab. why is that? 😅

1 minute ago, Ikeasofa said:

Is it possible to configure the plugin to not auto update the drivers on Pascal GPUs?

This is already possible but you have to set the driver to the specific driver version 580.x

2 minutes ago, Ikeasofa said:

Also for some reason I can't find the update helper plugin in the "Plugin" tab. why is that? 😅

The Plugin update helper is part of the driver plugins and not a dedicated plugin.

For all of you having issue with containers not correctly starting, please update the plugin to the latest version 2026.05.01 and reboot your Server.

I think its already set to it?
Not 100% sure. Keep in mind I haven't rebooted yet just in case I have to set some settings. I don't want to criticize your plugin here btw. I just want to avoid having to reboot twice on any upcoming update :)

Just now, Ikeasofa said:

I think its already set to it?

What did the plugin update helper say before rebooting?

Did you wait until it said it's safe to reboot?

Yeah, of course.

This is the log before reboot

26 minutes ago, ich777 said:

Diagnostics and your docker run command from the container would be also be interesting.

thank for reply i have NVIDIA GeForce RTX 4060 now switch to open source driver still the same error

docker run
  -d
  --name='llama.cpp'
  --net='br0'
  --ip='192.168.0.82'
  --pids-limit 2048
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="GNAS"
  -e HOST_CONTAINERNAME="llama.cpp"
  -e 'TCP_PORT_8000'='8080'
  -e 'CA_TS_FALLBACK_DIR'='/models'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/'
  -v '/mnt/ncache/appdata/llama.cpp/models':'/models':'rw'
  --gpus all 'ghcr.io/ggml-org/llama.cpp:server-cuda'

f9238272f96172115220e760c98ae6daab201d5664e67e80b912c1592ff8c1e8
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

Run 'docker run --help' for more information

The command failed.

Edited May 1May 1 by Gvon

3 minutes ago, Ikeasofa said:

Yeah, of course.

I look into that, maybe an issue with the plugin update helper.