PenTurDucKenLinE

@ich777 @itimpi @primeval_god Thank you to each of you for your responses! 😃 @primeval_god Do you think there's any chance some Unraid community members would be willing to collaborate on creating a Distrobox plugin? I can tinker around with testing stuff, but I'd have to use AI to actually build a plugin myself. I wonder whether Limetech would jump in if they saw enough people interested in it?

@ich777 Got it! When you develop your plugins, do you have a test rig? Not sure the best way to test plugins on Unraid.

@ich777 You've created many great plugins and have a lot of insight into what's possible on Unraid... what are your thoughts on the possibility of creating a distrobox plugin that (1) installs distrobox, and (2) helps manage installed distro images?

It would be great if Distrobox could be available on Unraid. Ive heard some people have been able to install it.

Copy that! Thank you @ich777 ! Appreciate ya! Once I get everything set up and have a chance to dig in, I'll circle back here... probably with more questions, haha.

According to the manufacturer I'm going with, the minimum Linux Kernel version that supports this AMD hardware is 6.11, but they recommend 6.15 or the latest. As I understand, Unraid currently uses 6.12.24-Unraid, so I'm thinking the hardware will be at least basically supported. I guess I'm just not familiar enough with Slackware to know whether there are any options to update driver packages on Unraid to newer versions.

Hi @ich777 ! I'll soon be trying to set up Unraid on a PC with AMD Ryzen AI Max+ 395 processor. Not sure how familiar you are with that, but this device has a whole bunch of stuff integrated into it, including a GPU and NPU. I'm not sure to what extent Unraid and/or Slackware kernels support the components of this AMD APU. Furthermore, I'm not sure how easy/difficult it is to get the newest version of AMD ROCm on Unraid/Slackware. So, I have a few questions for you: Do you have any feedback or ideas on how to ensure I can get appropriate / updated drivers for the AMD Ryzen AI Max+ 395 on Unraid Do you think your Unraid Plugin Update Helper could be the basis for providing more updated driver support for an AMD processor like the AMD Ryzen AI Max+ 395 ? If "yes" to #2, is there any way I could help create that plugin?

🤦‍♂️ oh... Oops, yeah, haha... thank you!

Copy that! My apologies, who is LT?

@dlandon First off, thank you so much for your hard work on developing this plugin - as a (newish) Unraid user, it has been quite helpful! Recently I bought some NVMe modules in preparation for a new server I'm going to build. I bought a couple Sabrent USB NVMe enclosures (Model EC-SNVE) for the NVMe modules to test out Unraids pool functionality. However, I noticed a couple problems: UA recognizes the Sabrent enclosure, but not the NVMe modules. UA sees both of the enclosures as the same device, showing each drive as separate partitions of the same device. UA seemingly can't distinguish between the two Sabrent enclosures because the controller on each one is programmed with the same serial. To get UA to recognize the NVMe modules (and thus see each device as distinct devices), I had to do the following: # Edit the udev rule nano /etc/udev/rules.d/99-nvme-serial-mapping.rules # Create unique by-id entries based on NVMe serials and USB port location SUBSYSTEM=="block", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000001*", ENV{ID_SERIAL}="Sabrent_NVMe_1000000001", ENV{ID_SERIAL_SHORT}="1000000001", SYMLINK+="disk/by-id/nvme-Sabrent_1000000001%n" SUBSYSTEM=="block", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000002*", ENV{ID_SERIAL}="Sabrent_NVMe_1000000002", ENV{ID_SERIAL_SHORT}="1000000002", SYMLINK+="disk/by-id/nvme-Sabrent_1000000002%n" # Also create unique USB-style identifiers by port location SUBSYSTEM=="block", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="9210", KERNELS=="1-3:*", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000001*", SYMLINK+="disk/by-id/usb-Sabrent_SSD_1000000001-0:0%n" SUBSYSTEM=="block", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="9210", KERNELS=="1-1:*", PROGRAM=="/usr/sbin/smartctl -i $devnode", RESULT=="*Serial Number:*1000000002*", SYMLINK+="disk/by-id/usb-Sabrent_SSD_1000000002-0:0%n" # Reload rules udevadm control --reload-rules udevadm trigger Do you have any recommendations on any other way to work with this issue?