I have two different PCs with two different sets of Bluetooth hardware, and on both of them Bluetooth got broken on upgrade to 23.10.
The primary symptom on both is that in the Bluetooth Manager, when I try and turn Bluetooth on it still says it's off (I think a screenshot is attached, though I'm not sure with this newer forum post interface).
One of my PCs is a Dell Precision M6700, and here's the dmesg output:
Code:
(base) scott@oem-Precision-M6700:~$ sudo dmesg | grep -i bluetooth[sudo] password for scott:
[ 1.296992] usb 1-1.4: Product: DW380 Bluetooth Module
[ 18.968989] Bluetooth: Core ver 2.22
[ 18.969011] NET: Registered PF_BLUETOOTH protocol family
[ 18.969012] Bluetooth: HCI device and connection manager initialized
[ 18.969016] Bluetooth: HCI socket layer initialized
[ 18.969018] Bluetooth: L2CAP socket layer initialized
[ 18.969022] Bluetooth: SCO socket layer initialized
[ 19.554007] Bluetooth: hci0: BCM: chip id 63
[ 19.554983] Bluetooth: hci0: BCM: features 0x07
[ 19.570988] Bluetooth: hci0: Dell Wireless 380 Bluetooth 4.0 Module
[ 19.570993] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1447
[ 19.721746] Bluetooth: hci0: BCM20702A1 'brcm/BCM20702A1-413c-8197.hcd' Patch
[ 20.577969] Bluetooth: hci0: BCM: features 0x07
[ 20.593973] Bluetooth: hci0: Dell Wireless 380 Bluetooth 4.0 Module
[ 20.593975] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1447
My second is a Beelink SER5 MAX with Ryzen 7 5800H, and its dmesg output is:
Code:
(base) scott@beelink-5800u:~$ sudo dmesg | grep -i bluetooth
[sudo] password for scott:
[ 2.075035] Bluetooth: Core ver 2.22
[ 2.075055] NET: Registered PF_BLUETOOTH protocol family
[ 2.075058] Bluetooth: HCI device and connection manager initialized
[ 2.075061] Bluetooth: HCI socket layer initialized
[ 2.075065] Bluetooth: L2CAP socket layer initialized
[ 2.075070] Bluetooth: SCO socket layer initialized
[ 2.210720] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 2.210735] Bluetooth: hci0: Boot Address: 0x24800
[ 2.210737] Bluetooth: hci0: Firmware Version: 255-255.255
[ 2.213363] Bluetooth: hci0: FW download error recovery failed (-19)
[ 2.213407] Bluetooth: hci0: sending frame failed (-19)
[ 2.213425] Bluetooth: hci0: Reading supported features failed (-19)
[ 2.213437] Bluetooth: hci0: Error reading debug features
[ 2.213439] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[ 2.213446] Bluetooth: hci0: sending frame failed (-19)
[ 2.213460] Bluetooth: hci0: Failed to read MSFT supported features (-19)
[ 4.576511] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 4.578505] Bluetooth: hci0: Device revision is 1
[ 4.578509] Bluetooth: hci0: Secure boot is enabled
[ 4.578511] Bluetooth: hci0: OTP lock is enabled
[ 4.578513] Bluetooth: hci0: API lock is enabled
[ 4.578515] Bluetooth: hci0: Debug lock is disabled
[ 4.578516] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 4.584019] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 4.584038] Bluetooth: hci0: Boot Address: 0x24800
[ 4.584040] Bluetooth: hci0: Firmware Version: 255-255.255
[ 6.017237] Bluetooth: hci0: Waiting for firmware download to complete
[ 6.017480] Bluetooth: hci0: Firmware loaded in 1399829 usecs
[ 6.017540] Bluetooth: hci0: Waiting for device to boot
[ 6.032546] Bluetooth: hci0: Device booted in 14687 usecs
[ 6.032572] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 6.032889] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[ 6.039137] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 6.041627] Bluetooth: hci0: Firmware revision 0.3 build 249 week 27 2023
[ 6.047711] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
So it seems there are two different problems, but the same overall symptom.
Bluetooth worked just fine on 23.04 Budgie before the upgrade.
Honestly, I've never had a great experience using upgrade, though it had been a few years since I actually did one as I went to Chromebooks for my daily driver home PCs for a couple years. Got two new PCs a couple months back and went back to full-blown Linux.
Any help wold be appreciated.
Thanks,
Scott
Bookmarks