I have been having issues with pairing and maintaining connection with bluetooth on 24.04.
The bluetooth worked flawlessly both on Jammy and it also works windows 11. Has anyone else had issues with bluetooth on 24.04?
Has it been just recently? Can you post results from terminal for lsusb; sudo dmesg|egrep -i 'blue|firm'; uname -r
Hey Jeremy, thanks for response. The unformatted text reads like garbage so here is the copy and paste job.
tony@linuxmint:~$ sudo dmesg|egrep -i ‘blue|firm’; uname -r
[sudo] password for tony:
[ 0.296751] DMAR: [Firmware Bug]: RMRR entry for device 09:00.0 is broken - applying workaround
[ 0.296754] DMAR: [Firmware Bug]: RMRR entry for device 0a:00.0 is broken - applying workaround
[ 4.661868] Bluetooth: Core ver 2.22
[ 4.661893] NET: Registered PF_BLUETOOTH protocol family
[ 4.661895] Bluetooth: HCI device and connection manager initialized
[ 4.661898] Bluetooth: HCI socket layer initialized
[ 4.661901] Bluetooth: L2CAP socket layer initialized
[ 4.661906] Bluetooth: SCO socket layer initialized
[ 4.777265] Bluetooth: hci1: CSR: Setting up dongle with HCI ver=6 rev=22bb
[ 4.777270] Bluetooth: hci1: LMP ver=6 subver=22bb; manufacturer=10
[ 4.778167] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=0810
[ 4.778170] Bluetooth: hci0: LMP ver=6 subver=1512; manufacturer=10
[ 4.778172] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once…
[ 5.094763] nouveau 0000:01:00.0: pmu: firmware unavailable
[ 5.110265] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[ 5.110271] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 5.110274] Bluetooth: hci0: HCI Set Event Filter command not supported.
[ 5.385747] si2168 19-0064: firmware version: B 4.0.2
[ 5.414112] si2168 19-0066: firmware version: B 4.0.2
[ 5.770763] si2168 25-0064: firmware version: B 4.0.2
[ 5.781760] si2168 25-0066: firmware version: B 4.0.2
[ 6.186398] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.186403] Bluetooth: BNEP filters: protocol multicast
[ 6.186406] Bluetooth: BNEP socket layer initialized
[ 6.192657] Bluetooth: MGMT ver 1.22
[ 6.192709] Bluetooth: MGMT ver 1.22
[ 10.259105] si2168 19-0066: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 10.709309] si2168 19-0066: firmware version: B 4.0.4
[ 10.734881] si2168 25-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 11.191004] si2168 25-0064: firmware version: B 4.0.4
[ 11.742086] si2168 25-0066: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 12.197211] si2168 25-0066: firmware version: B 4.0.4
[ 12.743064] si2168 19-0064: downloading firmware from file ‘dvb-demod-si2168-b40-01.fw’
[ 13.193203] si2168 19-0064: firmware version: B 4.0.4
[ 18.969861] Bluetooth: RFCOMM TTY layer initialized
[ 18.969867] Bluetooth: RFCOMM socket layer initialized
[ 18.969871] Bluetooth: RFCOMM ver 1.11
6.8.0-35240528-generic
tony@linuxmint:~$
May want to try a 6.12 kernel from Index of /mainline and see if it is fixed. These CSR Bluetooth cause the Linux devs major headaches as there are a number of fakes and they all use the same USB ID
I think I have found a solution. My HTPC setup is in the loft with an HDMI and ethernet/usb/remote control cables into my lounge.
I discovered at some stage I’d stuck a USB btooth dongle in the back of the computer when the internal onboard btooth packed up. I also had one in the usb hub in the lounge, so doubling up on btooth dongles. I have removed one and it now works. What I can’t understand is why it works on windows and never had an issue on Jammy??? Oh well one of life’s little mysteries.
I have just found a work-around. I installed qpgraph and created a startup script to enable a combined sink then a desktop icon to instigate qgraph when I connect my btooth headphones. So far works flawlessly.
This is to enable the lovely Jane to listen quietly to the home theatre as she doesn’t like it loud and deaf old me to listen on my headphones. Happy household at last!
I appreciate the devs all do their thing and devote their time for nothing on all our behalf.
The annoying thing is why do the devs constantly change things that work for years with newer “solutions” that create all sorts of problems? Pulse and alsa have worked well for many years and all of a sudden they change it to pipewire and create hours and hours of end users chasing their tails with compatibility issues. The same thing with snaps and flatpacks, I could go on and on but it’s Christmas so merry one to you and yours.
So there were 2 all along, I wondered if that is why the above happened. I would guess your dmesg only shows the 22bb revision now
Yes, there we are. Thank you for your assistance.
889.656593] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb
[ 889.656597] Bluetooth: hci0: LMP ver=6 subver=22bb; manufacturer=10
[ 889.831200] Bluetooth: MGMT ver 1.22
[ 950.398658] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb
[ 950.398677] Bluetooth: hci0: LMP ver=6 subver=22bb; manufacturer=10
I’ll mark this as solved.
Cheers Tony