12 hours ago, djtodd said:

Are you 100% sure that there is no space at the beginning, it looks like there is one space there:

1 minute ago, ich777 said:

I don't think that Unraid is the culprit here since I just tested it and with Jellyfin everything is working as expected.

So you rebuilt the

3 hours ago, ich777 said:

Are you 100% sure that there is no space at the beginning, it looks like there is one space there:

Yeah, not a space. Looks like one! Had my hopes up for a minute that I pulled a classic IT fat finger.

12 hours ago, anthony0030 said:

@djtodd I see that transcoding that h264 file is not working on your GTX 1050. Possibly that file format is not supported on your GPU. Take a look at the compatibility list here https://developer.nvidia.com/video-encode-decode-support-matrix

Your GPU can’t do all the versions. Try playing something else maby?

Nah, all of this stuff was working fine before. It's OK. I'm using this as a learning experience and I'm going to delve into Intel hardware. Lots to play with there with power savings and other things to fiddle with.

It's not a crisis, its an opportunity to learn!

Hi,

I updated my PR for this Repo. So that its mergable again.

Contains an automatic build pipeline and new UI/UX design.

(only dark because of my browser settings. for you it's probably not dark ;-))

PR: https://github.com/unraid/unraid-nvidia-driver/pull/7

best regards

Edited April 5Apr 5 by Valtos

I have started a second Unraid server and installed a Nvidia GTX 970 in it. I am getting an error nvidia-smi not able to communicate. I have tried several of the troubleshooting ideas that are listed in this topic. Anybody have any ideas. I have tried moving the driver versions, uninstalled and reinstalled the plugin. This is in a Dell T320. I also have a Dell 720 with a GTX 1080. In the Dell 720 the plugin does not recognize the integrated video card but in the T320 it does.

8 minutes ago, Valtos said:

I updated my PR for this Repo. So that its mergable again.

@SimonF would you mind taking a look at that since this would revert pretty much everything from your PR.

@Valtos depending on what @SimonF says, does the PR or better speaking also take into consideration that a user has multiple GPUs installed in his system?

If so is there an index displayed? I would also like to turn the logic around for the driver so all drivers are OpenSource except for the legacy 580.x driver version, so to speak OpenSource goes away and it says Legacy there.

6 minutes ago, Dax said:

I have started a second Unraid server and installed a Nvidia GTX 970 in it. I am getting an error nvidia-smi not able to communicate. I have tried several of the troubleshooting ideas that are listed in this topic. Anybody have any ideas. I have tried moving the driver versions, uninstalled and reinstalled the plugin. This is in a Dell T320. I also have a Dell 720 with a GTX 1080. In the Dell 720 the plugin does not recognize the integrated video card but in the T320 it does.

Please always post your Diagnostics, without them troubleshooting is impossible.

13 minutes ago, Dax said:

I have started a second Unraid server and installed a Nvidia GTX 970 in it. I am getting an error nvidia-smi not able to communicate. I have tried several of the troubleshooting ideas that are listed in this topic. Anybody have any ideas. I have tried moving the driver versions, uninstalled and reinstalled the plugin. This is in a Dell T320. I also have a Dell 720 with a GTX 1080. In the Dell 720 the plugin does not recognize the integrated video card but in the T320 it does.

6 minutes ago, ich777 said:

Please always post your Diagnostics, without them troubleshooting is impossible.

Sorry I was wondering about that after I saw several other posts.

memoryalpha-diagnostics-20260405-1533.zip

6 minutes ago, Dax said:

Sorry I was wondering about that after I saw several other posts.

Please do the following from a Unraid Terminal:

echo "blacklist nouveau" > /boot/config/modprobe.d/nouveau.conf

after that reboot (you will get no output from the command).

This is caused because the card is bound to the nouveau instead to the nvidia driver as you can see here:

0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)

Subsystem: EVGA Corporation Device [3842:3975]

Kernel driver in use: nouveau

Kernel modules: nouveau, nvidia_drm, nvidia

6 minutes ago, ich777 said:

Please do the following from a Unraid Terminal:

echo "blacklist nouveau" > /boot/config/modprobe.d/nouveau.conf

after that reboot (you will get no output from the command).

This is caused because the card is bound to the nouveau instead to the nvidia driver as you can see here:

0a:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1)

Subsystem: EVGA Corporation Device [3842:3975]

Kernel driver in use: nouveau

Kernel modules: nouveau, nvidia_drm, nvidia

Thank you very much that did it.

1 hour ago, ich777 said:

@Valtos depending on what @SimonF says, does the PR or better speaking also take into consideration that a user has multiple GPUs installed in his system?

If so is there an index displayed? I would also like to turn the logic around for the driver so all drivers are OpenSource except for the legacy 580.x driver version, so to speak OpenSource goes away and it says Legacy there.

Done. The PR now handles multiple GPUs. Each GPU is listed in the System Info card with an expandable detail panel showing chip codename, architecture, device ID, kernel module support, and recommended driver (from gpu-support.php).

The module support is computed across all installed GPUs:

- If all GPUs support open-source -> auto-selected, no dropdown

- If all GPUs need proprietary (pre-Turing) -> auto-selected as "Legacy"

- If mixed (e.g. Turing + Blackwell) -> open-source (the common denominator)

- If conflicting (e.g. Volta + Blackwell) -> error banner, download disabled

Labels have been renamed: "Proprietary" -> "Legacy (Proprietary)" open-source is now the default. The module type dropdown is hidden entirely when only one option is valid.

best regards

16 hours ago, ich777 said:

@SimonF would you mind taking a look at that since this would revert pretty much everything from your PR.

@Valtos depending on what @SimonF says, does the PR or better speaking also take into consideration that a user has multiple GPUs installed in his system?

If so is there an index displayed? I would also like to turn the logic around for the driver so all drivers are OpenSource except for the legacy 580.x driver version, so to speak OpenSource goes away and it says Legacy there.

Will try and look into this week but maybe next.

Has anyone been able to get Wayland working with Nvidia?

I've been trying to configure a few of the gaming related containers from linuxserver. I've followed the docs and added required values (nvidia-drm.modeset=1 nvidia_drm.fbdev=1), env, etc

Example: https://github.com/linuxserver/docker-melonds?tab=readme-ov-file#nvidia-proprietary-drivers

I've seen a few posts regarding this and unraid (https://github.com/linuxserver/docker-webstation/issues/3)

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

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

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

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

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

[NVENC] Initializing...

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

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

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.

INFO:data_websocket:Starting pcmflux audio pipeline...

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

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

INFO:data_websocket:pcmflux audio capture started successfully.

[NVENC] Found 1 CUDA devices:

[NVENC] Device 0: NVIDIA GeForce RTX 5060 Ti

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

INFO:data_websocket:pcmflux audio chunk broadcasting task started.

[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

INFO:data_websocket:Received redundant resize request for primary (3440x1270). 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] First non-silent audio chunk detected! Encoding...

[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: 3440x1270 | 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

INFO:data_websocket:Received STOP_VIDEO for 'primary'. Stopping stream.

INFO:data_websocket:Stopping all streams for display 'primary'...

[Wayland] Capture loop stopped.
```

29 minutes ago, M1K3Y said:

I've been trying to configure a few of the gaming related containers from linuxserver. I've followed the docs and added required values (nvidia-drm.modeset=1 nvidia_drm.fbdev=1), env, etc

How did you add that exactly?

Diagnostics alongside your docker run command would be good to know.

10 minutes ago, ich777 said:

How did you add that exactly?

Diagnostics alongside your docker run command would be good to know.

I added to my flash drive Syslinux configuration

---

default menu.c32

menu title Lime Technology, Inc.

prompt 0

timeout 50

label unRAID OS

  menu default

  kernel /bzimage

  append vfio-pci.ids=1912:0014 pcie_acs_override=downstream,multifunction initrd=/bzroot nvidia-drm.modeset=1 nvidia_drm.fbdev=1

label unRAID OS GUI Mode

  kernel /bzimage

  append pcie_acs_override=downstream,multifunction initrd=/bzroot,/bzroot-gui

label unRAID OS Safe Mode (no plugins, no GUI)

  kernel /bzimage

  append pcie_acs_override=downstream initrd=/bzroot unraidsafemode

label unRAID OS GUI Safe Mode (no plugins)

  kernel /bzimage

  append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui unraidsafemode

label Memtest86+

  kernel /memtest

I ran into a problem regarding having two GPUs as well. I have two gtx 1080. Both show up in system devices. When I have the latest, but wrong driver (v595), the plugin and everything else sees both GPUs, but obviously get the can't communicate error. When I install the correct driver (v580), The second GPU disappears everywhere except in the system devices. I was on unraid v7.2.4 and switch to 7.3.0beta2, but that did nothing. I have tried both independently without problems. I have switched the cards around, I have tried different gpu slots (all me slots work when using one card). I have tried messing with every BIOS settings, I have updated to the latest, bios, but nothing.

I have had both working in the past (around a year ago), but just recently put the 2nd gpu back into the server and ran into this problem.

In the logs, what I find is this error.

Apr 8 11:45:25 serverPGS kernel: NVRM: GPU 0000:81:00.0: RmInitAdapter failed! (0x24:0x72:1603)

Apr 8 11:45:25 serverPGS kernel: NVRM: GPU 0000:81:00.0: rm_init_adapter failed, device minor number 1

Apr 8 11:45:26 serverPGS kernel: NVRM: GPU 0000:81:00.0: RmInitAdapter failed! (0x24:0x72:1603)

Apr 8 11:45:26 serverPGS kernel: NVRM: GPU 0000:81:00.0: rm_init_adapter failed, device minor number 1

serverpgs-diagnostics-20260408-1154.zip

2 minutes ago, michaelfancey said:

I have had both working in the past (around a year ago), but just recently put the 2nd gpu back into the server and ran into this problem.

Please try to reseat the card but this seems like an issue with the PCI bus but I could be also be wrong about that.

Is your Power Supply up to the task? Please also try to update the BIOS if there is a newer BIOS version available and maybe also try to reset the BIOS back to defaults, sometimes it's only a small setting that needs to be changed.

1 hour ago, M1K3Y said:

  append vfio-pci.ids=1912:0014 pcie_acs_override=downstream,multifunction initrd=/bzroot nvidia-drm.modeset=1 nvidia_drm.fbdev=1

Looking good to me.

I just wanted to jump in again and thank @ich777 for nor only the Nvidia driver, but the iGPU one as well.

Having much better luck on my new Intel setup!

Hi everybody.

I laso got a problem with wayland especially with a linuxserver docker image (orcaslicer). To put it short the GPU acceleration is not working because some files are missing driver side. You can read the whole support thread here in Discord ⁠LinuxServer.io⁠.

Edited April 12Apr 12 by AvoooCadoo

7 hours ago, AvoooCadoo said:

I laso got a problem with wayland especially with a linuxserver docker image (orcaslicer). To put it short the GPU acceleration is not working because some files are missing driver side. You can read the whole support thread here in Discord ⁠LinuxServer.io⁠.

Can you please link the correct convo, you linked linuxserver.io directly

Ah sorry my bad did not check the link.

Here you go: https://discord.com/channels/354974912613449730/1492288595157975071

Also the resulting github issue:

https://github.com/linuxserver/docker-jenkins-builder/issues/392

Howdy. I just noticed I'm also stuck on an old driver like the person above. Image and diagnostics attached. Thanks.

unraid-diagnostics-20260413-0632.zip

1 minute ago, joey911 said:

Howdy. I just noticed I'm also stuck on an old driver like the person above. Image and diagnostics attached. Thanks.

Google is telling me support ended on my card with this version so this doesn't seem like the bug I thought it was.

4 hours ago, AvoooCadoo said:

Here you go: https://discord.com/channels/354974912613449730/1492288595157975071

I think I'm not in that Discord (even don't know which ono this is), could you please send me some screenshots please?

It just shows no text channels.

However I'm looking into that but TBH I have to say I don't even know where to start.
Do you have a link from the container, how do you run the container, where is your docker run output, do you have any Diagnostics, do you use wayland,...?