Qualcom Bluetooth firmware

business_kid · 03-09-2021, 09:14 AM

Bluetooth has worked on this box at slow speed and frankly wasn't worth the effort. Now I think I know why. From 'lsusb'

Code:

lsusb |grep -i Bluetooth
Bus 001 Device 015: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 Bluetooth 4.0

And dmesg

Code:

[    8.182976] usb 2-3: new high-speed USB device number 4 using xhci_hcd
[    8.211976] usb 1-1.2: new full-speed USB device number 4 using ehci-pci
[    8.292120] usb 1-1.2: New USB device found, idVendor=0cf3, idProduct=3004, bcdDevice= 0.02
[    8.292123] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    8.292126] usb 1-1.2: Product: Bluetooth USB Host Controller
[    8.292127] usb 1-1.2: Manufacturer: Atheros Communications
[    8.292129] usb 1-1.2: SerialNumber: Alaska Day 2006

… And further down …

[    8.658577] usbcore: registered new interface driver btusb
[    8.661930] usbcore: registered new interface driver ath3k
[    8.662565] Bluetooth: hci0: don't support firmware rome 0x1020200

That AR3012 should be on usb-3.0,IIRC and not usb-2.0. It should be doing usb-4.0, and not dawdling along. My versions are kernel-firmware-20210208_b79d239-noarch-1, and kernel-generic 5.10.15 from the 2021-02-11 iso.

Is this a kernel issue?

jamison20000e · 03-09-2021, 09:25 AM

Hi.

Did you look through the bug reports from searching that [B]part?[/B]

business_kid · 03-09-2021, 10:47 AM

No, to be honest. It's from 2012, so they're thin on the ground. I was hoping for a firmware update; But why it's picking the firmware so late I don't know - like the firmware is an afterthought, nearly 50 lines down.

I know what happens with a kernel bug - you have to grab & compile the bleeding edge version, apply patches, insert firmware whatever, and there's too much going on for others at home right now for me to go near any of that ATM.

business_kid · 03-10-2021, 10:08 AM

Well it wasn't me, it appears to have been a kernel bug.

I found this https://bugzilla.kernel.org/show_bug.cgi?id=210681

If Slackware is implementing this fix dated 2021-03-02, I'll wait for an updated kernel. Otherwise, if I get time I'll have a go myself.

EDIT: Apparently it was fixed in kernel-5.11.2