Trouble passing through Bluetooth USB device

pm41aif

New Member
Aug 9, 2022
10
3
3
Hello community,
I have recently installed the latest version of Proxmox and restored all my VMs into a clean pool. No hardware or hardware configuration was changed on the system.
So some strange reason one of my Bluetooth devices (USB) is not available for the host anymore, and by that I mean, it is not visible under USB devices to assign to VM anymore (web UI). After some research I found the device using this command:

lsusb | grep Bluetooth
Bus 005 Device 008: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

For some reason (unclear to me) the vendor id and product id are different from my previous Proxmox install.
Adding the device 0a5c:4500 manually to a VM config file, doesn’t do much for the device to be passed to the VM. It shows up as “unknown” in the list and nothing happens.

Can someone please give a hand or point me into the right direction?
Many thanks in advance.
 
Have you tried passing the device through the USB port instead of the vendor/device id.
 
Have you tried passing the device through the USB port instead of the vendor/device id.
Thank you for replying mate. The device itself doesn't appear in any lists within the webui. The device is a build in wifi and Bluetooth module from the mother board. In the past, in order to get its full functionality I would pcie passthrough the wifi part and usb passthough the Bluetooth part to a vm, without any problem. Can it be that somehow the host is holding onto the Bluetooth device and that's why it is not showing up in the list?
 
Last edited:
In the past, in order to get its full functionality I would pcie passthrough the wifi part and usb passthough the Bluetooth part. Can it that somehow the host is holding onto the Bluetooth device and that's why it is not showing up in the list?
Not the host, but maybe the Bluetooth device is connected internally to a USB controller that you passed through to another VM?
 
lsusb | grep Bluetooth
Bus 005 Device 008: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
This is a USB hub and those cannot be passed through. Can you show the whole output of lsusb?
EDIT: My onboard Bluetooth device (which is also combined with a PCIe WiFi) is named Wireless_Device, which I did not recognize at first.
 
Last edited:
Not the host, but maybe the Bluetooth device is connected internally to a USB controller that you passed through to another VM?
Thank you for the idea. I have only two VMs running. I tried running only the Windows VM which misses the Bluetooth device, tried passing through the USB devices as devices and not as ports (in case any of the ports was part of the USB controller connected to the BT device), tied adding the WiFi card to /etc/modprobe.d/vfio-pci.conf, checked BIOS settings, Bluetooth controller is enabled, updated Proxmox, same result, BT not being picked up by the Windows VM.

The one difference that changed after adding the WiFi card to /etc/modprobe.d/vfio-pci.conf, is that the manually added BT device within the VM config file doesn't show up in red anymore, as shown in the screenshot of prior condition.

The whole output of lsusb is:
Code:
Bus 009 Device 006: ID 1532:0083 Razer USA, Ltd RC30-0315, Gaming Mouse [Basilisk X HyperSpeed]
Bus 009 Device 007: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI)
Bus 009 Device 005: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 009 Device 004: ID 0403:7a58 Future Technology Devices International, Ltd USB <-> Serial Cable
Bus 009 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 009 Device 002: ID 056a:0026 Wacom Co., Ltd PTH-450 [Intuos5 touch (S)]
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 003: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer
Bus 010 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 009: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 005 Device 007: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 005 Device 012: ID 05ac:8289 Apple, Inc. Bluetooth Host Controller
Bus 005 Device 008: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 005 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1532:0083 Razer USA, Ltd RC30-0315, Gaming Mouse [Basilisk X HyperSpeed]
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Here is a print out of the PCIe Wifi card (in case if it helps for anything):

Code:
 lspci -v
3a:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
    Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
    Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 35
    Memory at ed800000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [40] Express Endpoint, MSI 00
    Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [14c] Latency Tolerance Reporting
    Capabilities: [154] L1 PM Substates
    Kernel driver in use: vfio-pci
    Kernel modules: iwlwifi
 

Attachments

  • Screen Shot 2023-10-28 at 5.32.06 pm.png
    Screen Shot 2023-10-28 at 5.32.06 pm.png
    59.1 KB · Views: 3
Bus 005 Device 012: ID 05ac:8289 Apple, Inc. Bluetooth Host Controller Bus 005 Device 008: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Funny how the "Apple, Inc. Bluetooth Host Controller" has the same vendor ID as "Broadcom Corp. BCM2046". 05ac:8289 is not the Bluetooth controller you are looking for? The name/description of devices can vary depending on which updates are installed.
 
Funny how the "Apple, Inc. Bluetooth Host Controller" has the same vendor ID as "Broadcom Corp. BCM2046". 05ac:8289 is not the Bluetooth controller you are looking for? The name/description of devices can vary depending on which updates are installed.
I agree, it is rather strange, and I don't understand how it came to this. In my previous Proxmox install they were different. The "Apple, Inc. Bluetooth Host Controller" is another WiFi card that I use for a MacOS VM (native controller for AirDrop), which works just fine.

After looking further into the device I am trying to troubleshoot (0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)), I tried passing through only the mentioned USB port (usb4: host=5-5.2). This had the same result, not visible, not accessible for the VM.

Then, I went a step further and tried passing through the USB controller this port is sitting on, just to see if it changes anything. The result was a bunch of devices and ports appearing on the Windows side, a Bluetooth device being one of them. Now, in theory with the correct Bluetooth device being passed through, it should work out of the box. In this case however, I can see a BT device in Device manger but no driver installed, no working. I tried downloading and installing the appropriate drivers from the motherboard manufacturer, no change. I have attached a screenshot of the Device manager in the Windows VM. This BT device ended up being the "Apple, Inc. Bluetooth Host Controller" because it sits on the same vendor ID as you mentioned yourself. But no sign of the 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth).

BTW, I thought the Apple Wifi/BT card should be just picked up by Windows but no, it can see it but no fitting drivers.

Is there a way, somehow to split those two? I am running Proxmox 8.0.4 if its helpful.

This is a command I used to dig deeper:
Code:
udevadm info --query=all --name=/dev/bus/usb/005/008
P: /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:3c:00.3/usb5/5-5/5-5.2
M: 5-5.2
R: 2
U: usb
T: usb_device
D: c 189:519
N: bus/usb/005/008
L: 0
V: usb
E: DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:3c:00.3/usb5/5-5/5-5.2
E: DEVNAME=/dev/bus/usb/005/008
E: DEVTYPE=usb_device
E: DRIVER=usb
E: PRODUCT=a5c/4500/100
E: TYPE=9/0/0
E: BUSNUM=005
E: DEVNUM=008
E: MAJOR=189
E: MINOR=519
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=15069441
E: ID_BUS=usb
E: ID_MODEL=BRCM20702_Hub
E: ID_MODEL_ENC=BRCM20702\x20Hub
E: ID_MODEL_ID=4500
E: ID_SERIAL=Apple_Inc._BRCM20702_Hub
E: ID_VENDOR=Apple_Inc.
E: ID_VENDOR_ENC=Apple\x20Inc.
E: ID_VENDOR_ID=0a5c
E: ID_REVISION=0100
E: ID_USB_MODEL=BRCM20702_Hub
E: ID_USB_MODEL_ENC=BRCM20702\x20Hub
E: ID_USB_MODEL_ID=4500
E: ID_USB_SERIAL=Apple_Inc._BRCM20702_Hub
E: ID_USB_VENDOR=Apple_Inc.
E: ID_USB_VENDOR_ENC=Apple\x20Inc.
E: ID_USB_VENDOR_ID=0a5c
E: ID_USB_REVISION=0100
E: ID_USB_INTERFACES=:090000:
E: ID_VENDOR_FROM_DATABASE=Broadcom Corp.
E: ID_MODEL_FROM_DATABASE=BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
E: ID_PATH=pci-0000:3c:00.3-usb-0:5.2
E: ID_PATH_TAG=pci-0000_3c_00_3-usb-0_5_2
E: ID_FOR_SEAT=usb-pci-0000_3c_00_3-usb-0_5_2
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:
 

Attachments

  • Screen Shot 2023-10-29 at 10.35.39 am.png
    Screen Shot 2023-10-29 at 10.35.39 am.png
    217.2 KB · Views: 1

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!