Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] Nvidia-Driver

Featured Replies

53 minutes ago, ich777 said:

Build is running, please give it a bit, in the meantime please uninstall the plugin.

I'll update this post here when it's done.

EDIT: @rpetrina14 the driver is now rebuilt, please install the plugin again and reboot afterwards.

Unraid 7.2.4 GPU is a RTX2060 SUPER with driver 590.48.01.

  -d
  --name='orcaslicer'
  --net='bridge'
  --pids-limit 2048
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Capkinserver"
  -e HOST_CONTAINERNAME="orcaslicer"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:3001]'
  -l net.unraid.docker.icon=
  -p '3002:3000/tcp'
  -p '3001:3001/tcp'
  -v '/mnt/user/public/3D Druck/':'/3dfiles':'rw'
  -v '/mnt/user/appdata/orcaslicer':'/config':'rw'
  --runtime=nvidia
  --gpus=all 'lscr.io/linuxserver/orcaslicer'

293896f0896c6c02c800716a997b180f930883aa42cf50c8a9ae32c0f9a909bb

Logs before opening WebUI

ERROR: driverInitFileInfo 578 result=11ERROR: init 664 result=11ERROR: init 250 result=11INFO:selkies.__main__:Starting mode 'websockets'...

INFO:selkies.__main__:Starting Selkies in 'websockets' mode.

INFO:data_websocket:pcmflux library found. Audio capture is available.

INFO:data_websocket:pixelflux library found. Striped encoding modes available.

pci id for fd 15: 10de:1f06, driver (null)

pci id for fd 16: 10de:1f06, driver (null)

pci id for fd 17: 10de:1f06, driver (null)

pci id for fd 16: 10de:1f06, driver (null)

pci id for fd 17: 10de:1f06, driver (null)

pci id for fd 14: 10de:1f06, driver (null)

pci id for fd 18: 10de:1f06, driver (null)

pci id for fd 19: 10de:1f06, driver (null)

pci id for fd 18: 10de:1f06, driver (null)

pci id for fd 19: 10de:1f06, driver (null)

INFO:root:Expected C js_config_t size (from ctypes): 1354 bytes

KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied

INFO:main:Upload directory ensured: /config/Desktop

INFO:main:Legacy Mode ENABLED (SELKIES_MASTER_TOKEN is not set).

INFO:main:Starting Selkies (WebSocket Mode) with settings: {'_setting_definitions': [{'name': 'audio_enabled', 'type': 'bool', 'default': True, 'help': 'Enable server-to-client audio streaming.'}, {'name': 'microphone_enabled', 'type': 'bool', 'default': True, 'help': 'Enable client-to-server microphone forwarding.'}, {'name': 'gamepad_enabled', 'type': 'bool', 'default': True, 'help': 'Enable gamepad support.'}, {'name': 'clipboard_enabled', 'type': 'bool', 'default': True, 'help': 'Enable clipboard synchronization.'}, {'name': 'clipboard_in_enabled', 'type': 'bool', 'default': True, 'help': 'Enable client-to-server clipboard synchronization.'}, {'name': 'clipboard_out_enabled', 'type': 'bool', 'default': True, 'help': 'Enable server-to-client clipboard synchronization.'}, {'name': 'command_enabled', 'type': 'bool', 'default': True, 'help': 'Enable parsing of command websocket messages.'}, {'name': 'file_transfers', 'type': 'list', 'default': 'upload,download', 'meta': {'allowed': ['upload', 'download']}, 'help': 'Allowed file transfer directions (comma-separated: "upload,download"). Set to "" or "none" to disable.'}, {'name': 'framerate', 'type': 'range', 'default': '8-120', 'meta': {'default_value': 60}, 'help': 'Allowed framerate range (e.g., "8-165") or a fixed value (e.g., "60").'}, {'name': 'audio_bitrate', 'type': 'enum', 'default': '320000', 'meta': {'allowed': ['64000', '128000', '192000', '256000', '320000']}, 'help': 'The default audio bitrate.'}, {'name': 'is_manual_resolution_mode', 'type': 'bool', 'default': False, 'help': 'Lock the resolution to the manual width/height values.'}, {'name': 'manual_width', 'type': 'int', 'default': 0, 'help': 'Lock width to a fixed value. Setting this forces manual resolution mode.'}, {'name': 'manual_height', 'type': 'int', 'default': 0, 'help': 'Lock height to a fixed value. Setting this forces manual resolution mode.'}, {'name': 'scaling_dpi', 'type': 'enum', 'default': '96', 'meta': {'allowed': ['96', '120', '144', '168', '192', '216', '240', '264', '288']}, 'help': 'The default DPI for UI scaling.'}, {'name': 'enable_binary_clipboard', 'type': 'bool', 'default': False, 'help': 'Allow binary data (e.g., images) on the clipboard.'}, {'name': 'use_browser_cursors', 'type': 'bool', 'default': False, 'help': 'Use browser CSS cursors instead of rendering to canvas.'}, {'name': 'use_css_scaling', 'type': 'bool', 'default': False, 'help': 'HiDPI when false, if true a lower resolution is sent from the client and the canvas is stretched.'}, {'name': 'ui_title', 'type': 'str', 'default': 'Selkies', 'help': 'Title in top left corner of sidebar.'}, {'name': 'ui_show_logo', 'type': 'bool', 'default': True, 'help': 'Show the Selkies logo in the sidebar.'}, {'name': 'ui_show_core_buttons', 'type': 'bool', 'default': True, 'help': 'Show the core components buttons display, audio, microphone, and gamepad.'}, {'name': 'ui_show_sidebar', 'type': 'bool', 'default': True, 'help': 'Show the main sidebar UI.'}, {'name': 'ui_sidebar_show_video_settings', 'type': 'bool', 'default': True, 'help': 'Show the video settings section in the sidebar.'}, {'name': 'ui_sidebar_show_screen_settings', 'type': 'bool', 'default': True, 'help': 'Show the screen settings section in the sidebar.'}, {'name': 'ui_sidebar_show_audio_settings', 'type': 'bool', 'default': True, 'help': 'Show the audio settings section in the sidebar.'}, {'name': 'ui_sidebar_show_stats', 'type': 'bool', 'default': True, 'help': 'Show the stats section in the sidebar.'}, {'name': 'ui_sidebar_show_clipboard', 'type': 'bool', 'default': True, 'help': 'Show the clipboard section in the sidebar.'}, {'name': 'ui_sidebar_show_files', 'type': 'bool', 'default': True, 'help': 'Show the file transfer section in the sidebar.'}, {'name': 'ui_sidebar_show_apps', 'type': 'bool', 'default': True, 'help': 'Show the applications section in the sidebar.'}, {'name': 'ui_sidebar_show_sharing', 'type': 'bool', 'default': True, 'help': 'Show the sharing section in the sidebar.'}, {'name': 'ui_sidebar_show_gamepads', 'type': 'bool', 'default': True, 'help': 'Show the gamepads section in the sidebar.'}, {'name': 'ui_sidebar_show_fullscreen', 'type': 'bool', 'default': True, 'help': 'Show the fullscreen button in the sidebar.'}, {'name': 'ui_sidebar_show_gaming_mode', 'type': 'bool', 'default': True, 'help': 'Show the gaming mode button in the sidebar.'}, {'name': 'ui_sidebar_show_trackpad', 'type': 'bool', 'default': True, 'help': 'Show the virtual trackpad button in the sidebar.'}, {'name': 'ui_sidebar_show_keyboard_button', 'type': 'bool', 'default': True, 'help': 'Show the on-screen keyboard button in the display area.'}, {'name': 'ui_sidebar_show_soft_buttons', 'type': 'bool', 'default': True, 'help': 'Show the soft buttons section in the sidebar.'}, {'name': 'enable_sharing', 'type': 'bool', 'default': True, 'help': 'Master toggle for all sharing features.'}, {'name': 'enable_collab', 'type': 'bool', 'default': True, 'help': 'Enable collaborative (read-write) sharing link.'}, {'name': 'enable_shared', 'type': 'bool', 'default': True, 'help': 'Enable view-only sharing links.'}, {'name': 'enable_player2', 'type': 'bool', 'default': True, 'help': 'Enable sharing link for gamepad player 2.'}, {'name': 'enable_player3', 'type': 'bool', 'default': True, 'help': 'Enable sharing link for gamepad player 3.'}, {'name': 'enable_player4', 'type': 'bool', 'default': True, 'help': 'Enable sharing link for gamepad player 4.'}, {'name': 'debug', 'type': 'bool', 'default': False, 'help': 'Enable debug logging.'}, {'name': 'mode', 'type': 'str', 'default': 'websockets', 'help': "Specify the mode: 'webrtc' or 'websockets'; defaults to websockets"}, {'name': 'enable_dual_mode', 'type': 'bool', 'default': False, 'help': 'Enable switching Streaming modes from UI'}, {'name': 'audio_device_name', 'type': 'str', 'default': 'output.monitor', 'help': 'Audio device name for pcmflux capture.'}, {'name': 'encoder', 'type': 'enum', 'default': 'x264enc', 'meta': {'allowed': ['x264enc', 'x264enc-striped', 'jpeg']}, 'help': 'The default video encoder.'}, {'name': 'h264_crf', 'type': 'range', 'default': '5-50', 'meta': {'default_value': 25}, 'help': 'Allowed H.264 CRF range (e.g., "5-50") or a fixed value.'}, {'name': 'jpeg_quality', 'type': 'range', 'default': '1-100', 'meta': {'default_value': 40}, 'help': 'Allowed JPEG quality range (e.g., "1-100") or a fixed value.'}, {'name': 'h264_fullcolor', 'type': 'bool', 'default': False, 'help': 'Enable H.264 full color range for pixelflux encoders.'}, {'name': 'h264_streaming_mode', 'type': 'bool', 'default': False, 'help': 'Enable H.264 streaming mode for pixelflux encoders.'}, {'name': 'use_cpu', 'type': 'bool', 'default': False, 'help': 'Force CPU-based encoding for pixelflux.'}, {'name': 'use_paint_over_quality', 'type': 'bool', 'default': True, 'help': 'Enable high-quality paint-over for static scenes.'}, {'name': 'paint_over_jpeg_quality', 'type': 'range', 'default': '1-100', 'meta': {'default_value': 90}, 'help': 'Allowed JPEG paint-over quality range or a fixed value.'}, {'name': 'h264_paintover_crf', 'type': 'range', 'default': '5-50', 'meta': {'default_value': 18}, 'help': 'Allowed H.264 paint-over CRF range or a fixed value.'}, {'name': 'h264_paintover_burst_frames', 'type': 'range', 'default': '1-30', 'meta': {'default_value': 5}, 'help': 'Allowed H.264 paint-over burst frames range or a fixed value.'}, {'name': 'second_screen', 'type': 'bool', 'default': True, 'help': 'Enable support for a second monitor/display.'}, {'name': 'port', 'type': 'int', 'default': 8081, 'env_var': 'CUSTOM_WS_PORT', 'help': 'Port for the data websocket server.'}, {'name': 'control_port', 'type': 'int', 'default': 8083, 'help': 'Port for the internal control plane API.'}, {'name': 'master_token', 'type': 'str', 'default': '', 'help': 'Master token to enable secure mode and protect the control plane API.'}, {'name': 'dri_node', 'type': 'str', 'default': '', 'env_var': 'DRI_NODE', 'help': 'Path to the DRI render node for VA-API.'}, {'name': 'watermark_path', 'type': 'str', 'default': '', 'env_var': 'WATERMARK_PNG', 'help': 'Absolute path to the watermark PNG file.'}, {'name': 'watermark_location', 'type': 'int', 'default': -1, 'env_var': 'WATERMARK_LOCATION', 'help': 'Watermark location enum (0-6).'}, {'name': 'wayland_socket_index', 'type': 'int', 'default': 0, 'help': 'Index for the Wayland command socket (e.g. 0 for wayland-0).'}], 'audio_enabled': (True, False), 'microphone_enabled': (True, False), 'gamepad_enabled': (False, False), 'clipboard_enabled': (True, False), 'clipboard_in_enabled': (True, False), 'clipboard_out_enabled': (True, False), 'command_enabled': (True, False), 'file_transfers': ['upload', 'download'], 'framerate': (8, 120), 'audio_bitrate': '320000', 'is_manual_resolution_mode': (False, False), 'manual_width': 0, 'manual_height': 0, 'scaling_dpi': '96', 'enable_binary_clipboard': (False, False), 'use_browser_cursors': (False, False), 'use_css_scaling': (False, False), 'ui_title': 'Selkies', 'ui_show_logo': (True, False), 'ui_show_core_buttons': (True, False), 'ui_show_sidebar': (True, False), 'ui_sidebar_show_video_settings': (True, False), 'ui_sidebar_show_screen_settings': (True, False), 'ui_sidebar_show_audio_settings': (True, False), 'ui_sidebar_show_stats': (True, False), 'ui_sidebar_show_clipboard': (True, False), 'ui_sidebar_show_files': (True, False), 'ui_sidebar_show_apps': (True, False), 'ui_sidebar_show_sharing': (True, False), 'ui_sidebar_show_gamepads': (False, False), 'ui_sidebar_show_fullscreen': (True, False), 'ui_sidebar_show_gaming_mode': (True, False), 'ui_sidebar_show_trackpad': (True, False), 'ui_sidebar_show_keyboard_button': (True, False), 'ui_sidebar_show_soft_buttons': (True, False), 'enable_sharing': (True, False), 'enable_collab': (True, False), 'enable_shared': (True, False), 'enable_player2': (False, False), 'enable_player3': (False, False), 'enable_player4': (True, False), 'debug': (False, False), 'mode': 'websockets', 'enable_dual_mode': (False, False), 'audio_device_name': 'output.monitor', 'encoder': 'x264enc', 'h264_crf': (5, 50), 'jpeg_quality': (1, 100), 'h264_fullcolor': (False, False), 'h264_streaming_mode': (False, False), 'use_cpu': (False, False), 'use_paint_over_quality': (True, False), 'paint_over_jpeg_quality': (1, 100), 'h264_paintover_crf': (5, 50), 'h264_paintover_burst_frames': (1, 30), 'second_screen': (False, False), 'port': 8082, 'control_port': 8083, 'master_token': '', 'dri_node': '/dev/dri/renderD128', 'watermark_path': '', 'watermark_location': -1, 'wayland_socket_index': 0}

INFO:main:Initial Encoder: x264enc, Framerate: 60

INFO:main:SelkiesStreamingApp initialized: encoder=x264enc, display=1024x768

INFO:webrtc_input:Wayland input injection initialized.

INFO:webrtc_input:Built Wayland scancode map with 456 keys.

INFO:main:All main components initialized. Running server...

INFO:webrtc_input:Initializing 4 persistent gamepad instances...

INFO:root:Packed js_config payload for 'Microsoft X-Box 360 pad' (js0): len=1360 bytes. Name='Microsoft X-Box 360 pad', Vendor=0x045e, Product=0x028e, Version=0x0100, Reported Buttons=11 (Array capacity: 512), Reported Axes=8 (Array capacity: 64)

INFO:selkies_gamepad:Gamepad configured. JS socket: /tmp/selkies_js0.sock, EVDEV socket: /tmp/selkies_event1000.sock. Using fixed config: Microsoft X-Box 360 pad

INFO:webrtc_input:Initialized and started persistent gamepad instance for index 0 (Name: 'Microsoft X-Box 360 pad', JS: /tmp/selkies_js0.sock, EVDEV: /tmp/selkies_event1000.sock).

INFO:root:Packed js_config payload for 'Microsoft X-Box 360 pad' (js1): len=1360 bytes. Name='Microsoft X-Box 360 pad', Vendor=0x045e, Product=0x028e, Version=0x0100, Reported Buttons=11 (Array capacity: 512), Reported Axes=8 (Array capacity: 64)

INFO:selkies_gamepad:Gamepad configured. JS socket: /tmp/selkies_js1.sock, EVDEV socket: /tmp/selkies_event1001.sock. Using fixed config: Microsoft X-Box 360 pad

INFO:webrtc_input:Initialized and started persistent gamepad instance for index 1 (Name: 'Microsoft X-Box 360 pad', JS: /tmp/selkies_js1.sock, EVDEV: /tmp/selkies_event1001.sock).

INFO:root:Packed js_config payload for 'Microsoft X-Box 360 pad' (js2): len=1360 bytes. Name='Microsoft X-Box 360 pad', Vendor=0x045e, Product=0x028e, Version=0x0100, Reported Buttons=11 (Array capacity: 512), Reported Axes=8 (Array capacity: 64)

INFO:selkies_gamepad:Gamepad configured. JS socket: /tmp/selkies_js2.sock, EVDEV socket: /tmp/selkies_event1002.sock. Using fixed config: Microsoft X-Box 360 pad

INFO:webrtc_input:Initialized and started persistent gamepad instance for index 2 (Name: 'Microsoft X-Box 360 pad', JS: /tmp/selkies_js2.sock, EVDEV: /tmp/selkies_event1002.sock).

INFO:root:Packed js_config payload for 'Microsoft X-Box 360 pad' (js3): len=1360 bytes. Name='Microsoft X-Box 360 pad', Vendor=0x045e, Product=0x028e, Version=0x0100, Reported Buttons=11 (Array capacity: 512), Reported Axes=8 (Array capacity: 64)

INFO:selkies_gamepad:Gamepad configured. JS socket: /tmp/selkies_js3.sock, EVDEV socket: /tmp/selkies_event1003.sock. Using fixed config: Microsoft X-Box 360 pad

INFO:webrtc_input:Initialized and started persistent gamepad instance for index 3 (Name: 'Microsoft X-Box 360 pad', JS: /tmp/selkies_js3.sock, EVDEV: /tmp/selkies_event1003.sock).

INFO:webrtc_input:Clipboard monitor running (binary mode: False)

INFO:webrtc_input:Wayland mode: Cursor monitor disabled (handled by compositor callback).

INFO:selkies_gamepad:Gamepad /tmp/selkies_js0.sock: Event processor started.

INFO:selkies_gamepad:JS interposer server listening on /tmp/selkies_js0.sock

INFO:selkies_gamepad:Gamepad /tmp/selkies_js1.sock: Event processor started.

INFO:selkies_gamepad:JS interposer server listening on /tmp/selkies_js1.sock

INFO:selkies_gamepad:Gamepad /tmp/selkies_js2.sock: Event processor started.

INFO:selkies_gamepad:JS interposer server listening on /tmp/selkies_js2.sock

INFO:selkies_gamepad:Gamepad /tmp/selkies_js3.sock: Event processor started.

INFO:selkies_gamepad:JS interposer server listening on /tmp/selkies_js3.sock

INFO:selkies_gamepad:EVDEV interposer server listening on /tmp/selkies_event1000.sock

INFO:selkies_gamepad:EVDEV interposer server listening on /tmp/selkies_event1001.sock

INFO:selkies_gamepad:EVDEV interposer server listening on /tmp/selkies_event1002.sock

INFO:selkies_gamepad:EVDEV interposer server listening on /tmp/selkies_event1003.sock

INFO:data_websocket:Data WebSocket Server listening on port 8082

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID: 99

User GID: 100

───────────────────────────────────────

Linuxserver.io version: v2.3.2-ls13

Build-date: 2026-04-14T13:04:24+00:00

───────────────────────────────────────

[ls.io-init] Generating labwc rc.xml from template

/usr/bin/nvidia-smi

**** creating video group videonlgb with id 18 ****

**** adding /dev/dri/renderD128 to video group videonlgb with id 18 ****

**** permissions for /dev/dri/card0 are good ****

by-path

card0

renderD128

**** NVIDIA GPU detected ****

**** Setting up OpenCL ICD for NVIDIA ****

**** Setting up EGL vendor file for NVIDIA ****

**** Fixing GBM library linkage ****

[custom-init] No custom files found, skipping...

[svc-de] Wayland mode: Waiting for socket at /config/.XDG/wayland-1...

[svc-de] /config/.XDG/wayland-1 found launching de

[ls.io-init] done.

No desktop processes found to terminate.

19

20

[Wayland] Initializing GL Renderer using device: /dev/dri/renderD128

[svc-de] Wayland mode: Waiting for socket at /config/.XDG/wayland-1...

[svc-de] /config/.XDG/wayland-1 found launching de

[Wayland] Warning: Failed to bind EGL to Wayland Display (Optional): EglExtensionNotSupported(["EGL_WL_bind_wayland_display"])

No desktop processes found to terminate.

[Wayland] GPU Initialization failed: Failed to allocate GBM buffer. Falling back to Software Renderer (Pixman).

[Wayland] Socket listening on: "wayland-1"

[svc-de] Wayland mode: Waiting for socket at /config/.XDG/wayland-1...

[svc-de] /config/.XDG/wayland-1 found launching de

Logs after opening WebUI

INFO:data_websocket:Legacy client ('127.0.0.1', 52384) connected. Role: controller, Slot: None

INFO:data_websocket:Data WebSocket connected from ('127.0.0.1', 52384)

INFO:data_websocket:Attempting to establish PulseAudio connection...

INFO:data_websocket:PulseAudio connection established.

INFO:data_websocket:Registering new client for display: primary

INFO:data_websocket:Applying and sanitizing client settings for 'primary' (initial=True)

INFO:data_websocket:DPI changed from None to 96. Applying system-level change.

INFO:data_websocket:Wayland Settings: Executing 'wlr-randr --output WL-1 --scale 1.0' on wayland-0

INFO:data_websocket:Initial setup or dimensional change detected for 'primary'. Performing full display reconfiguration.

INFO:data_websocket:Starting display reconfiguration...

INFO:data_websocket:Calculating new extended desktop layout from ALL clients...

INFO:data_websocket:Layout calculated: Total Size=1920x918. Layouts: {'primary': {'x': 0, 'y': 0, 'w': 1920, 'h': 918}}

INFO:data_websocket:Starting separate capture instances for each ACTIVE display region...

INFO:data_websocket:Client 'primary' is active. Starting its capture.

INFO:data_websocket:Preparing to start capture for display='primary': Res=1920x918, Offset=0x0

INFO:main:Parsed DRI node '/dev/dri/renderD128' to index 0.

INFO:data_websocket:Registered Wayland cursor callback for 'primary'

[Wayland] Configuring Output: 1920x918 @ 60.00 FPS (Scale 1.00)

INFO:data_websocket:Video chunk sender started for display 'primary'.

INFO:data_websocket:SUCCESS: Capture started for 'primary'.

INFO:data_websocket:Broadcasting primary stream resolution to all clients: {"type": "stream_resolution", "width": 1920, "height": 918}

INFO:data_websocket:Broadcasting display config update: DISPLAY_CONFIG_UPDATE,{"type": "display_config_update", "displays": ["primary"]}

INFO:data_websocket:Display reconfiguration finished successfully.

INFO:data_websocket:Reconfiguration process complete (state unlocked).

INFO:data_websocket:Initial client settings message processed by ws_handler.

INFO:data_websocket:Initial setup: Primary client connected, audio not active, attempting start.

[Wayland] Encode Node Index: 0 | Driver: ../../../../bus/pci/drivers/nvidia

[Wayland] Nvidia Encoder detected. Initializing NVENC...

[NVENC] Initializing...

INFO:data_websocket:Starting pcmflux audio pipeline...

INFO:data_websocket:pcmflux settings: device='output.monitor', bitrate=320000, channels=2

INFO:data_websocket:pcmflux audio capture started successfully.

[pcmflux] Attempting to connect to PulseAudio device: output.monitor with latency: 10ms

INFO:data_websocket:pcmflux audio chunk broadcasting task started.

INFO:data_websocket:Received redundant resize request for primary (1920x918). No action taken.

INFO:data_websocket:Received START_AUDIO command from client for server-to-client audio.

INFO:data_websocket:START_AUDIO: pcmflux audio pipeline already active.

[pcmflux] SUCCESS: Connected to PulseAudio.

[pcmflux] SUCCESS: Opus encoder created.

[pcmflux] Capture loop started. Device: output.monitor, Rate: 48000, Channels: 2, Bitrate: 320 kbps, VBR: On, Silence Gate: Off, Debug Logging: Off, PCM Chunk: 3840 bytes

[NVENC] Found 1 CUDA devices:

[NVENC] Device 0: NVIDIA GeForce RTX 2060 SUPER

[NVENC] Bound to CUDA device via PCI Bus ID: 0000:01:00.0

[Wayland] Failed to init NVENC: Failed to initialize encoder. Falling back to CPU.

[Wayland] Decision: No GPU Encoder available -> Using CPU Software Encoding.

Stream settings active -> Res: 1920x918 | FPS: 60.0 | Stripes: 1 | Mode: H264 (CPU) FullFrame | CRF: 25 | PaintOver CRF: 18 (Burst: 5f) | Colorspace: I420 (Limited Range) | Damage Thresh: 10f | Damage Dur: 20f

[pcmflux] First non-silent audio chunk detected! Encoding...

Also reinstalled the plugin itself (always with reboot inbetween).

  • Replies 5.9k
  • Views 1.1m
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • 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

  • Recompiled the drivers and they are now just working fine (to get it working scroll down):   Please do the following (this is only necessary if you upgraded before I recompiled the dri

  • I'm currently spinning up my build VM and compiling the drivers again, currently drivers for 6.11.0 stable are not available...

Posted Images

  • Author
7 minutes ago, AvoooCadoo said:

Also reinstalled the plugin itself (always with reboot inbetween).

Did you ever consider to remove the container including the appdata directory and starting over?

Seems there is nothing wrong and it should work as intended, can you maybe try another Browser too since I have already confirmation that the newly built driver works.

24 minutes ago, ich777 said:

Did you ever consider to remove the container including the appdata directory and starting over?

Seems there is nothing wrong and it should work as intended, can you maybe try another Browser too since I have already confirmation that the newly built driver works.

Did that multiple times. I also got the Intel IGPU plugin maybe that could interfere? Tried edge and firefox.

  • Author
13 minutes ago, AvoooCadoo said:

Did that multiple times. I also got the Intel IGPU plugin maybe that could interfere? Tried edge and firefox.

Maybe, I'm not the creator from the container but as you can see others already also had success with the new driver. I assume you are passing thourh D128 but your Nvidia GPU is D129 but as said before, for an Nvidia GPU you usually don't pass through a /dev/dri.

Did you also read my other post where I mentioned how I got it running? You only need --runtime=nvidia and --gpus=all

7 minutes ago, ich777 said:

Maybe, I'm not the creator from the container but as you can see others already also had success with the new driver. I assume you are passing thourh D128 but your Nvidia GPU is D129 but as said before, for an Nvidia GPU you usually don't pass through a /dev/dri.

Did you also read my other post where I mentioned how I got it running? You only need --runtime=nvidia and --gpus=all

yeah did a new container with only using the run command as yours:

  -d
  --name='orcaslicer'
  --net='bridge'
  --pids-limit 2048
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Capkinserver"
  -e HOST_CONTAINERNAME="orcaslicer"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='https://[IP]:[PORT:3001]'
  -l net.unraid.docker.icon=
  -p '3002:3000/tcp'
  -p '3001:3001/tcp'
  -v '/mnt/user/public/3D Druck/':'/3dfiles':'rw'
  -v '/mnt/user/appdata/orcaslicer':'/config':'rw'
  --runtime=nvidia
  --gpus=all 'lscr.io/linuxserver/orcaslicer'

293896f0896c6c02c800716a997b180f930883aa42cf50c8a9ae32c0f9a909bb

  • Author
9 hours ago, AvoooCadoo said:

yeah did a new container with only using the run command as yours:

And you deleted the directory in appdata for the container too?

I now have another confirmation that it works, don't know what causes that on your end.

3 hours ago, ich777 said:

And you deleted the directory in appdata for the container too?

I now have another confirmation that it works, don't know what causes that on your end.

Yes deleted. What else could i try? I deleted some orphaned images in advanced view too.

But i noticed when installing the container while pulling the images the first 5 or so lines stated already exists.

  • Author
4 minutes ago, AvoooCadoo said:

But i noticed when installing the container while pulling the images the first 5 or so lines stated already exists.

This is just normal because I assume you have other containers from Linuxserver.io installed and they share probably the base images with other containers that's why you see that.

In the GitHub issue is also mentioned that something on the Nvidia Toolkit side changed, maybe that's the cause of the issue in your case. The maintainer from the image said that he is looking into that and rebuilding the base images today.

I don't think that this is a driver issue anymore and more related to the Toolkit changes and the container.

I updated to open source 595 driver and none of my docker containers are launching that requires the 3090. How do i revert back to the 590 open source driver since I also have a 5060ti in the system

getting this error trying to startup:
Failed starting container: 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: unknown

edit: had to restore the last known good unraid flash backup to get open sourced 590 driver and my GPUs working again. Really not sure if it was the 595 driver update or something got corrupted. I had updated to the 595 driver, didnt reboot yet because I was hitting the 3090 with a lot of LLM requests and it seemingly froze the 3090. Upon rebooting, 595 was active and both the 3090 and 5060ti were detected but I kept getting the ldconfig errors when trying to load docker containers that used the GPUs

Edited by ranova

  • Author
10 hours ago, ranova said:

Failed starting container: 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: unknown

Do you have Diagnostics? Otherwise I'm not able to help.

What are your container startup parameters so to speak what is your docker run command?

I would like to confirm I am having the same issues as others expressed in the thread, some of my docker containers still work with the latest Nvidia open source drives like emby. But steam-headless and ollama refuse to start, stating the exact same logs like previously mentioned.

I will attempt to downgrade my driver's. Because this happened for me once I updated both steam-headless and ollama to their latest docker image. Emby has not had a recent update and I assume that's why it's still working.

And unfortunately I don't have a current backup of my docker images. 😞

9 hours ago, ich777 said:

Do you have Diagnostics? Otherwise I'm not able to help.

What are your container startup parameters so to speak what is your docker run command?

I have the same issue.

I was using the following command in Unraid terminal to check if the Nvidia driver was working...
```docker run --rm --gpus all nvidia/cuda:12.3.2-base-ubuntu22.04 nvidia-smi```

Output:
```docker run --rm --gpus all nvidia/cuda:12.3.2-base-ubuntu22.04 nvidia-smi

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```

  • Author
34 minutes ago, Mrtj18 said:

And unfortunately I don't have a current backup of my docker images. 😞

30 minutes ago, eyesfit said:

I have the same issue.

Please guys, you've all read the previous posts, where are your Diagnostics?

It is pretty useless to say I have the same issue when you post no diagnostics at all. I even don't know on which Unraid version you are nor do I know what exact driver you all on.

Do you all use --gpus all?
Please remove that variable and add the variables like mentioned in the second post.

2 hours ago, ich777 said:

Please guys, you've all read the previous posts, where are your Diagnostics?

It is pretty useless to say I have the same issue when you post no diagnostics at all. I even don't know on which Unraid version you are nor do I know what exact driver you all on.

Do you all use --gpus all?
Please remove that variable and add the variables like mentioned in the second post.

I can confirm after re-reading your posts and checking the docker container setup I had for ollama. I had the --gpus=all flag in the extra parameters section. Thus causing ollama not to start. As soon as I placed what you mentioned in the 2nd post of this thread. the --runtime=nvidia flag there, the docker started.

I also removed all --gpus=all flags from other containers I have. As well as placed the actual GPU-ID in the nvidia visable devices section as well. I had All listed there.

My steam-headless issue is an issue with the container itself. It does not like to play well with the latest nvidia drivers for some reason. I see other reports of users downgrading to 580.142 driver. I will just possibly wait on a new update to the container. Or try and find the previous docker image release name, because I didnt have the issue before upgrading.

So sorry, user error once again. lol

Hi,

I wanted to upgrade my system so I could use the models locally directly on my server. To do this, I installed an RTX 5070 TI. I followed a lot of the instructions I saw in this thread, such as uninstalling and reinstalling the NVIDIA driver. I even spoke with Perplexity, who said that my driver isn't loading

“The driver loads, but it fails when initializing the card because Unraid assigns it an invalid PCIe region (This PCI I/O region assigned to your NVIDIA device is invalid, probe ... failed with error -1).”


tower-diagnostics-20260422-1116.zip

Edited by Nono@Server

4 hours ago, Nono@Server said:

Hi,

I wanted to upgrade my system so I could use the models locally directly on my server. To do this, I installed an RTX 5070 TI. I followed a lot of the instructions I saw in this thread, such as uninstalling and reinstalling the NVIDIA driver. I even spoke with Perplexity, who said that my driver isn't loading

“The driver loads, but it fails when initializing the card because Unraid assigns it an invalid PCIe region (This PCI I/O region assigned to your NVIDIA device is invalid, probe ... failed with error -1).”


tower-diagnostics-20260422-1116.zip

you need to boot in UEFI mode, youre currently using legacy. Also check that Resizable BAR Support and Above 4G Decoding is enabled

26 minutes ago, Mainfrezzer said:

you need to boot in UEFI mode, youre currently using legacy. Also check that Resizable BAR Support and Above 4G Decoding is enabled

I tried booting into UEFI, but it just takes me straight back to the BIOS, and I don't know why. I don't think I had this problem before I replaced my motherboard at the same time as my graphics card.

Maybe I don't have UEFI on the Unraid USB drive.

5 minutes ago, Nono@Server said:

I tried booting into UEFI, but it just takes me straight back to the BIOS, and I don't know why. I don't think I had this problem before I replaced my motherboard at the same time as my graphics card.

Maybe I don't have UEFI on the Unraid USB drive.

You can either click this checkbox in the unraid webgui
image.png

or rename the EFI- folder to EFI

Im gonna assume now that the motherboard is set to boot uefi/bios at the same time

54 minutes ago, Mainfrezzer said:

You can either click this checkbox in the unraid webgui
image.png

or rename the EFI- folder to EFI

Im gonna assume now that the motherboard is set to boot uefi/bios at the same time

Thank you. After allowing the USB drive to boot in UEFI mode, the card is now detected properly.

For me this is driver version related, specifically since 595.58.03 so I assume it's an Nvidia problem not the driver plugin

I have Intel integrated GPU along with Nvidia RTX 4060

The 4060 is passed to a gaming VM when it's started and handed back to host when the VM stops so power management persists

by use of the following script in /etc/libvirt/hooks/qem

#!/bin/bash

if [ "$2" == "prepare" ]
then
killall nvidia-persistenced
elif [ "$2" == "release" ]
then
nvidia-persistenced

echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control

fi

exit 0 

This worked fine until updating the driver to 595.58.03. At which point I started seeing the following when shutting the VM down. My limited understanding, the host was trying to take back control of the audio part of the 4060 before the VM had released it

Apr 15 09:24:07 myunraid kernel: vfio-pci 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none
Apr 15 09:24:07 myunraid kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
Apr 15 09:24:07 myunraid kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Apr 15 09:24:10 myunraid kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 2
Apr 15 09:24:10 myunraid kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
Apr 15 09:24:10 myunraid kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
Apr 15 09:24:10 myunraid kernel: BUG: kernel NULL pointer dereference, address: 000000000000001c
Apr 15 09:24:10 myunraid kernel: #PF: supervisor read access in kernel mode
Apr 15 09:24:10 myunraid kernel: #PF: error_code(0x0000) - not-present page
Apr 15 09:24:10 myunraid kernel: PGD 0 P4D 0 
Apr 15 09:24:10 myunraid kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI
Apr 15 09:24:10 myunraid kernel: CPU: 7 UID: 0 PID: 2118002 Comm: qemu-event Tainted: P     U     O       6.12.54-Unraid #1
Apr 15 09:24:10 myunraid kernel: Tainted: P]=PROPRIETARY_MODULE, [U]=USER, [O]=OOT_MODULE
Apr 15 09:24:10 myunraid kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E13/MAG B760M MORTAR WIFI II (MS-7E13), BIOS 1.B0 03/04/2026
Apr 15 09:24:10 myunraid kernel: RIP: 0010:nv_audio_dynamic_power+0x8f/0x110 [nvidia]
Apr 15 09:24:10 myunraid 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 15 09:24:10 myunraid kernel: RSP: 0018:ffffc9000b126b98 EFLAGS: 00010207
Apr 15 09:24:10 myunraid kernel: RAX: ffff8881404d39a0 RBX: 0000000000000000 RCX: ffff888101570bb8
Apr 15 09:24:10 myunraid kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8881017fc100
Apr 15 09:24:10 myunraid kernel: RBP: ffff888161c85bf0 R08: ffff8881017fb000 R09: 00000000ffffffff
Apr 15 09:24:10 myunraid kernel: R10: 00000000ffffffff R11: ffffffffa65b06a8 R12: ffff888161c85c50
Apr 15 09:24:10 myunraid kernel: R13: ffffffffa17c3dc0 R14: ffff888345c36820 R15: ffff888161c85d50
Apr 15 09:24:10 myunraid kernel: FS:  0000152e70eff6c0(0000) GS:ffff88885f5c0000(0000) knlGS:0000000000000000 ......... 

To remedy this I changed the hooks script to

#!/bin/bash
if [ "$2" == "prepare" ]; then
    killall nvidia-persistenced 2>/dev/null
elif [ "$2" == "release" ]; then
    nvidia-persistenced
fi
exit 0

and created /boot/config/modprobe.d/nvidia.conf containing "options nvidia NVreg DynamicPowerManagement=0x00" without ""

And appended boot option in SysLinux Configuration "nvidia_drm.fbdev=0" without ""

This worked fine when the VM was shutdown. However, when I attempt to stop all containers binhex-krusader (I think) was somehow holding onto the 4060 as below:

Apr 22 17:00:28 myunraid kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 2
Apr 22 17:00:28 myunraid nvidia-persistenced: Started (37875)
Apr 22 17:01:06 myunraid kernel: docker0: port 4(vethdb03243) entered disabled state
Apr 22 17:01:06 myunraid kernel: veth88185cb: renamed from eth0
Apr 22 17:01:07 myunraid kernel: docker0: port 4(vethdb03243) entered disabled state
Apr 22 17:01:07 myunraid kernel: vethdb03243 (unregistering): left allmulticast mode
Apr 22 17:01:07 myunraid kernel: vethdb03243 (unregistering): left promiscuous mode
Apr 22 17:01:07 myunraid kernel: docker0: port 4(vethdb03243) entered disabled state
Apr 22 17:01:07 myunraid kernel: docker0: port 1(veth200eb14) entered disabled state
Apr 22 17:01:07 myunraid kernel: vethb8b2976: renamed from eth0
Apr 22 17:01:07 myunraid kernel: docker0: port 1(veth200eb14) entered disabled state
Apr 22 17:01:07 myunraid kernel: veth200eb14 (unregistering): left allmulticast mode
Apr 22 17:01:07 myunraid kernel: veth200eb14 (unregistering): left promiscuous mode
Apr 22 17:01:07 myunraid kernel: docker0: port 1(veth200eb14) entered disabled state
Apr 22 17:01:09 myunraid kernel: veth9c6c9dd: renamed from eth0
Apr 22 17:01:09 myunraid kernel: docker0: port 3(vethcdc26e9) entered disabled state
Apr 22 17:01:09 myunraid kernel: veth3146c42: renamed from eth0
Apr 22 17:01:09 myunraid kernel: docker0: port 3(vethcdc26e9) entered disabled state
Apr 22 17:01:09 myunraid kernel: vethcdc26e9 (unregistering): left allmulticast mode
Apr 22 17:01:09 myunraid kernel: vethcdc26e9 (unregistering): left promiscuous mode
Apr 22 17:01:09 myunraid kernel: docker0: port 3(vethcdc26e9) entered disabled state
Apr 22 17:01:10 myunraid kernel: br-ba13ce51d72c: port 4(vethadd7090) entered disabled state
Apr 22 17:01:10 myunraid kernel: veth899b005: renamed from eth0
Apr 22 17:01:10 myunraid kernel: br-ba13ce51d72c: port 4(vethadd7090) entered disabled state
Apr 22 17:01:10 myunraid kernel: vethadd7090 (unregistering): left allmulticast mode
Apr 22 17:01:10 myunraid kernel: vethadd7090 (unregistering): left promiscuous mode
Apr 22 17:01:10 myunraid kernel: br-ba13ce51d72c: port 4(vethadd7090) entered disabled state
Apr 22 17:01:10 myunraid kernel: br-ba13ce51d72c: port 3(veth09f6b7d) entered disabled state
Apr 22 17:01:10 myunraid kernel: veth8511e99: renamed from eth0
Apr 22 17:01:10 myunraid kernel: br-ba13ce51d72c: port 3(veth09f6b7d) entered disabled state
Apr 22 17:01:10 myunraid kernel: veth09f6b7d (unregistering): left allmulticast mode
Apr 22 17:01:10 myunraid kernel: veth09f6b7d (unregistering): left promiscuous mode
Apr 22 17:01:10 myunraid kernel: br-ba13ce51d72c: port 3(veth09f6b7d) entered disabled state
Apr 22 17:01:11 myunraid kernel: br-ba13ce51d72c: port 2(vethc9c0771) entered disabled state
Apr 22 17:01:11 myunraid kernel: vetha24d22e: renamed from eth0
Apr 22 17:01:11 myunraid kernel: br-ba13ce51d72c: port 2(vethc9c0771) entered disabled state
Apr 22 17:01:11 myunraid kernel: vethc9c0771 (unregistering): left allmulticast mode
Apr 22 17:01:11 myunraid kernel: vethc9c0771 (unregistering): left promiscuous mode
Apr 22 17:01:11 myunraid kernel: br-ba13ce51d72c: port 2(vethc9c0771) entered disabled state
Apr 22 17:01:11 myunraid kernel: br-ba13ce51d72c: port 1(veth7559afd) entered disabled state
Apr 22 17:01:11 myunraid kernel: vethe345a06: renamed from eth0
Apr 22 17:01:11 myunraid kernel: br-ba13ce51d72c: port 1(veth7559afd) entered disabled state
Apr 22 17:01:11 myunraid kernel: veth7559afd (unregistering): left allmulticast mode
Apr 22 17:01:11 myunraid kernel: veth7559afd (unregistering): left promiscuous mode
Apr 22 17:01:11 myunraid kernel: br-ba13ce51d72c: port 1(veth7559afd) entered disabled state
Apr 22 17:01:11 myunraid kernel: Oops: general protection fault, probably for non-canonical address 0x7369645f766564b6: 0000 [#1] PREEMPT SMP NOPTI
Apr 22 17:01:11 myunraid kernel: CPU: 6 UID: 99 PID: 24821 Comm: Xvnc Tainted: P     U     O       6.12.54-Unraid #1
Apr 22 17:01:11 myunraid kernel: Tainted: [P]=PROPRIETARY_MODULE, [U]=USER, [O]=OOT_MODULE
Apr 22 17:01:11 myunraid kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E13/MAG B760M MORTAR WIFI II (MS-7E13), BIOS 1.B0 03/04/2026
Apr 22 17:01:11 myunraid kernel: RIP: 0010:_nv000022kms+0xaa/0xbb0 [nvidia_modeset]
Apr 22 17:01:11 myunraid kernel: Code: 00 83 c1 01 48 05 78 0e 00 00 83 f9 04 75 bc be 01 00 00 00 bf 40 52 00 00 e8 32 02 f9 ff 49 89 c5 48 85 c0 0f 84 9e 05 00 00 <41> 8b 47 40 49 8d b5 20 0c 00 00 31 d2 45 31 f6 48 89 75 a8 41 89
Apr 22 17:01:11 myunraid kernel: RSP: 0000:ffffc90021f97960 EFLAGS: 00010282
Apr 22 17:01:11 myunraid kernel: RAX: ffffc90000c56008 RBX: ffff8881c6bdc000 RCX: 0000000000000000
Apr 22 17:01:11 myunraid kernel: RDX: 0000000000005248 RSI: 0000000000000000 RDI: ffffc90000c5b248
Apr 22 17:01:11 myunraid kernel: RBP: ffffc90021f979d0 R08: 000000000000000c R09: ffffc90000c56000
Apr 22 17:01:11 myunraid kernel: R10: 0000000000000006 R11: ffff888197974070 R12: ffffffffa06d7a80
Apr 22 17:01:11 myunraid kernel: R13: ffffc90000c56008 R14: 0000000000000000 R15: 7369645f76656476
Apr 22 17:01:11 myunraid kernel: FS:  0000000000000000(0000) GS:ffff88885f580000(0000) knlGS:0000000000000000
Apr 22 17:01:11 myunraid kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 22 17:01:11 myunraid kernel: CR2: 00001474ae97e6b0 CR3: 0000000005618002 CR4: 0000000000772ef0
Apr 22 17:01:11 myunraid kernel: PKRU: 55555554
Apr 22 17:01:11 myunraid kernel: Call Trace:
Apr 22 17:01:11 myunraid kernel: <TASK>
Apr 22 17:01:11 myunraid kernel: ? prep_new_page+0x32/0x50
Apr 22 17:01:11 myunraid kernel: ? get_page_from_freelist+0x803/0x950
Apr 22 17:01:11 myunraid kernel: ? nv_drm_atomic_apply_modeset_config+0x41a/0x570 [nvidia_drm]
Apr 22 17:01:11 myunraid kernel: ? drm_atomic_check_only+0x6f3/0x820 [drm]
Apr 22 17:01:11 myunraid kernel: ? nv_drm_atomic_state_alloc+0x1b/0x60 [nvidia_drm]
Apr 22 17:01:11 myunraid kernel: ? lruvec_stat_mod_folio.constprop.0+0x10/0x20
Apr 22 17:01:11 myunraid kernel: ? drm_atomic_commit+0x6b/0xd0 [drm]
Apr 22 17:01:11 myunraid kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Apr 22 17:01:11 myunraid kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm]
Apr 22 17:01:11 myunraid kernel: ? nv_drm_revoke_modeset_permission+0x1a0/0x220 [nvidia_drm]
Apr 22 17:01:11 myunraid kernel: ? kmem_cache_free_bulk+0x197/0x1f0
Apr 22 17:01:11 myunraid kernel: ? nv_drm_master_drop+0x2f/0x1c0 [nvidia_drm]
Apr 22 17:01:11 myunraid kernel: ? __pfx_drm_gem_object_release_handle+0x10/0x10 [drm]
Apr 22 17:01:11 myunraid kernel: ? drm_drop_master+0x18/0x30 [drm]
Apr 22 17:01:11 myunraid kernel: ? drm_master_release+0x57/0xa0 [drm]
Apr 22 17:01:11 myunraid kernel: ? drm_file_free+0x182/0x1e0 [drm]
Apr 22 17:01:11 myunraid kernel: ? drm_release+0x5c/0xa0 [drm]
Apr 22 17:01:11 myunraid kernel: ? __fput+0x10a/0x1d0
Apr 22 17:01:11 myunraid kernel: ? task_work_run+0x68/0x80
Apr 22 17:01:11 myunraid kernel: ? do_exit+0x36f/0x8d0
Apr 22 17:01:11 myunraid kernel: ? mtree_range_walk+0xf3/0x170
Apr 22 17:01:11 myunraid kernel: ? do_group_exit+0x79/0x80
Apr 22 17:01:11 myunraid kernel: ? get_signal+0x617/0x660
Apr 22 17:01:11 myunraid kernel: ? arch_do_signal_or_restart+0x28/0x1d0
Apr 22 17:01:11 myunraid kernel: ? fatal_signal_pending+0x9/0x30
Apr 22 17:01:11 myunraid kernel: ? fault_signal_pending+0x1b/0x60
Apr 22 17:01:11 myunraid kernel: ? do_user_addr_fault+0x2c0/0x490
Apr 22 17:01:11 myunraid kernel: ? irqentry_exit_to_user_mode+0x49/0x80
Apr 22 17:01:11 myunraid kernel: ? asm_exc_page_fault+0x22/0x30
Apr 22 17:01:11 myunraid kernel: </TASK>
Apr 22 17:01:11 myunraid kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 vhost_net tun vhost vhost_iotlb tap ipvlan br_netfilter nf_conntrack_netlink xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nvidia_uvm(PO) af_packet nfnetlink dm_crypt dm_mod md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag i915(O) intel_gtt iptable_mangle xt_addrtype iptable_raw xt_comment xt_connmark nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_mark ip6table_mangle ip6table_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc atlantic r8125(O) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl intel_cstate mei_pxp mei_hdcp iwlmvm nvidia_drm(PO)
Apr 22 17:01:11 myunraid kernel: nvidia_modeset(PO) xe mac80211 btusb btrtl drm_gpuvm btbcm libarc4 btintel drm_exec nvidia(PO) iwlwifi gpu_sched drm_buddy bluetooth i2c_algo_bit drm_suballoc_helper drm_display_helper drm_ttm_helper ttm sr_mod input_leds drm_kms_helper ecdh_generic cdrom cfg80211 led_class ecc joydev drm intel_uncore wmi_bmof mxm_wmi i2c_i801 mei_me i2c_smbus mei rfkill agpgart i2c_core thermal fan video wmi backlight acpi_tad acpi_pad button [last unloaded: atlantic]
Apr 22 17:01:11 myunraid kernel: ---[ end trace 0000000000000000 ]---
Apr 22 17:01:11 myunraid kernel: pstore: backend (efi_pstore) writing error (-28)
Apr 22 17:01:11 myunraid kernel: RIP: 0010:_nv000022kms+0xaa/0xbb0 [nvidia_modeset]
Apr 22 17:01:11 myunraid kernel: Code: 00 83 c1 01 48 05 78 0e 00 00 83 f9 04 75 bc be 01 00 00 00 bf 40 52 00 00 e8 32 02 f9 ff 49 89 c5 48 85 c0 0f 84 9e 05 00 00 <41> 8b 47 40 49 8d b5 20 0c 00 00 31 d2 45 31 f6 48 89 75 a8 41 89
Apr 22 17:01:11 myunraid kernel: RSP: 0000:ffffc90021f97960 EFLAGS: 00010282
Apr 22 17:01:11 myunraid kernel: RAX: ffffc90000c56008 RBX: ffff8881c6bdc000 RCX: 0000000000000000
Apr 22 17:01:11 myunraid kernel: RDX: 0000000000005248 RSI: 0000000000000000 RDI: ffffc90000c5b248
Apr 22 17:01:11 myunraid kernel: RBP: ffffc90021f979d0 R08: 000000000000000c R09: ffffc90000c56000
Apr 22 17:01:11 myunraid kernel: R10: 0000000000000006 R11: ffff888197974070 R12: ffffffffa06d7a80
Apr 22 17:01:11 myunraid kernel: R13: ffffc90000c56008 R14: 0000000000000000 R15: 7369645f76656476
Apr 22 17:01:11 myunraid kernel: FS:  0000000000000000(0000) GS:ffff88885f580000(0000) knlGS:0000000000000000
Apr 22 17:01:11 myunraid kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 22 17:01:11 myunraid kernel: CR2: 00001474ae97e6b0 CR3: 00000002aaf52006 CR4: 0000000000772ef0
Apr 22 17:01:11 myunraid kernel: PKRU: 55555554
Apr 22 17:01:11 myunraid kernel: Fixing recursive fault but reboot is needed!
Apr 22 17:01:11 myunraid kernel: BUG: using smp_processor_id() in preemptible [00000000] code: Xvnc/24821
Apr 22 17:01:11 myunraid kernel: caller is __schedule+0x2d/0x760
Apr 22 17:01:11 myunraid kernel: CPU: 6 UID: 99 PID: 24821 Comm: Xvnc Tainted: P     UD    O       6.12.54-Unraid #1
Apr 22 17:01:11 myunraid kernel: Tainted: [P]=PROPRIETARY_MODULE, [U]=USER, [D]=DIE, [O]=OOT_MODULE
Apr 22 17:01:11 myunraid kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E13/MAG B760M MORTAR WIFI II (MS-7E13), BIOS 1.B0 03/04/2026
Apr 22 17:01:11 myunraid kernel: Call Trace:
Apr 22 17:01:11 myunraid kernel: <TASK>
Apr 22 17:01:11 myunraid kernel: dump_stack_lvl+0x47/0x70
Apr 22 17:01:11 myunraid kernel: check_preemption_disabled+0xb7/0xd0
Apr 22 17:01:11 myunraid kernel: __schedule+0x2d/0x760
Apr 22 17:01:11 myunraid kernel: ? _printk+0x58/0x80
Apr 22 17:01:11 myunraid kernel: do_task_dead+0x3e/0x40
Apr 22 17:01:11 myunraid kernel: make_task_dead+0xfc/0x110
Apr 22 17:01:11 myunraid kernel: rewind_stack_and_make_dead+0x16/0x20
Apr 22 17:01:11 myunraid kernel: RIP: 0033:0x1474aefff6c0
Apr 22 17:01:11 myunraid kernel: Code: Unable to access opcode bytes at 0x1474aefff696.
Apr 22 17:01:11 myunraid kernel: RSP: 002b:00007ffcd73ac978 EFLAGS: 00010246
Apr 22 17:01:11 myunraid kernel: RAX: 00001474aefff6c0 RBX: 00001474b9f08fa8 RCX: 0000000000000001
Apr 22 17:01:11 myunraid kernel: RDX: 0000000000000003 RSI: 0000000000000000 RDI: 00001474b635dc00
Apr 22 17:01:11 myunraid kernel: RBP: 00007ffcd73ac9d0 R08: 00001474b635dc00 R09: 0000000000000007
Apr 22 17:01:11 myunraid kernel: R10: 000055dac13cbf80 R11: 1556005f37d461e2 R12: 000000000000096c
Apr 22 17:01:11 myunraid kernel: R13: 0000000000000000 R14: 00001474b9f07680 R15: 000055dac13c83f0
Apr 22 17:01:11 myunraid kernel: </TASK>
Apr 22 17:01:11 myunraid kernel: BUG: scheduling while atomic: Xvnc/24821/0x00000000
Apr 22 17:01:11 myunraid kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 vhost_net tun vhost vhost_iotlb tap ipvlan br_netfilter nf_conntrack_netlink xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE xfrm_user xfrm_algo ip6table_nat iptable_nat nf_nat nvidia_uvm(PO) af_packet nfnetlink dm_crypt dm_mod md_mod zfs(PO) spl(O) ntfs3 tcp_diag inet_diag i915(O) intel_gtt iptable_mangle xt_addrtype iptable_raw xt_comment xt_connmark nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_mark ip6table_mangle ip6table_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc atlantic r8125(O) intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl intel_cstate mei_pxp mei_hdcp iwlmvm nvidia_drm(PO)
Apr 22 17:01:11 myunraid kernel: nvidia_modeset(PO) xe mac80211 btusb btrtl drm_gpuvm btbcm libarc4 btintel drm_exec nvidia(PO) iwlwifi gpu_sched drm_buddy bluetooth i2c_algo_bit drm_suballoc_helper drm_display_helper drm_ttm_helper ttm sr_mod input_leds drm_kms_helper ecdh_generic cdrom cfg80211 led_class ecc joydev drm intel_uncore wmi_bmof mxm_wmi i2c_i801 mei_me i2c_smbus mei rfkill agpgart i2c_core thermal fan video wmi backlight acpi_tad acpi_pad button [last unloaded: atlantic]
Apr 22 17:01:11 myunraid kernel: Preemption disabled at:
Apr 22 17:01:11 myunraid kernel: [<0000000000000000>] 0x0
Apr 22 17:01:11 myunraid kernel: CPU: 6 UID: 99 PID: 24821 Comm: Xvnc Tainted: P     UD    O       6.12.54-Unraid #1
Apr 22 17:01:11 myunraid kernel: Tainted: [P]=PROPRIETARY_MODULE, [U]=USER, [D]=DIE, [O]=OOT_MODULE
Apr 22 17:01:11 myunraid kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E13/MAG B760M MORTAR WIFI II (MS-7E13), BIOS 1.B0 03/04/2026
Apr 22 17:01:11 myunraid kernel: Call Trace:
Apr 22 17:01:11 myunraid kernel: <TASK>
Apr 22 17:01:11 myunraid kernel: dump_stack_lvl+0x47/0x70
Apr 22 17:01:11 myunraid kernel: __schedule_bug+0x85/0xa0
Apr 22 17:01:11 myunraid kernel: __schedule+0x63/0x760
Apr 22 17:01:11 myunraid kernel: ? _printk+0x58/0x80
Apr 22 17:01:11 myunraid kernel: do_task_dead+0x3e/0x40
Apr 22 17:01:11 myunraid kernel: make_task_dead+0xfc/0x110
Apr 22 17:01:11 myunraid kernel: rewind_stack_and_make_dead+0x16/0x20
Apr 22 17:01:11 myunraid kernel: RIP: 0033:0x1474aefff6c0
Apr 22 17:01:11 myunraid kernel: Code: Unable to access opcode bytes at 0x1474aefff696.
Apr 22 17:01:11 myunraid kernel: RSP: 002b:00007ffcd73ac978 EFLAGS: 00010246
Apr 22 17:01:11 myunraid kernel: RAX: 00001474aefff6c0 RBX: 00001474b9f08fa8 RCX: 0000000000000001
Apr 22 17:01:11 myunraid kernel: RDX: 0000000000000003 RSI: 0000000000000000 RDI: 00001474b635dc00
Apr 22 17:01:11 myunraid kernel: RBP: 00007ffcd73ac9d0 R08: 00001474b635dc00 R09: 0000000000000007
Apr 22 17:01:11 myunraid kernel: R10: 000055dac13cbf80 R11: 1556005f37d461e2 R12: 000000000000096c
Apr 22 17:01:11 myunraid kernel: R13: 0000000000000000 R14: 00001474b9f07680 R15: 000055dac13c83f0
Apr 22 17:01:11 myunraid kernel: </TASK>

Rolled the driver back to 590.48.01 and all is well in my world again

I've attached diagnostics taken with each driver installed

myunraid-diagnostics-20260422-1702-Nvidia595.58.03.zip myunraid-diagnostics-20260422-1647-Nvidia590.48.01 .zip

Edited by fka

On 4/21/2026 at 8:39 AM, ich777 said:

Please guys, you've all read the previous posts, where are your Diagnostics?

It is pretty useless to say I have the same issue when you post no diagnostics at all. I even don't know on which Unraid version you are nor do I know what exact driver you all on.

Do you all use --gpus all?
Please remove that variable and add the variables like mentioned in the second post.

Thank you for your work and that information, I guess I was using some legacy nvidia docker commands:


services:

llama-swap:

image: ghcr.io/mostlygeek/llama-swap:cuda13

container_name: llama-swap-cuda

restart: unless-stopped

ports:

- "8887:8080"

volumes:

- /mnt/user/AI/models:/models

environment:

- NVIDIA_VISIBLE_DEVICES=all

- NVIDIA_DRIVER_CAPABILITIES=all

- LD_LIBRARY_PATH=/custom-bin/bin:/usr/local/cuda/lib64:/usr/lib/x86_64-linux-gnu

- GGML_CUDA_FORCE_FA3=1

- GGML_CUDA_GRAPH_OPT=1

deploy:

resources:

reservations:

devices:

- driver: nvidia

count: all

capabilities: [gpu]

entrypoint: ["/app/llama-swap"]

command: ["--config", "/app/config.yaml", "--listen", "0.0.0.0:8080"]

Updated it to the following and its now working again:

version: "3.8"

services:

llama-swap:

image: ghcr.io/mostlygeek/llama-swap:cuda13

container_name: llama-swap-cuda

restart: unless-stopped

runtime: nvidia

ports:

- "8887:8080"

volumes:

- /mnt/samsungevo/AI/models:/models

environment:

- NVIDIA_VISIBLE_DEVICES=GPU-xxx-xxx-xxx-xxxx-xxxx,GPU-xxx-xxx-xxx-xxxx-xxxx

- NVIDIA_DRIVER_CAPABILITIES=all

- LD_LIBRARY_PATH=/custom-bin/bin:/custom-bin-turbo/bin:/usr/local/nvidia/lib:/usr/local/nvidia/lib64:/usr/local/cuda/lib64:/usr/lib/x86_64-linux-gnu

- GGML_CUDA_FORCE_FA3=1

- GGML_CUDA_GRAPH_OPT=1

entrypoint: ["/app/llama-swap"]

command: ["--config", "/app/config.yaml", "--listen", "0.0.0.0:8080"]

I just updated to RC v7.3 and I ran into what looks like a similar issue @ich777 found here https://github.com/NVIDIA/nvidia-container-toolkit/issues/1385#issuecomment-3497279007

All my GPU containers with --gpus=all were failing before startup with errors like:

error running prestart hook #0: exit status 1
Auto-detected mode as 'legacy'
nvidia-container-cli: ldcache error: process /sbin/ldconfig failed with error code: 1

With toolkit debug enabled, the specific error was:

could not start /sbin/ldconfig: process confinement failed: invalid argument

In my case, a fix was to add:

[nvidia-container-cli]
no-pivot = true

to /etc/nvidia-container-runtime/config.toml, then restart Docker.

Specifically: no-pivot = true needed to be under [nvidia-container-cli] .

After that and restarting docker, my GPU containers appear to be working again (until reboot since that's not persisted)

For context, I had originally hit this after updating to RV 7.3, then even after rolling Unraid back and changing driver versions the issue was still there until I applied the no-pivot fix. Originally posted here: https://discord.com/channels/216281096667529216/1440856243156680757/1496671614107127879

Versions:

Driver: 595.58.03 (Also tried 590)

nvidia-container-cli: 1.19.0~1.19.0

nvidia-container-runtime: 1.19.0

EDIT: It seems this is the related commit
https://github.com/unraid/nvidia-container-toolkit/commit/5085b229cfc356d01eca4823feb6dae7e9afbf49

I believe no-pivot = true should be under [nvidia-container-cli] not [nvidia-container-runtime]?

Looking at @zoggy 's docs post it seems:

--gpus all alone on Docker → Docker directly triggers the hook path → that is the legacy-compatible path. There was a bug in the config for this path, but it works after fixing no-pivot = true

--gpus all --runtime=nvidia → Docker explicitly uses the NVIDIA runtime, which is NVIDIA’s recommended Docker invocation. Avoids the bug above

gilfoyle-diagnostics-20260422_1709.zip

Edited by pureelectricity
Found the GH Commit with the issue & updated with zoggy reference

--gpus came with docker 19.03, and a lot of improvements with --gpus came with docker29 ( https://docs.docker.com/engine/release-notes/29/ )

https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/docker-specialized.html

so why would someone not want to use --gpus today and instead the legacy --runtime ?

browsing i found

https://gitlab.com/nvidia/container-toolkit/container-toolkit/-/tree/main/cmd/nvidia-container-runtime#notes-on-using-the-docker-cli

image.png

Edited by zoggy

EDIT: Adding runtime: nvidia into the compose file appears to have fixed the issue. Previously, it wasn't required when using the deploy: notation. I'm not sure what changed, but adding the runtime back fixed the issue. I'm leaving this here in case it helps someone else out.

After upgrading beyond 7.2.5-rc1, I am unable to start containers using my Nvidia GTX 970. The newer kernel versions do not appear to have a working - at least for the GTX 970 - 580 series driver. 580.125 is the last driver version that worked for me. Diagnostics are attached and additional information is below. Any help would be appreciated.

Nvidia Info:

Nvidia Driver Version: 580.142
Open Source Kernel Module: No
Installed GPU(s):
0:
NVIDIA GeForce GTX 970
0C:00.0
GPU-f2b9c44f-accf-5c81-4303-1f1c97c38b39

GPU Driver Support:

0: NVIDIA GeForce GTX 970
Detected via: nvidia-smi
Chip codename: GM204
Architecture: Maxwell
Kernel module support: proprietary-only
Device ID input: 0x13C210DE
Normalized ID: 13c2
Supported candidates: 580.142
Recommended Driver: 580.142 (best-available)

nvidia-smi Output:

Thu Apr 23 22:21:09 2026
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 580.142                Driver Version: 580.142        CUDA Version: 13.0     |
+-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce GTX 970         On  |   00000000:0C:00.0 Off |                  N/A |
| 47%   39C    P8             13W /  250W |       2MiB /   4096MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------+

Error when starting via docker compose:

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

Example Docker Compose Service:

services:
  plex:
    container_name: plex
    image: ghcr.io/hotio/plex
    restart: always
    network_mode: host
    tmpfs:
      - /transcode
    volumes:
      - $DATADIR/plex:/config
      - $MEDIADIR/media:/data
    environment:
      - TZ=$TZ
      - UMASK=002
      - PLEX_BETA_INSTALL=true
      - PLEX_CLAIM_TOKEN=************
      - PLEX_ADVERTISE_URL=**************
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              capabilities:
                - gpu
              count: all
    healthcheck:
      test: curl --connect-timeout 15 --max-time 100 --silent --show-error --fail
        "http://$IP_ADDRESS:32400/identity" >/dev/null
      interval: 15s
      timeout: 5s
      retries: 5
      start_period: 60s
    labels:
      net.unraid.docker.icon: https://raw.githubusercontent.com/walkxcode/dashboard-icons/master/png/plex.png
      net.unraid.docker.webui: http://$IP_ADDRESS:32400/web

dragon-diagnostics-20260423-2201.zip

Edited by mrvnsk9

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.