Lost bluetooth

[beerglass]

I've been running Proxmox VE 7.3-6 and with one guest which is linux OS and suddenly lost my bluetooth passthrough

The hardware is intel NUC and this is the error I now get

I can't figure out any fix and so coming here for any help

Many Thanks



root@nuc:~# dmesg | egrep -i 'blue|firm'
[ 4.967993] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 4.992897] Bluetooth: Core ver 2.22
[ 4.992913] NET: Registered PF_BLUETOOTH protocol family
[ 4.992914] Bluetooth: HCI device and connection manager initialized
[ 4.992917] Bluetooth: HCI socket layer initialized
[ 4.992919] Bluetooth: L2CAP socket layer initialized
[ 4.992922] Bluetooth: SCO socket layer initialized
[ 5.011971] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 5.013348] Bluetooth: hci0: Device revision is 2
[ 5.013351] Bluetooth: hci0: Secure boot is enabled
[ 5.013352] Bluetooth: hci0: OTP lock is enabled
[ 5.013353] Bluetooth: hci0: API lock is enabled
[ 5.013354] Bluetooth: hci0: Debug lock is disabled
[ 5.013356] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 5.050965] iwlwifi 0000:00:14.3: loaded firmware version 46.ea3728ee.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm
[ 5.059471] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 5.189366] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 6.540792] Bluetooth: hci0: Waiting for firmware download to complete
[ 6.541221] Bluetooth: hci0: Firmware loaded in 1447018 usecs
[ 6.541262] Bluetooth: hci0: Waiting for device to boot
[ 6.555225] Bluetooth: hci0: Device booted in 13658 usecs
[ 6.557906] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
[ 6.559235] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 6.562227] Bluetooth: hci0: Firmware revision 0.1 build 108 week 45 2022
[ 23.084365] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 23.085288] Bluetooth: hci0: Device revision is 2
[ 23.085309] Bluetooth: hci0: Secure boot is enabled
[ 23.085310] Bluetooth: hci0: OTP lock is enabled
[ 23.085311] Bluetooth: hci0: API lock is enabled
[ 23.085312] Bluetooth: hci0: Debug lock is disabled
[ 23.085313] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 23.114049] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 26.471708] Bluetooth: hci0: command 0xfc09 tx timeout
[ 34.503557] Bluetooth: hci0: Failed to send firmware data (-110)
[ 34.503741] Bluetooth: hci0: Intel reset sent to retry FW download
[ 36.679498] Bluetooth: hci0: command 0xfc1e tx timeout
[ 36.679498] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 37.778357] Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
[ 37.779289] Bluetooth: hci0: Device revision is 2
[ 37.779292] Bluetooth: hci0: Secure boot is enabled
[ 37.779293] Bluetooth: hci0: OTP lock is enabled
[ 37.779293] Bluetooth: hci0: API lock is enabled
[ 37.779294] Bluetooth: hci0: Debug lock is disabled
[ 37.779295] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 37.811596] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 39.332230] Bluetooth: hci0: urb 0000000005bc096d failed to resubmit (2)
[ 41.351342] Bluetooth: hci0: command 0xfc09 tx timeout
[ 49.414563] Bluetooth: hci0: Failed to send firmware data (-110)
[ 49.414703] Bluetooth: hci0: Intel reset sent to retry FW download
[ 51.589566] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 51.589565] Bluetooth: hci0: command 0xfc1e tx timeout

 

[jackb]

Came here to say that I think I have a similar issue to you. In my case, I only attempted to set this up yesterday and whilst it looked like it was working initially, it stopped working.

Details:
Hardware: Lenovo m70q tiny
Host OS: Proxmox 7.3-4
Guest OS: Ubuntu 20.
I am passing through USB Device 8087:0026 which in an Intel Wifi/BT module.

My experience is that when I first passed this device through to the guest, I was able to run bluetoothctl and perform a "scan le" which correctly discovered all of the BT MAC addresses that I expected to see. A short time later, this "scan le" stopped working.

When I review the dmesg on the host, I have a similar output to you:

dmesg | egrep -i 'blue|firm'

[ 0.604435] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 5.622344] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 5.627661] Bluetooth: Core ver 2.22
[ 5.629421] NET: Registered PF_BLUETOOTH protocol family
[ 5.630436] Bluetooth: HCI device and connection manager initialized
[ 5.631449] Bluetooth: HCI socket layer initialized
[ 5.632682] Bluetooth: L2CAP socket layer initialized
[ 5.633444] Bluetooth: SCO socket layer initialized
[ 5.711058] iwlwifi 0000:00:14.3: loaded firmware version 66.f1c864e0.0 QuZ-a0-hr-b0-66.ucode op_mode iwlmvm
[ 5.827078] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[ 5.827643] Bluetooth: hci0: Boot Address: 0x24800
[ 5.828166] Bluetooth: hci0: Firmware Version: 106-39.22
[ 5.828642] Bluetooth: hci0: Firmware already loaded
[ 5.869273] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 696.440551] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[ 696.441564] Bluetooth: hci0: Device revision is 2
[ 696.441581] Bluetooth: hci0: Secure boot is enabled
[ 696.441594] Bluetooth: hci0: OTP lock is enabled
[ 696.441606] Bluetooth: hci0: API lock is enabled
[ 696.441619] Bluetooth: hci0: Debug lock is disabled
[ 696.441631] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 696.476203] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[ 699.869457] Bluetooth: hci0: command 0xfc09 tx timeout
[ 707.901059] Bluetooth: hci0: Failed to send firmware data (-110)
[ 707.901141] Bluetooth: hci0: Intel reset sent to retry FW download
[ 710.077006] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 710.077006] Bluetooth: hci0: command 0xfc1e tx timeout
[ 713.281578] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[ 713.283580] Bluetooth: hci0: Device revision is 2
[ 713.284481] Bluetooth: hci0: Secure boot is enabled
[ 713.285374] Bluetooth: hci0: OTP lock is enabled
[ 713.286201] Bluetooth: hci0: API lock is enabled
[ 713.286923] Bluetooth: hci0: Debug lock is disabled
[ 713.287601] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 713.334720] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[ 714.825327] Bluetooth: hci0: urb 0000000082e1982f submission failed (2)
[ 714.825774] Bluetooth: hci0: sending frame failed (-2)
[ 716.828763] Bluetooth: hci0: command 0xfc09 tx timeout
[ 725.052661] Bluetooth: hci0: Failed to send firmware data (-110)
[ 725.053161] Bluetooth: hci0: Intel reset sent to retry FW download
[ 727.228531] Bluetooth: hci0: command 0xfc1e tx timeout
[ 727.228582] Bluetooth: hci0: Failed to read MSFT supported features (-110)
[ 5807.144663] ghash_clmulni_intel processor_thermal_device snd_hda_core btusb cec aesni_intel btrtl rc_core snd_hwdep btbcm i2c_algo_bit crypto_simd processor_thermal_rfim snd_pcm fb_sys_fops cryptd btintel processor_thermal_mbox iwlwifi bluetooth processor_thermal_rapl snd_timer syscopyarea input_leds snd rapl mei_me intel_rapl_common ecdh_generic sysfillrect apple_mfi_fastcharge ecc sysimgblt soundcore pcspkr efi_pstore think_lmi intel_cstate cfg80211 firmware_attributes_class ee1004 mei intel_wmi_thunderbolt intel_soc_dts_iosf wmi_bmof intel_pch_thermal serial_multi_instantiate int3400_thermal int3403_thermal acpi_thermal_rel int340x_thermal_zone mac_hid acpi_pad acpi_tad vhost_net vhost vhost_iotlb tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi drm sunrpc ip_tables x_tables autofs4 zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c simplefb

I seem to be able to get the "scan le" to work again by powering off the host and then doing a clean boot. But once again, this stops working after a short period of time.

I wondered if passing through the USB port might work but haven't tested. I also wondered if presenting Proxmox from loading the kernel modules and device firmware would work but again, I haven't tried this.