teedge77

It's entirely possible I just messed it up and then fixed it. I originally tried the proprietary drivers, and it wouldn't see my 5090 at all. So, I read up on it some and saw I needed the open source drivers. When I tried those, it still didn't see the 5090. I do remember Claude saying it was still referencing the proprietary drivers or something somewhere. Maybe it didn't remove the proprietary drivers completely when i changed to the open source drivers, or I needed to reboot first. I'm not sure. I tried a few things and gave up.

So, I will make this short and to the point. I installed an RTX 5090 without knowing it was not well-supported in UNRAID. The TL;DR of it all is that I had Claude get it working for me and here are the steps that I had Claude outline. If there is anything that can be added or adjusted to make this work better, let me know, and I can update the original part to make it easier for others. If this just doesn't work for anyone, let me know that, and I can just dump it all out of here. Here it is: RTX 5090 on Unraid - Installing Open Kernel Modules The Problem The RTX 5090 (GB202/Blackwell) requires NVIDIA's open kernel modules. The standard Nvidia Driver plugin installs proprietary modules by default, which results in: - nvidia-smi returning "No devices were found" - dmesg showing: NVRM: installed in this system requires use of the NVIDIA open kernel modules. The GPU appears in lspci and the driver loads, but the proprietary modules refuse to initialize the card. The Fix 1. SSH into your Unraid server 2. Check that the GPU is detected by PCIe: lspci | grep -i nvidia You should see the RTX 5090 listed. 3. Confirm the error in dmesg: dmesg | grep -i nvidia Look for: NVRM: installed in this system requires use of the NVIDIA open kernel modules. 4. Remove the proprietary driver package: removepkg $(ls /var/log/packages/ | grep '^nvidia-[0-9]') 5. Download the open source driver package for your kernel: KERNEL=$(uname -r) wget -O /tmp/nvos.txz "https://github.com/unraid/unraid-nvidia-driver/releases/download/${KERNEL}/nvos-590.48.01-${KERNEL}-1.txz" Note: Check https://github.com/unraid/unraid-nvidia-driver/releases for the latest driver version available for your kernel. 6. Install the open source package: installpkg /tmp/nvos.txz 7. Unload the old modules and load the new ones: rmmod nvidia_uvm nvidia_drm nvidia_modeset nvidia 2>/dev/null modprobe nvidia modprobe nvidia_uvm 8. Verify it works: nvidia-smi You should see: NVIDIA GeForce RTX 5090 | 32607MiB | Driver 590.48.01 | CUDA 13.1 9. Make it persistent across reboots - update the plugin settings: sed -i 's/driver_version=.*/driver_version=latest_nos/' /boot/config/plugins/nvidia-driver/settings.cfg Hopefully, this helps others that have a 5090 they couldn't use or intended on getting one until they realized it's not well-supported without some work. I've spent so much time and money trying to get this thing set up for AI experimentation because I didn't know about certain hardware requirements and interconnections. If anyone is interested in more about what my setup is, let me know. Here is a little info on it: M/B: ASRockRack B650D4U-2L2T/BCM Version 4.01 s/n M80-J5S00800165 BIOS: American Megatrends International, LLC. Version 20.07 Dated 10/17/2024 CPU: AMD Ryzen 9 7950X3D 16-Core @ 4200 MHz HVM: Enabled IOMMU: Enabled Cache: L1 - Cache: 1 MiB, L2 - Cache: 16 MiB, L3 - Cache: 128 MiB Memory: 128 GiB DDR5 (max. installable capacity 128 GiB) (Special thank you to JorgeB for suggesting I put this in here.)

I think I messed that one up. When I look at the other containers, they have the port set correctly. I think I probably just give up. Maybe I will try to figure it out again someday, when I'm tired of it again. Thanks for the help.

This is how they are formatted: http://[IP]:[PORT] Is that correct?

Any tip(s) on how to configure them?

I use it for most but not all.

Nothing I see in the diagnostics. This is also for every container, not just that one. Included my diagnostics, since I'm definitely no expert. zion-diagnostics-20220609-1601.zip

OK, I've checked here: https://wiki.unraid.net/Manual/Docker_Management and here: https://forums.unraid.net/topic/57181-docker-faq/ and have not found where to configure it. Could you elaborate a little?

I used to be able to click a docker icon, get a dropdown, and from that dropdown, i could click the web gui link to open the docker's web site. That doesn't appear anymore. Is there a place to enable that or is this an isolated issue for me? I've attached an image of what I now see.

Anyone have an issue with there being two instances of port 9022 in the template and it makes the docker not start? I originally fixed it by removing one, but then Fix Common Problems complained, so I just changed one to 9023. Just wanted to check on this to see if it's truly the original docker template or if my template was somehow misconfigured by me.

the one (and there is now only one) available via Community Applications plugin. I see a dropdown for "script" and two options: Joe L. and gfjardim. Should I not be seeing those both?

Sure. I definitely understand the need for Lime Technology to be clear that they aren't encouraging illegal activities. However, something more inquisitory and less accusatory would have been nice. I could have explained what I was doing, as opposed to suddenly having to defend myself. Anyway, not a big deal. I would have been more butthurt if I had been banned or my post removed. Sidenote, I still haven't found time to get the old cards into unRAID. Not that anyone cares. Ha.

Ah, great. Thank you for the help. Unfortunately, I am traveling this week. Once I get back, I will give it a shot though.

So, it occurred to me that it may be possible to just use a Debian VM with GPU pass-through to accomplish this. Is it possible to pass-through 2 GPUs to a single VM?

I used to read comp.os.minix articles last millennium from the command line using the tin newsreader and I'm quite disturbed by what Usenet has become and how people now pay a subscription for the privilege of downloading pirated material in high definition automatically. I now understand why people insist on redacting their diagnostics before posting here. It's an aspect of home NAS usage I find quite distasteful. On the other hand, I've been trying to crack RC5 ciphers for years and for fun, mostly via the distributed.net project, and first with CPUs and then with GPUs. There's nothing sinister about that at all and the 72-bit version is proving to be extremely difficult to crack by brute force alone. I can't help the OP, I'm afraid, because I use AMD GPUs with other OS distributions, but I thought his comments deserved some support. My unRAID servers are just used to store my lifetime's accumulated documents, photographs, music and video, every single file either created by me or else paid for and legitimate, with the original stored away and available as proof. Thank you for the support. We do a lot of hash-cracking for our testing because passwords really are a great attack vector. Even Domain Admins, whether people or service accounts, still use very poorly chosen passwords. Getting access to a Domain Controller via an authenticated user or...null sessions (which are actually still out there) is an extremely easy way to start password attacks. Hash-cracking an entire domain worth of hashes gives the client the added benefit of knowing how well training goes, or just how poorly they still choose passwords. Applications like pipal give very good statistics on passwords. I did consider getting AMD cards this time because they have always had a significant advantage in GPU cracking over NVIDIA. I think my choice was 1 part NVIDIA "fanboi" and 1 part always used NVIDIA, so I know how to get it all working. I spent some time yesterday comparing hash-cracking speeds on CPU vs GPU and also speeds of a few different hashes. We also looked at how the reporting for speeds is different between hashcat and oclhashcat, which seemed strange. Right now, I manage about 4 billion hashes/second on NTLM. Looking at some of the rigs online with 8 AMD graphics cards, they are getting around 120 billion. It's all very interesting and I am by no means a cryptography expert, but I definitely am interested in learning more and experimenting to understand things a little better. Anyway...I suppose I am getting off-topic. Thanks again for helping explain there's isn't necessarily anything evil in cracking hashes.