Bluetooth issues (ongoing)
Hi, On my Acer Travelmate connected to a Dell Dock, Bluetooth isn't working after boot. I need to call rfkill and do a bluetooth service restart, then it works flawlessly. This is after a fresh boot: mfeilner@maldacena:~> bluetoothctl Agent registered [bluetooth]# list Controller F4:B3:01:49:51:46 maldacena.feilner-it.net [default] [bluetooth]# devices Device 0C:A6:94:D1:77:5D Büro Regensburg (...) [bluetooth]# connect 0C:A6:94:D1:77:5D Attempting to connect to 0C:A6:94:D1:77:5D [bluetooth]# power on Changing power on succeeded [bluetooth]# connect 0C:A6:94:D1:77:5D Attempting to connect to 0C:A6:94:D1:77:5D Failed to connect: org.bluez.Error.InProgress br-connection-busy [bluetooth]# power off Failed to set power off: org.bluez.Error.Busy Failed to connect: org.bluez.Error.Failed br-connection-unknown Failed to set power off: org.bluez.Error.Failed [bluetooth]# power off Failed to set power off: org.bluez.Error.Failed [bluetooth]# exit mfeilner@maldacena:~> The "connect" commands fail, and after calling them, "power off" will also fail. (Yes, pairing has been successful) I have a solution, but I would love to know the root of the problem and help others, maybe. Here's my little script that fixes it: #!/bin/bash sudo rfkill unblock bluetooth sudo service bluetooth restart sleep 3s bluetoothctl power on After that, Bluetooth works as expected. The script only needs to be called once after boot - I automated that as a start script. I have no idea what goes wrong upon initialization of bluetooth on boot, but only if I call rfkill and restart the service, bluetooth connection to my stereo can be established. I have seen this behaviour also on my media center, the start script fixed it there, too. Any ideas? How can I help? In the meantime, I check the usual pages for a bug related to this. It's been like this for months... -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Sustainable Open Source Strategy, Networking, Politics, Journalism Knowledge Management, Rubber Ducks, Trainings, Workshops, Documentation https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) https://mastodon.cloud/@mfeilner https://mastodon.social/@FeilnerIT PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Mastodon, Matrix, Jabber, ...
On 2023-02-17 11:33, Markus Feilner wrote:
I have no idea what goes wrong upon initialization of bluetooth on boot, but only if I call rfkill and restart the service, bluetooth connection to my stereo can be established. I have seen this behaviour also on my media center, the start script fixed it there, too.
You should study the logs. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am Freitag, 17. Februar 2023, 11:45:56 CET schrieb Carlos E. R.:
On 2023-02-17 11:33, Markus Feilner wrote:
I have no idea what goes wrong upon initialization of bluetooth on boot, but only if I call rfkill and restart the service, bluetooth connection to my stereo can be established. I have seen this behaviour also on my media center, the start script fixed it there, too.
You should study the logs.
Oh, I did. Sorry that I forgot to mention that. Only weird line in dmesg are these: [ 23.594878] Bluetooth: hci0: Opcode 0x 408 failed: -110 [ 23.594884] Bluetooth: hci0: command 0x0408 tx timeout Sometimes I also had to remove the modules with sudo modprobe -r btusb; sudo modprobe -r btintel; sudo modprobe btusb; sudo modprobe btintel and then a sudo service bluetooth restart which results in this: [ 9540.509328] usbcore: deregistering interface driver btusb [ 9540.941896] usbcore: registered new interface driver btusb [ 9541.003728] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [ 9541.003783] Bluetooth: hci0: Boot Address: 0x24800 [ 9541.003785] Bluetooth: hci0: Firmware Version: 15-45.22 [ 9541.003786] Bluetooth: hci0: Firmware already loaded [ 9541.173980] Bluetooth: MGMT ver 1.22 [ 9541.227840] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0) and then Bluetooth works. I am clueless. In rare cases, I had to do the modprobe and service restart and rfkill several times until the hardware did what I desired. But as I said, I got a "works for me" solution, but I guess there might be more to that - since it appeared on several devices. Maybe this mail is helpful to someone ...
Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
-- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Sustainable Open Source Strategy, Networking, Politics, Journalism Knowledge Management, Rubber Ducks, Trainings, Workshops, Documentation https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) https://mastodon.cloud/@mfeilner https://mastodon.social/@FeilnerIT PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Mastodon, Matrix, Jabber, ...
Oh sorry, I forgot this info, too: I am running Tumbleweed with kernel 6.1.10-1 and KDE Plasma (which obviously isn't related, I assume). Current bluetooth version is 5.66, acc. to bluetoothctl. mfeilner@maldacena:~> bluetoothctl Agent registered [Büro Regensburg]# info Device 0C:A6:94:D1:77:5D (public) Name: PhilipsBT Alias: Büro Regensburg Class: 0x00240404 Icon: audio-headset Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb) [Büro Regensburg]# show Controller F4:B3:01:49:51:46 (public) Name: maldacena.feilner-it.net Alias: maldacena.feilner-it.net Class: 0x006c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0542 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0c (12) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded [Büro Regensburg]# maldacena:/home/mfeilner # hwinfo --bluetooth 02: USB 00.0: 11500 Bluetooth Device [Created at usb.122] Unique ID: CiZ2.qmlouffvxgF Parent ID: uIhY.Md0RKo+2xQF SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-3/3-3:1.0 SysFS BusID: 3-3:1.0 Hardware Class: bluetooth Model: "Intel AX200 Bluetooth" Hotplug: USB Vendor: usb 0x8087 "Intel Corp." Device: usb 0x0029 "AX200 Bluetooth" Revision: "0.01" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v8087p0029d0001dcE0dsc01dp01icE0isc01ip01in00" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #10 (Hub) Anything else I missed? Am Freitag, 17. Februar 2023, 12:16:51 CET schrieb Markus Feilner:
Am Freitag, 17. Februar 2023, 11:45:56 CET schrieb Carlos E. R.:
On 2023-02-17 11:33, Markus Feilner wrote:
I have no idea what goes wrong upon initialization of bluetooth on boot, but
only if I call rfkill and restart the service, bluetooth connection
to my stereo can be established. I have seen this behaviour also on my media center, the start script fixed it there, too.
You should study the logs.
Oh, I did. Sorry that I forgot to mention that. Only weird line in dmesg are these:
[ 23.594878] Bluetooth: hci0: Opcode 0x 408 failed: -110 [ 23.594884] Bluetooth: hci0: command 0x0408 tx timeout
Sometimes I also had to remove the modules with
sudo modprobe -r btusb; sudo modprobe -r btintel; sudo modprobe btusb; sudo modprobe btintel and then a sudo service bluetooth restart
which results in this: [ 9540.509328] usbcore: deregistering interface driver btusb [ 9540.941896] usbcore: registered new interface driver btusb [ 9541.003728] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [ 9541.003783] Bluetooth: hci0: Boot Address: 0x24800 [ 9541.003785] Bluetooth: hci0: Firmware Version: 15-45.22 [ 9541.003786] Bluetooth: hci0: Firmware already loaded [ 9541.173980] Bluetooth: MGMT ver 1.22 [ 9541.227840] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
and then Bluetooth works. I am clueless. In rare cases, I had to do the modprobe and service restart and rfkill several times until the hardware did what I desired.
But as I said, I got a "works for me" solution, but I guess there might be more to that - since it appeared on several devices.
Maybe this mail is helpful to someone ...
Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
-- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Sustainable Open Source Strategy, Networking, Politics, Journalism Knowledge Management, Rubber Ducks, Trainings, Workshops, Documentation https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) https://mastodon.cloud/@mfeilner https://mastodon.social/@FeilnerIT PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Mastodon, Matrix, Jabber, ...
On Friday, 17 February 2023 19:16:51 +08 Markus Feilner wrote:
Maybe this mail is helpful to someone ...
Oh it is. Bluetooth on my desktop running off the PCIe WiFi card sometimes works and sometimes doesn't. I just had a setup that didn't rely on bluetooth until I spotted the LDAC codec was supported in the audio settings recently and wanted to try it out. Thanks for this workaround!
Am Montag, 20. Februar 2023, 12:03:15 CET schrieb Martin Wilck:
On Fri, 2023-02-17 at 11:33 +0100, Markus Feilner wrote:
In the meantime, I check the usual pages for a bug related to this. It's been like this for months...
Have you openened a bug?
Martin Nope,
a) I have a workaround and b) I am unsure if the problem is common or just related to my setup(s). I don't want to use anybody else's time if the problem doesn't appear elsewhere... -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Sustainable Open Source Strategy, Networking, Politics, Journalism Knowledge Management, Rubber Ducks, Trainings, Workshops, Documentation https://www.feilner-it.net, 93059 Regensburg Wöhrdstr. 10, +49 170 302 7092 (+Signal) https://mastodon.cloud/@mfeilner https://mastodon.social/@FeilnerIT PGP: 40A3C306F96133067C11CFD9A958A906268C9F0A http://www.feilner-it.net/files/MFpub.asc Xing: http://www.xing.com/profile/Markus_Feilner LinkedIn: https://www.linkedin.com/in/markusfeilner @mfeilner: Mastodon, Matrix, Jabber, ...
On 2023-02-20 19:20, Markus Feilner wrote:
Am Montag, 20. Februar 2023, 12:03:15 CET schrieb Martin Wilck:
On Fri, 2023-02-17 at 11:33 +0100, Markus Feilner wrote:
In the meantime, I check the usual pages for a bug related to this. It's been like this for months...
Have you openened a bug?
Martin Nope,
a) I have a workaround and b) I am unsure if the problem is common or just related to my setup(s).
I don't want to use anybody else's time if the problem doesn't appear elsewhere...
I'm not sure if it's the same problem but last year (there was an email thread about it) I had problems with pipewire and a race condition between pulseaudio and pipewire for my bluetooth audio. Since I didn't want pipewire at all, I turned it off and blacklisted pipewire. Before that, I solved the problem like this: As normal user: systemctl --user disable --now pipewire.{socket,service} Check: systemctl --user status pipewire.service systemctl --user status pipewire.socket -- /bengan
On Mon, 2023-02-20 at 19:20 +0100, Markus Feilner wrote:
Am Montag, 20. Februar 2023, 12:03:15 CET schrieb Martin Wilck:
On Fri, 2023-02-17 at 11:33 +0100, Markus Feilner wrote:
In the meantime, I check the usual pages for a bug related to this. It's been like this for months...
Have you openened a bug?
Martin Nope,
a) I have a workaround and b) I am unsure if the problem is common or just related to my setup(s).
I don't want to use anybody else's time if the problem doesn't appear elsewhere...
I don't think you'd be wasting time. Things like this need to be documented. I personally have problems with Bluetooth all the time on TW. Unlike you, I haven't yet figured out workarounds, or got to the point where I'd be able to write a meaningful bug report. My current "workaround" is to just not use TW for Bluetooth. I use Leap or Android to connect my BT devices. Stop whining here. Regards, Martin
On 2023-02-21 06:50, Martin Wilck wrote:
I personally have problems with Bluetooth all the time on TW. Unlike you, I haven't yet figured out workarounds, or got to the point where I'd be able to write a meaningful bug report.
Hi Martin, As a Tumbleweed user, I feel my contribution is to report bugs. I do it when I can. Sometimes it will take me months to report a bug. :\ When I'm unclear on where to begin, my general strategy is to look at the bugs database[1]. I search using some high-level keywords (e.g. Bluetooth tumbleweed) and scan the bug hits. Based on what I see, I may iterate bug searches with more and more keywords. What I look for are those bugs that potentially resemble my issue and where there is some engineering interaction. Specifically, what I'm looking for are the data being gathered and how it is being gathered. If I'm lucky, I find a bug that is tracking my issue. It generally takes about 10 - 15 minutes to do the above. Sometimes I'll go to the upstream project to try to glean additional debug methods. That adds a bit more time. But not significant. Once I have the information to gather debug information, I model a bug report against a bug that's similar to my issue. Noting the *Product, Component, etc.* What can take the most amount of time is writing a clear bug report. I sometimes use an external editor to compose the message and when satisfied, I copy-and-paste the results. Sometimes gathering the debug data can take a while. I figure the above time is a modest investment. Cheers! _*References *_ 1 - https://bugzilla.opensuse.org --- Pablo Sanchez - Blueoak Database Engineering Ph: 819.459.1926 iNum: 883.5100.0990.1054
On Tue, 2023-02-21 at 07:43 -0500, Pablo Sanchez wrote:
On 2023-02-21 06:50, Martin Wilck wrote:
I personally have problems with Bluetooth all the time on TW. Unlike you, I haven't yet figured out workarounds, or got to the point where I'd be able to write a meaningful bug report.
Hi Martin,
As a Tumbleweed user, I feel my contribution is to report bugs. I do it when I can. Sometimes it will take me months to report a bug. :\ ...
I know that quite well. My contribution (being a SUSE employee) is to both report and fix bugs, and I do. A bugzilla.suse.com search for bugs reported by "wilck" turns up >700 bugs, over a time span of 20+ years. Still, I can't write (good) bug reports for every problem I encounter. I consider the pros and cons in every case. Bluetooth on TW (in particular, bluetooth sound) is an area which I've basically given up. I am not proud of that; you can rightfully criticize me for it. But I feel I just can't be active in every area. Thanks, Martin
participants (6)
-
Bengt Gördén -
Carlos E. R. -
Chan Ju Ping -
Markus Feilner -
Martin Wilck -
Pablo Sanchez