Everything posted by ich777
-
[Plugin] Nvidia-Driver
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.
-
[Plugin] Nvidia-Driver
Can you please share Diagnostics or at least a screenshot or a animation from what doesn't work or what are you exactly selecting?
-
[Plugin] Nvidia-Driver
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?
-
GPU‑Container starten nicht: nvidia-container-cli: ldcache error: process /sbin/ldconfig failed (Unraid + Nvidia Driver Plugin)
docker run und auch die Diagnostics fehlen. Die toml ist falsch. Bitte mach eine saubere Deinstallation Neustinstallation vom Plugin: Plugin löschen Reboot Plugin neu installieren Evtl. Treiber auswählen wenn du einen anderen brauchst Reboot
-
[Plugin] LXC Plugin
Sorry about that @Nooke & @ostenax, I'll look into that. Give me a bit. EDIT: Please reinstall or check for LXC updates within the plugins settings page itself, this is now fixed.
-
[Plugin] Nvidia-Driver
Sorry but this was 28 days ago and with the old Nvidia Driver and the driver was compiled 5 days ago: 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.
-
[Plugin] Nvidia-Driver
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.
-
[Plugin] Nvidia-Driver
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.
-
[Plugin] Nvidia-Driver
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. EDIT: No, I don't think so because it seems that not many users have that issue like you have and the Driver is for all cards the same.
-
[Plugin] Nvidia-Driver
And if you redownload the driver, does it say the checksum matches?
-
[Support] ich777 - Gameserver Dockers
I think you all should look at the pinned post from @Cyd for ARK since it's the same engine IIRC.
-
[Plugin] Nvidia-Driver
Remove the two NVIDIA_* variables and replace the extra parameter --runtime nvidia with --gpus all
-
[Plugin] Nvidia-Driver
An what about removing the --runtime nvidia and these two variables and adding --gpus all
-
[Plugin] Nvidia-Driver
I would strongly recommend that you change that to you actual GPU UUID.
-
[Plugin] Nvidia-Driver
Do you have Diagnostics or anything? Please post your Diagnostics if something is not working.
-
[Support] ich777 - Gameserver Dockers
Please update the container itself and try if it is working.
-
[Support] CrowdSec Threat Map Docker Template (crowdsec-threat-map-docker)
Von dort wirst du keine Antwort erhalten vermute ich. Den Unraid Support, also mit einem Ticket würde ich das machen: https://unraid.net/support?srsltid=AfmBOoqicyZxvnNZrUMkynWR26F3LJHaAQsP422QgNCc4dfpKskk96SH Kann dir da leider nicht mehrsagen.
-
[Support] CrowdSec Threat Map Docker Template (crowdsec-threat-map-docker)
Kann da leider nicht weiterhelfen, bitte an den support wenden.
-
[Plugin] Nvidia-Driver
First of all you have a lot of those lines in your syslog: Apr 26 15:38:31 Futro kernel: input: Mouse passthrough as /devices/virtual/input/input5 Apr 26 15:38:31 Futro kernel: input: Mouse passthrough (absolute) as /devices/virtual/input/input6 Apr 26 15:38:31 Futro kernel: input: Keyboard passthrough as /devices/virtual/input/input7 Apr 26 15:38:31 Futro kernel: input: Sunshine Nintendo (virtual) pad as /devices/virtual/input/input8 Apr 26 15:38:31 Futro kernel: input: Sunshine X-Box One (virtual) pad as /devices/virtual/input/input9 Apr 26 15:38:31 Futro kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 26 15:38:34 Futro acpid: input device has been disconnected, fd 11 Apr 26 15:38:35 Futro kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0 ### [PREVIOUS LINE REPEATED 2 TIMES] ### Apr 26 15:38:36 Futro kernel: traps: light-locker[74379] trap int3 ip:14dde23fea77 sp:7fff1a91b290 error:0 in libglib-2.0.so.0.8400.4[66a77,14dde23b7000+a1000] Apr 26 15:38:36 Futro kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0 ### [PREVIOUS LINE REPEATED 3 TIMES] ### Not sure what causes that since I'm not very familiar with the Steam Headless container. Please also post your docker run command if possible. Didn't you also have to create a modprobe.d file for the container to properly run? Yes, that's caused because 50 series needs to have the OpenSource driver installed.
-
[Plugin] Nvidia-Driver
Then please leave it as is, as noted above, this is not working for all users, may depends on the hardware which I did not test.
-
[Plugin] Nvidia-Driver
No, just the driver packages where updated. Just redownload a driver and everything should hopefully be good. Pleasr do keep note you should now use --gpus all in Extra Parameters and delete --runtime nvidia since everything should now be handled by Docker
-
[Plugin] Nvidia-Driver
Maybe, but if you make a few mistakes in a row while pushing a big update in the background to the nvidia-container-toolkit and libnvidia-container can be troublesome at times :D
-
[Plugin] Nvidia-Driver
So your issue is fixed anyways. I upgraded the Nvidia toolkit to the latest version and made a mistake with one line, however it seems that the new container runtime causes issues for some users. But for all latest versions the issue should be fixed so to speak for Unraid 7.2.4 and Unraid 7.2.0-rc.1, I'll trigger the new build for Unraid 7.2.5-rc.2 now.
-
[Plugin] Nvidia-Driver
When did you exactly upgrade?
-
[Plugin] Nvidia-Driver
This is fixed in about an hour.