jafo09

Hi everyone, not sure if this helps but always like to share info when I can. Similar issue as described here - Plex working fine then all of a sudden (with no known changes made to either unraid server or home networking setup) it became unreachable from either the dcoker UI or from three other clients throughout the house all connected via ethernet. Unraid server was working fine, able to connect to internet etc. I was about to start rebooting everything (although i was super reluctant to reboot the unraid server as I'm at 82 days of uptime and super happy with how stable it has been) when I noticed there was an update available for the plex docker. I applied it, re-started the docker and then (so far - half an hour later) have had no problems. If anyone wants me to check anything in log files etc just let me know - happy to provide more info. Really can't correlate the two activities but there it is... Mike

Also confirming this weird behaviour, have had Windows VM running for months and suddenly this morning very frequent disconnects. Eventually I can get it reconneceted and it's stable for a long period of time (measured in minutes) and then it goes through the disconnect dance. The VM is unaffected (i.e it doesn't crash or change state). I think I'm on 6.8.2 as well but have been for quite a while (weeks at least)...and I have made no changes in the past month as it has performed very well aside from this new quirk.

Seemed to work, haven't had a chance yet to actually try bluetooth but I think everything got loaded based on what I see in the logs? Thanks for adding them. Mike Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi ... Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Waiting for firmware download to complete Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Firmware loaded in 2723888 usecs Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Waiting for device to boot Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Device booted in 15546 usecs Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-18-16-1.ddc Jan 19 12:21:39 EMT kernel: Bluetooth: hci0: Applying Intel DDC parameters completed

Thanks Chuck, I will try your method, I didn't realize you didn't need BT drivers in the main unraid image. Just fyi I am trying to enable it in my Plex docker so seems like a similar approach to what you did for node-red might work.

Will update, always good to be on the latest stable release. root@EMT:/lib/firmware/intel# modinfo btintel filename: /lib/modules/4.19.56-Unraid/kernel/drivers/bluetooth/btintel.ko.xz firmware: intel/ibt-12-16.ddc firmware: intel/ibt-12-16.sfi firmware: intel/ibt-11-5.ddc firmware: intel/ibt-11-5.sfi license: GPL version: 0.1 description: Bluetooth support for Intel devices ver 0.1 author: Marcel Holtmann <[email protected]> srcversion: B978516D847A719EA755825 depends: bluetooth retpoline: Y intree: Y name: btintel vermagic: 4.19.56-Unraid SMP mod_unload

Hi, I just built an unraid server ( Linux 4.19.56-Unraid x86_64). Motherboard is a Gigabyte B450 I AORUS PRO WIFI-CF. Was trying to get bluetooth enabled and noticed in syslog it is looking for intel/ibt-18-16-1.sfi (actual error below). It appears the unraid boot image contains ibt-11-5 and ibt-12-16. Is there anything obvious I should try (aside from trying to wget the right driver and permanently store it in ram duh :-)). Trying to patch in the driver to the boot flash drive image seems a bit daunting... Error: hci0: Direct firmware load for intel/ibt-18-16-1.sfi failed with error -2