mkfelidae

Alright, I have it fixed.... a bit more hacked together than un-get for sure but here goes...... I first went and found a bluez package that was both built for slackware, and was newer than 5.63 (the busted version) I narrowed it down to this one: https://slackware.uk/slackware/slackware64-current/slackware64/n/bluez-5.70-x86_64-1.txz I then removed the one that un-get had installed, dumped the more up to date packages somewhere convenient (in my case /boot/config) and added the following line to my go file (/boot/config/go): installpkg /boot/config/go/bluez-5.70-x86_64-1.txz before the rc.d call (if you're using bluetooth inside home assistant you probably modified the go file already to add /etc/rc.d/rc.bluetooth start) I am running unraid 6.11.5 and havent tested anything more up to date, hope this helps.

I have the same issue, it is currently reported upstream in bluez but is definitely the dongle you are using (mine is doing it too) we have to wait for someone to repackage a newer version of bluez for slackware and then will need to update it from our end (i used un-get for my bluez)

I am truly stumped on this one. I have had a functioning Remote access to LAN running for over a year until changing my ISP (comcast -> Centurylink GPON Fiber) after changing I no longer could access all of the devices on my LAN I wanted to including a Ubuntu server. Some Devices respond to pings, some do not; and even more strange the list of devices is not set in stone. I haven't changed the settings within the wireguard clients nor in unRAID itself. I previously had a static route configured with my previous router, and had resetup that same static route in my new router, when this didn't work I actually switched out for another router entirely ( a cradlepoint AER2100) and configured a static route for that one too (my previous comcast setup is broken) I can ping some devices one the lan (the two that always are available are the default LAN gateway [either c4000z or the AER2100] and the unRAID host. I cannot resolve most of the other hosts on my network from a remote wireguard client. What am I doing wrong? let me know what I can include to better help troubleshoot this issue.

So I have the virsh commands for changing the Floppies/CD-Roms in a running VM here it is with breakdown: change-media [domain name] [vm-device-tag] [fully qualified path to disk to attach] --live should look like this (at least for me it did): change-media "Windows 3.11 For Workgroups" fda "/mnt/user/isos/Microsoft MS-DOS 6.22 Plus Enhanced Tools (3.5)/Disk1.img" --live this command should return a reply of: "successfully updated media" if it was successful XML for a floppy drive should look something like this: <disk type="file" device="floppy"> <driver name="qemu" type="raw"/> <target dev="fda" bus="fdc"/> <readonly/> <boot order="1"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> </disk> There are other flags like --update and --eject that may be useful for higher level OSs that track drive states, MS-Dos does not seem to do so. hope these help.

here is my WFW 3.11 XML rough ported to unraid from VMM, may still need to clean up the vm console as noVNC didn't like this quite yet. I attached floppies through GUI in VMM but you could likely do it through virsh editing while the VM is live, I can do some troubleshooting on that later if you would like but I have to go to work soon. At me specifically if I can help further as I sometimes don't get notifications from this thread. WFW 3.11 tcp-ip.xml

I have floppy images for windows 3.11 WFW and dos 6.22 I also have drivers for TCP-IP and the RTL8139 network interface card for WFW 3.11 I have an operational VM that was native to VMM (KVM/QEMU) and would likely just need some unRAID specific tweaks (like changing out spice for VNC and changing the emulator from kvm-spice to qemu-system-x86_64) let me know if that would be something you would like @sasdakota

I didn't see it in there either, I see you have several USB controllers bound to VFIO are those all going to one VM? or are they being passed to different VMs? The Intel AX200 chipset is designed to expose Wi-Fi over PCIe and bluetooth over USB, so unless Gigabyte did something strange with that chip it should have been connected to the rest of motherboard via both PCIe and USB. Check the VMs those USB hubs are connected, you're looking for a USB device with the Vendor ID 8087:0029. Hope this helps

That particular card exposes, (like most wifi/bluetooth cards) the bluetooth portion of the card as a USB device, check your USB devices and you should find one that is "intel bluetooth" or something, you have to pass that through separately.

I would appreciate this as well.

I use two USB tuner sticks, both from hauppage, a WinTV-HVR (a single ATSC tuner with composite video input as well) and a WinTV-DualHD (a double ATSC tuner with no other features) both appear to use different drivers. and for the DualHD it shows up as the same driver twice. This uses the LibreELEC drivers as far as I know, I have always used the LibreELEC build before as that was the only build that showed my tuners.

Looks good here, shows the Nvidia GPU information i would need to pass a GPU to a docker, shows my ZFS information (currently no pools is correct, i haven't set any up yet.) and also shows that there are DVB adapters on my system. Fine work I must say.

For those of us who would like to combine DVB drivers as well as NVIDIA GPU drivers I would like to thank @ich777. Huge shout out to all the help I got for getting it configured.

For what it is worth, there is a plug-in called UNBalance that allows you to move data off of an array drive into other drives.

48GB DDR3 ECC 16 GB to windows 10 WM 4 GB for Ubuntu VM Thinking of doing a 16GB ramdisk for scratch/ windows 10 "pagefile.sys"

I would like to see QEMU non-native emulation support. QEMU already has the ability to emulate non-native architectures. Just building all the emulation targets would be awesome. I honestly don't care if that means I have to write my Domain XML from scratch on non-native VMs; I would really like this as an option, especially if your already compiling QEMU for UNRAID. I would also like a drop in method for adding kernel modules, for drivers and the like. Rather than compiling a custom kernel for each use case.