You are not logged in.
I just recompiled the modules in the drivers/bluetooth directory in the kernel source tree following the instructions in the wiki using the Arch Build System. After that i replaced the btusb.ko.zst with the newly compiled version followed by a depmod and a reboot.
The patch for my hardware was just changing one line in btusb.c in the mentioned directory
- { USB_DEVICE(0x8087, 0x0a2a), .driver_info = BTUSB_INTEL_COMBINED }, + { USB_DEVICE(0x8087, 0x0a2a), .driver_info = BTUSB_INTEL_COMBINED | + BTUSB_INTEL_BROKEN_INITIAL_NCMD },
Thank you !
Offline
Does that mean it works for you? If so, think about switching to the patches that lokjo linked in #24 because these patches will (hopefully) be part of the kernel source tree in the near future, so no patches on our side will be needed any more. They work for me, too.
Offline
commit has been merged into mainline for 5.17
https://git.kernel.org/pub/scm/linux/ke … 5b4c4c227b
It is marked for fixes so should be part of a future stable release.
Offline
Hello,
new to this channel here.
I just upgraded my system today, which included a new version of linux-firmware (20211027.1d00989-1 -> 20211216.f682ecb-1). And bluetooth stopped working.
The first sign I had was the command
bluetoothctl power on
Failed to set power on: org.bluez.Error.Failed
Looking in journalctl I see a lot of messages like so:
dbus-daemon[485]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)"
error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.129" (uid=0 pid=404051 comm="/usr/lib/bluetooth/bluetoothd ")
[...]
kernel: Bluetooth: hci0: QCA: Discarding other packets
[...]
kernel: Bluetooth: hci0: QCA memdump unexpected packet 32
Other error message in journalctl related to powering bluetooth on:
bluetoothd[28962]: Failed to set mode: Failed (0x03)
A bit of background:
I run a stock kernel 5.15.13-arch1-1
I have several packages installed related to bluetooth: bluez 5.63-1, bluez-libs 5.63-1, bluez-utils 5.63-1, pulseaudio-bluetooth 15.0-1
The machine is a dell xps 9700 with a Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01)
Any suggestion how to fix this?
Thank you
PS Other bits and pieces...
root@taipan ~ [1]# lsmod | grep -i bt
btqca 24576 1 hci_uart
btrtl 28672 1 hci_uart
btbcm 24576 1 hci_uart
btintel 45056 1 hci_uart
bluetooth 749568 34 btrtl,btqca,btintel,hci_uart,btbcm,bnep,rfcomm
Offline
Bluetooth not working for me either, Asus PN51 at Linux 5.15.13-arch1-1 (x86_64).
Not quite sure from the previous comments if if should already work or not...
Offline
Fix is queued for 5.16.1 and 5.15.15
https://git.kernel.org/pub/scm/linux/ke … 98ecbdb92b
https://git.kernel.org/pub/scm/linux/ke … a83a12e7c0
Last edited by loqs (2022-01-13 22:18:05)
Offline
Fix is queued for 5.16.1 and 5.15.15
https://git.kernel.org/pub/scm/linux/ke … 98ecbdb92b
https://git.kernel.org/pub/scm/linux/ke … a83a12e7c0
Thanks for the heads up.
Offline
With todays update to 5.16.1-arch1-1 it works again for me without any patches
Offline
The issue persists for me even after the upgrade. Didn't try 5.15.15, since the only way for me to use bluetooth devices is holding linux-lts at 5.10...
$ uname -r
5.16.1-arch1-1
# dmesg | grep -i bluetooth
[ 2.462815] Bluetooth: Core ver 2.22
[ 2.462837] NET: Registered PF_BLUETOOTH protocol family
[ 2.462839] Bluetooth: HCI device and connection manager initialized
[ 2.462844] Bluetooth: HCI socket layer initialized
[ 2.462846] Bluetooth: L2CAP socket layer initialized
[ 2.462850] Bluetooth: SCO socket layer initialized
[ 3.782199] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.782202] Bluetooth: BNEP filters: protocol multicast
[ 3.782206] Bluetooth: BNEP socket layer initialized
[ 4.720015] Bluetooth: hci0: command 0xfc05 tx timeout
[ 4.720030] Bluetooth: hci0: Reading Intel version command failed (-110)
Offline
.16.1 kernel did not resolve it for me. (bluetooth has worked before)
# rfkill list
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
$ lsmod | grep btusb
btusb 65536 0
btrtl 28672 1 btusb
btbcm 24576 1 btusb
btintel 45056 1 btusb
bluetooth 770048 13 btrtl,btintel,btbcm,bnep,btusb
# systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2022-01-20 18:57:39 EET; 8min ago
Docs: man:bluetoothd(8)
Main PID: 4751 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 76428)
Memory: 1.9M
CPU: 17ms
CGroup: /system.slice/bluetooth.service
└─4751 /usr/lib/bluetooth/bluetoothd
jan 20 18:57:39 pn51 systemd[1]: Starting Bluetooth service...
jan 20 18:57:39 pn51 bluetoothd[4751]: Bluetooth daemon 5.63
jan 20 18:57:39 pn51 systemd[1]: Started Bluetooth service.
jan 20 18:57:39 pn51 bluetoothd[4751]: Starting SDP server
jan 20 18:57:39 pn51 bluetoothd[4751]: Bluetooth management interface 1.21 initialized
# dmesg | grep -i bluetooth
[ 1.913824] Bluetooth: Core ver 2.22
[ 1.913843] NET: Registered PF_BLUETOOTH protocol family
[ 1.913844] Bluetooth: HCI device and connection manager initialized
[ 1.913849] Bluetooth: HCI socket layer initialized
[ 1.913851] Bluetooth: L2CAP socket layer initialized
[ 1.913852] Bluetooth: SCO socket layer initialized
[ 22.683113] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 22.683124] Bluetooth: BNEP filters: protocol multicast
[ 22.683132] Bluetooth: BNEP socket layer initialized
[ 745.966620] audit: type=1131 audit(1642698582.955:173): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 745.977677] audit: type=1130 audit(1642698582.965:176): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 758.638249] audit: type=1131 audit(1642698595.625:195): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 758.648701] audit: type=1130 audit(1642698595.638:198): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
# bluetoothctl devices
No default controller available
bluez and bluez-utils installed. Also tried bluez-utils-compat and bluez-hid2hci (since the dongle is for Logitech MX Master 3 and MX Keys).
Offline
yallu you seem to not have the same error messages, not sure if your problem is related to the one in this thread.
scaramanga, in the fix commit they say they applied it to three devices 8087:07dc, 8087:0a2a and 8087:0aa7. Do you have one of those three devices or something else? (lsusb shows these ids)
Offline
scaramanga, in the fix commit they say they applied it to three devices 8087:07dc, 8087:0a2a and 8087:0aa7. Do you have one of those three devices or something else? (lsusb shows these ids)
That explains it. I have 8087:0029 Intel Corp. AX200 Bluetooth (integrated into the mainboard).
Offline
That explains it. I have 8087:0029 Intel Corp. AX200 Bluetooth (integrated into the mainboard).
I guess you could try applying the fix manually like lula described in post 23, i.e. add for your card the BTUSB_INTEL_BROKEN_INITIAL_NCMD flag, then compile and run it. If it works you can try to ask them in the bluetooth mailing list to apply it to the kernel.
Offline
I did reboot a few times after upgrading to 5.16.2 just now with bluetooth seeming to work. If the problem appears again I'll try to apply the patch though.
Offline
yallu you seem to not have the same error messages, not sure if your problem is related to the one in this thread.
Sure, in the end my problem was solved either by .16.2 or by going to BIOS, disabling Bluetooth controller, rebooting, going to BIOS, enabling Bluetooth controller, booting up. Not sure which one...
Offline
So my problem reappeared and applying the patch that worked for 8087:0a2a to my device unfortunately did not work, the errors just change. Would the mailing list still be the right place to report this issue? Never done something like that before.
Offline
Hi. same problem here with kernel 5.16.2-arch1-1.
lsusb output: Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
output of systemctl status bluetooth: http://ix.io/3NvV
Offline
Interestingly now the AX200 does not even work with the 5.10 LTS Kernel anymore.
edit: a cold boot did make it work again, oh wow
Last edited by alxndr13 (2022-01-27 08:36:47)
Offline
Interestingly now the AX200 does not even work with the 5.10 LTS Kernel anymore.
edit: a cold boot did make it work again, oh wow
If I boot 5.10 first and then reboot into mainline it also works (despite some error messages) and vice versa. It seems reproducable if I turn off power for a few minutes, though.
Offline
I would suggest you to find the exact pattern how to reproduce your errors and also try to bisect the kernel to see exactly at which kernel commit the problems start (for me it was the commit 83f2dafe2a62). Then you can report all of that to the linux-bluetooth and regressions mailing lists.
For example for me it was also complicated that depending on if it was a cold start, first reboot or second reboot into a kernel version, and also depending on which version I was running before, I would either get or not get the errors.
Offline
My system has a Mini PCIe AX200 card, and I'm having the same issue w/ linux-lts 5.15.18-1-lts and linux 5.16.3.arch1-1. No issues were found on linux-lts 5.15.16-1.
The new kernels failed with the same timeout error. Cold boot, reboot, suspend, etc have no effect at all. It just doesn't work.
The log when BT worked:
Jan 31 03:43:11 sori kernel: Bluetooth: Core ver 2.22
Jan 31 03:43:11 sori kernel: Bluetooth: HCI device and connection manager initialized
Jan 31 03:43:11 sori kernel: Bluetooth: HCI socket layer initialized
Jan 31 03:43:11 sori kernel: Bluetooth: L2CAP socket layer initialized
Jan 31 03:43:11 sori kernel: Bluetooth: SCO socket layer initialized
Jan 31 03:43:12 sori kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Jan 31 03:43:12 sori kernel: Bluetooth: hci0: Boot Address: 0x24800
Jan 31 03:43:12 sori kernel: Bluetooth: hci0: Firmware Version: 235-51.21
Jan 31 03:43:12 sori kernel: Bluetooth: hci0: Firmware already loaded
...
The log when BT failed:
Jan 31 03:34:30 sori kernel: Bluetooth: Core ver 2.22
Jan 31 03:34:30 sori kernel: Bluetooth: HCI device and connection manager initialized
Jan 31 03:34:30 sori kernel: Bluetooth: HCI socket layer initialized
Jan 31 03:34:30 sori kernel: Bluetooth: L2CAP socket layer initialized
Jan 31 03:34:30 sori kernel: Bluetooth: SCO socket layer initialized
Jan 31 03:34:32 sori kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 31 03:34:32 sori kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
...
There's a related bug report on kernel.org, but the reports are quite inconsistent about which version introduced the bug.
Offline
My mother board is an asus ROG Strix B550-E GAMING and my kernel is 5.16.11-arch1-1 x86_64, and I'm having the same issue too.
dmesg -T | grep Bluetooth:
[Mon Feb 28 09:02:11 2022] Bluetooth: Core ver 2.22
[Mon Feb 28 09:02:11 2022] Bluetooth: HCI device and connection manager initialized
[Mon Feb 28 09:02:11 2022] Bluetooth: HCI socket layer initialized
[Mon Feb 28 09:02:11 2022] Bluetooth: L2CAP socket layer initialized
[Mon Feb 28 09:02:11 2022] Bluetooth: SCO socket layer initialized
[Mon Feb 28 09:02:11 2022] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[Mon Feb 28 09:02:11 2022] Bluetooth: BNEP filters: protocol multicast
[Mon Feb 28 09:02:11 2022] Bluetooth: BNEP socket layer initialized
[Mon Feb 28 09:02:13 2022] Bluetooth: hci0: Reading Intel version command failed (-110)
[Mon Feb 28 09:02:13 2022] Bluetooth: hci0: command 0xfc05 tx timeout
Offline
I'm on Gigabyte Aorus X570 with the AX200 Wifi6 and Bluetooth
Havent used the card previously but tried to connect to BT headphones.
Latest pkg from pacman: I get null errors in bluetooth service when trying to connect.
Tried bluez-git and this fixes the the null errors however.....
Sennheiser 550 => Command Timeout
Sony FW-1000MX4 => Fails to connect but after couple of retries its successfull however it does not list as a device for pipewire/pulse se errors bellow..
feb 28 23:21:26 Maxwell bluetoothd[51060]: profiles/audio/avdtp.c:cancel_request() Open: Connection timed out (110)
feb 28 23:21:26 Maxwell bluetoothd[51060]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
feb 28 23:21:27 Maxwell dbus-daemon[794]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.137" (uid=1000 pid=1531 comm="/usr/bin/wireplumber ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.2209" (uid=0 pid=51060 comm="/usr/lib/bluetooth/bluetoothd ")
feb 28 23:22:08 Maxwell bluetoothd[51060]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to F8:4E:17:4C:5F:30: Connection refused (111)
It's driving me crazy....
Last edited by Commander (2022-02-28 22:30:04)
Offline
The issues are not fixed as of 5.16.11, however I kinda lost motivation to dissect which commit actually made this occur, so I don't think I can submit a helpful bug report at the time being. It definitely is quite frustrating.
Offline
On 5.16.13 it seems to be a bit improved. The headphones this time said they connected but after a while disconnected. Took about 1minute or more before they even said connected...
mar 10 08:54:51 Maxwell bluetoothd[125644]: src/device.c:search_cb() F8:4E:17:4C:5F:30: error updating services: Connection refused (111)
mar 10 08:54:51 Maxwell bluetoothd[125644]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to F8:4E:17:4C:5F:30: Connection refused (111)
mar 10 08:54:13 Maxwell bluetoothd[125644]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
mar 10 08:53:42 Maxwell bluetoothd[125644]: profiles/audio/avdtp.c:cancel_request() Abort: Connection timed out (110)
mar 10 08:53:40 Maxwell bluetoothd[125644]: profiles/audio/avdtp.c:cancel_request() Start: Connection timed out (110)
mar 10 08:53:15 Maxwell bluetoothd[125644]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to F8:4E:17:4C:5F:30: Connection refused (111)
mar 10 08:52:42 Maxwell bluetoothd[125644]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/faststream_duplex
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/faststream
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/aptx_ll_0
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/aptx_ll_1
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/sbc_xq
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/sbc_xq
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/sbc
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSink/sbc
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/aac
mar 10 08:51:28 Maxwell bluetoothd[125644]: Endpoint registered: sender=:1.56 path=/MediaEndpoint/A2DPSource/aptx
Last edited by Commander (2022-03-11 08:22:47)
Offline