FS#69110 - [linux] 5.10.2 Bluetooth: hci0: don't support firmware rome 0x31010000 Qualcomm Atheros AR9462

Attached to Project: Arch Linux
Opened by Sourav Das (souravdas142) - Friday, 25 December 2020, 17:01 GMT
Last edited by Christian Heusel (gromit) - Tuesday, 01 August 2023, 13:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 12
Private No

Details

Description:
I have custom compile Linux 5.10.2 with a patch irrelevant to bluetooth without modifing anything else. But I am unable to manage to power on the bluetooth controller from bluetoothctl. when i try to power on the controller, a message shown "No default controller available". from journalctl log I got a error "Bluetooth: hci0: don't support firmware rome 0x31010000". There is no problem with Linux 5.9.14 though.

Additional info:
* package version(s) Linux 5.10.2, bluez-5.55-1
* config and/or log files etc. see journalctl log and bluetooth device log below.
* link to upstream bug report, if any : a bug report already has been filed at : https://www.spinics.net/lists/linux-bluetooth/msg89659.html and https://bugzilla.kernel.org/show_bug.cgi?id=210681 from the comment(https://bugzilla.kernel.org/show_bug.cgi?id=210681#c6) of the bug report, it is suggested that revert the commit to its(drivers/bluetooth/btusb.c file) previous and compile the kernel again fix the issue.

Steps to reproduce:
it seems to problem with Qualcomm Atheros bluetooth chipset. so with any chipset with Qualcomm Atheros, you can reproduce the error. in bluetoothctl interactive shell just turn the power on the bluetooth controller with "power on" you can see the problem "No default controller available".
   bluetooth (9.2 KiB)
   journalLog (172 KiB)
This task depends upon

Closed by  Christian Heusel (gromit)
Tuesday, 01 August 2023, 13:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux 5.11.arch2-1
Comment by KriK (krik) - Sunday, 27 December 2020, 20:29 GMT
Same with AR3012 and 5.10.3
Comment by Sourav Das (souravdas142) - Monday, 28 December 2020, 13:26 GMT
did you test compiling the kernel by reverting back drivers/bluetooth/btusb.c file to previous commit(what upstream bug reporter suggests)? did everything work? sorry i can't test it now that's why i am asking you.
Comment by Charles Bowman (cbowman57) - Monday, 28 December 2020, 18:00 GMT
DELL Inspiron24 Model 3455
Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

Same Bluetooth problem since 5.10.1

*since lspci didn't show a Bluetooth entry I'm assuming that it's connected to the network controller
Comment by Charles Bowman (cbowman57) - Friday, 01 January 2021, 00:35 GMT
I built 5.10.4 after making the addition in this patch that I found on the kernel bug tracker and my Bluetooth now works again.

Not sure if this is an actual fix or a workaround but I would really like to see it applied to 5.10.5 and future kernels until it's no longer needed.
   firmware_rome_error.patch (0.4 KiB)
Comment by Dmitryi (RusWolf) - Sunday, 03 January 2021, 10:53 GMT
04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)

[wolf@wolf-nout ~]$ sudo dmesg | grep Bluetooth
[sudo] пароль для wolf:
[ 4.888904] Bluetooth: Core ver 2.22
[ 4.888942] Bluetooth: HCI device and connection manager initialized
[ 4.888951] Bluetooth: HCI socket layer initialized
[ 4.888956] Bluetooth: L2CAP socket layer initialized
[ 4.888967] Bluetooth: SCO socket layer initialized
[ 5.759728] Bluetooth: hci0: don't support firmware rome 0x11020000
[ 5.862415] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.862420] Bluetooth: BNEP filters: protocol multicast
[ 5.862428] Bluetooth: BNEP socket layer initialized
[wolf@wolf-nout ~]$ uname -a
Linux wolf-nout 5.10.4-arch2-1 #1 SMP PREEMPT Fri, 01 Jan 2021 05:29:53 +0000 x86_64 GNU/Linux
Comment by Serge Popov (Serge92) - Sunday, 03 January 2021, 21:32 GMT
Same with Qualcomm Atheros AR9485 Kernel 5.10.2-2 Manjaro, notebook Samsung np350v5c
Comment by Andreas Gerlich (agl) - Monday, 11 January 2021, 19:47 GMT
ag@specht
---------
OS: Arch Linux x86_64
Host: DELL Vostro 3560, BIOS-Version A20
Kernel: 5.10.6-arch1-1
Uptime: 2 mins
Packages: 884 (pacman)
Shell: bash 5.1.4
Resolution: 1920x1080
DE: Cinnamon 4.8.5
WM: Mutter (Muffin)
WM Theme: cinnamon (Adwaita)
Theme: Adwaita [GTK2/3]
Icons: Adwaita [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i7-3612QM (8) @ 3.100GHz
GPU: AMD ATI Radeon HD 7500M/7600M Series
GPU: Intel 3rd Gen Core processor Graphics Controller
Memory: 773MiB / 7823MiB

[ag@specht ~]$ lspci | grep -i Network
08:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
[ag@specht ~]$

ag@specht ~]$ uname -a
Linux specht 5.10.6-arch1-1 #1 SMP PREEMPT Sat, 09 Jan 2021 18:22:35 +0000 x86_64 GNU/Linux
[ag@specht ~]$ sudo dmesg | grep -i bluetooth
[ 1.523703] usb 2-1.5: Product: Bluetooth USB Host Controller
[ 2.993380] Bluetooth: Core ver 2.22
[ 2.993404] Bluetooth: HCI device and connection manager initialized
[ 2.993408] Bluetooth: HCI socket layer initialized
[ 2.993411] Bluetooth: L2CAP socket layer initialized
[ 2.993415] Bluetooth: SCO socket layer initialized
[ 3.133992] Bluetooth: hci0: don't support firmware rome 0x1020200 <---------------
[ 3.267907] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.267909] Bluetooth: BNEP filters: protocol multicast
[ 3.267913] Bluetooth: BNEP socket layer initialized
[ag@specht ~]$

Here is the error "hci0: don't support firmware rome 0x1020200"!
(Bluetooth-Daemon (bluetoothd) is running)

With the LTS-Kernel (5.4.88-1-lts) bluetooth works well:

ag@specht ~]$ uname -a
Linux specht 5.4.88-1-lts #1 SMP Sat, 09 Jan 2021 14:02:47 +0000 x86_64 GNU/Linux
[ag@specht ~]$ sudo dmesg | grep -i bluetooth
[sudo] Passwort für ag:
[ 2.280682] usb 3-1.5: Product: Bluetooth USB Host Controller
[ 4.063050] Bluetooth: Core ver 2.22
[ 4.063074] Bluetooth: HCI device and connection manager initialized
[ 4.063078] Bluetooth: HCI socket layer initialized
[ 4.063080] Bluetooth: L2CAP socket layer initialized
[ 4.063084] Bluetooth: SCO socket layer initialized
[ 5.198937] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.198941] Bluetooth: BNEP filters: protocol multicast
[ 5.198950] Bluetooth: BNEP socket layer initialized
[ 15.918602] Bluetooth: RFCOMM TTY layer initialized
[ 15.918609] Bluetooth: RFCOMM socket layer initialized
[ 15.918614] Bluetooth: RFCOMM ver 1.11
[ 105.887988] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 105.887991] Bluetooth: HIDP socket layer initialized
[ 105.894197] input: Logitech Bluetooth Mouse M555b Mouse as /devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.5/3-1.5:1.0/bluetooth/hci0/hci0:21/0005:046D:B009.0001/input/input15
[ 105.894437] hid-generic 0005:046D:B009.0001: input,hidraw0: BLUETOOTH HID v4.19 Mouse [Logitech Bluetooth Mouse M555b] on 0c:84:dc:6d:8e:92
[ag@specht ~]$
Comment by Olof (olof) - Monday, 25 January 2021, 20:15 GMT
I also have this issue. Here are some debug info, if any further info is required just let me know.

Librem 15 v4


uname -a
Linux pedro 5.10.7-arch1-1 #1 SMP PREEMPT Wed, 13 Jan 2021 12:02:01 +0000 x86_64 GNU/Linux
➜ ~ sudo dmesg | grep -i bluetooth
[sudo] password for olof:
[15273.903267] audit: type=1131 audit(1611603863.376:823): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[15273.923589] audit: type=1130 audit(1611603863.396:824): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

➜ ~ sudo journalctl -b | grep Bluetooth
Jan 24 22:32:25 pedro kernel: Bluetooth: Core ver 2.22
Jan 24 22:32:25 pedro kernel: Bluetooth: HCI device and connection manager initialized
Jan 24 22:32:25 pedro kernel: Bluetooth: HCI socket layer initialized
Jan 24 22:32:25 pedro kernel: Bluetooth: L2CAP socket layer initialized
Jan 24 22:32:25 pedro kernel: Bluetooth: SCO socket layer initialized
Jan 24 22:32:25 pedro kernel: Bluetooth: hci0: don't support firmware rome 0x11020100
Jan 24 22:32:26 pedro systemd[1]: Starting Bluetooth service...
Jan 24 22:32:26 pedro bluetoothd[401]: Bluetooth daemon 5.55
Jan 24 22:32:26 pedro systemd[1]: Started Bluetooth service.
Jan 24 22:32:26 pedro systemd[1]: Reached target Bluetooth.
Jan 24 22:32:26 pedro kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 24 22:32:26 pedro kernel: Bluetooth: BNEP filters: protocol multicast
Jan 24 22:32:26 pedro kernel: Bluetooth: BNEP socket layer initialized
Jan 24 22:32:26 pedro bluetoothd[401]: Bluetooth management interface 1.18 initialized
Jan 24 22:34:37 pedro systemd[618]: Starting Bluetooth OBEX service...
Jan 24 22:34:37 pedro systemd[618]: Started Bluetooth OBEX service.

➜ ~ lspci | grep Wireless
01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
➜ ~ lsusb | grep Bluetooth
Bus 001 Device 002: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth
➜ ~
Comment by loqs (loqs) - Monday, 25 January 2021, 20:55 GMT
@olof the fix needs to come from upstream, the author of the commit that caused the regression may not be aware of the issue, see [1].

[1] https://bugzilla.kernel.org/show_bug.cgi?id=210681#c20
Comment by Brandom Rodriguez (BrandomRobor) - Thursday, 28 January 2021, 07:12 GMT
For the moment, I modified an AUR package to patch this bug. Please let me know if you have some issues with it, as it is my first PKGBUILD.

https://github.com/BrandomRobor/btusb-210681-fix
Comment by Johannes Mittendorfer (jmittendorfer) - Sunday, 31 January 2021, 09:56 GMT
Worked without problems for me
Comment by Andreas Gerlich (agl) - Monday, 01 February 2021, 20:00 GMT
Works likewise without problems with the Kernel 5.10.11-arch1-1
Comment by KriK (krik) - Tuesday, 16 February 2021, 03:55 GMT
Problem still exists even in 5.11 kernel
Comment by loqs (loqs) - Tuesday, 16 February 2021, 05:07 GMT
Upstream fix [1] should be merged during 5.12 merge window then backported to 5.11.Y stable.
Edit:
Fix has been backported to linux 5.11.arch2-1 [2].

[1] https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=234f414efd1164786269849b4fbb533d6c9cdbbf
[2] https://git.archlinux.org/linux.git/commit/?id=66b6d6c8306329134abeeb26d352f2074b2f0e1e

Loading...