August 13, 20187 yr I have a Bluetooth dongle that I want to use in a docker container. Docker requires that the Host OS install drivers for the device before it can be passed to the container. Searching the forums it appears I am not alone in that need, particularly for the users of Home Assistant. See this post for more info: Edited August 13, 20187 yr by kmwoley
August 13, 20187 yr +1 You are not alone. I’m using several home automation appliances via docker on unraid, where Bluetooth support is mandatory these days. Using another host or VM just for supporting Bluetooth is a huge pain. PLEASE add Bluetooth support. Edited August 13, 20187 yr by Diggewuff
August 13, 20187 yr +1 I have this exact use case also, It doesn't really make sense to make a VM with a docker container (home assistant) inside it just to be able to use a bluetooth dongle with unraid. Please add support for it at the OS level.
October 29, 20187 yr Author I don’t know what captures the @limetech folks attention to provide feedback on feature requests. This got posted in at the time 6.5 was getting prepped to ship, so maybe there’s time to look at it now?
October 29, 20187 yr Author That’s my understanding, yes. I’m not at all an expert, but I recall potentially needing bluez-libs and bluez-utils (bluez.org) to make it all work.
October 29, 20187 yr 15 minutes ago, kmwoley said: bluez-libs and bluez-utils Those are user-space utils that would be installed within a container I think.
October 29, 20187 yr Author If so, that’s easy. Kernel driver support is the biggest blocker. I am happy to test if you need it. Thanks for for looking into it!
November 13, 20187 yr If I can just 'pile on' to this thread... I have a MB with integrated Bluetooth (uses Intel 8260 communication module, which is connected via PCIE) and I want to pass that through to a docker. If I was using a VM instead, I'm sure I could just pass this IOMMU group: IOMMU group 17:[8086:24f3] 06:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) But I would prefer to use the docker so would need the kernel module. Is the correct module called 'btintel'? I guess it's not supported in the current kernel given: modprobe btintel modprobe: FATAL: Module btintel not found in directory /lib/modules/4.18.17-unRAID
November 13, 20187 yr 13 hours ago, dazzathewiz said: it's not supported in the current kernel given: Correct. We're adding bt kernel drivers in Unraid 6.7 release.
January 22, 20197 yr Yay!! Quote Added Bluetooth support in the Linux kernel. We did not add the user-space tools so this will be mostly useful to support Bluetooth in docker containers.
January 22, 20197 yr 1 hour ago, dazzathewiz said: Yay Let me know how this works out. There are a set of realtek bluetooth devices which require firmware and I've had a hard time finding the "official" firmware bin files. We'll keep an eye out for them but if the device doesn't work and it's realtek, check the syslog to see if there is a message indicating "can't find firmware".
January 23, 20197 yr Please let me know if you want to see the full syslog, but here is what I am seeing in mine Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM20702A Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 Jan 22 20:41:54 kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
January 23, 20197 yr 57 minutes ago, indy5 said: Please let me know if you want to see the full syslog, but here is what I am seeing in mine Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM20702A Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 Jan 22 20:41:54 kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 Jan 22 20:41:54 kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found Following this: https://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux/ We added that firmware for the next -rc release. Note: There may be other missing firmware you may run across depending on what device you're using. The problem is that the Linux world doesn't much like firmware - firmware files are referred to as 'blobs' which means they are just binary data files, which means they are not built from source. There is a kernel firmware repo but in our experience different manufacturers are slow to submit their firmware (looking at you again Realtek). For example, why didn't those guys at plugable submit this firmware to be included upstream? Then they wouldn't have had to write that article explaining how to make it work. Oh well...
January 25, 20197 yr On 1/23/2019 at 1:44 PM, limetech said: Following this: https://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux/ We added that firmware for the next -rc release. Note: There may be other missing firmware you may run across depending on what device you're using. The problem is that the Linux world doesn't much like firmware - firmware files are referred to as 'blobs' which means they are just binary data files, which means they are not built from source. There is a kernel firmware repo but in our experience different manufacturers are slow to submit their firmware (looking at you again Realtek). For example, why didn't those guys at plugable submit this firmware to be included upstream? Then they wouldn't have had to write that article explaining how to make it work. Oh well... I have upgraded to RC2 and am still having issues with this device. Jan 25 09:26:35 kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 Jan 25 09:26:35 kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.