bluetooth audio only connects after several tries
Hi there, am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot. I am still digging in the logfiles, but maybe these commands here are helpful for someone... Feel free to PM me if you have similar problems and / or send me links, any help is much appreciated. I know there's better ways of doing the following, esp. the sudo sections... :-) #!/bin/bash # sudo /sbin/modprobe -r btusb -r btintel sudo /sbin/modprobe btusb btintel sudo rfkill unblock bluetooth sudo service bluetooth restart sleep 3s bluetoothctl power on bluetoothctl connect 0C:A6:94:D1:77:5D sleep 3s sudo service bluetooth restart bluetoothctl connect 0C:A6:94:D1:77:5D pactl get-default-sink pactl set-default-sink bluez_sink.0C_A6_94_D1_77_5D.a2dp_sink -- 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 01/09/2023 10:28, Markus Feilner wrote:
Hi there,
am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever
I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U
Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot.
Can't speak for Tumbleweed, but on Leap following the upgrade to 15.5 it was necessary to install pipewire-pulseaudio to get my PC communicating with my bluetooth amplifier as before. I'd have thought that change already went through long ago in Tumbleweed though. Do you have that package installed? Nothing else needed configuring in my case, just a reboot and bluetooth / audio was back to normal. gumb
Am Freitag, 1. September 2023, 10:37:57 CEST schrieb gumb:
On 01/09/2023 10:28, Markus Feilner wrote:
Hi there,
am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever
I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U
Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot.
Can't speak for Tumbleweed, but on Leap following the upgrade to 15.5 it was necessary to install pipewire-pulseaudio to get my PC communicating with my bluetooth amplifier as before. I'd have thought that change already went through long ago in Tumbleweed though. Do you have that package installed?
It was not installed, I'm doing this right now... requests removal of pulseaudio – I will report – after reboot – what happened. :-)
Nothing else needed configuring in my case, just a reboot and bluetooth / audio was back to normal.
gumb
-- 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, ...
Hi there, installling pipewire- and its siblings seems to have done the needful. At least after first reboot, I could connect instantly through the Plasma widget and have sound. Will try to make it automatically connected after boot, though. Thanks a lot for helping, maybe someone finds the commands I shared useful :-) Am Freitag, 1. September 2023, 17:05:57 CEST schrieb Markus Feilner:
Am Freitag, 1. September 2023, 10:37:57 CEST schrieb gumb:
On 01/09/2023 10:28, Markus Feilner wrote:
Hi there,
am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever
I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U
Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot.
Can't speak for Tumbleweed, but on Leap following the upgrade to 15.5 it was necessary to install pipewire-pulseaudio to get my PC communicating with my bluetooth amplifier as before. I'd have thought that change already went through long ago in Tumbleweed though. Do you have that package installed?
It was not installed, I'm doing this right now... requests removal of pulseaudio – I will report – after reboot – what happened. :-)
Nothing else needed configuring in my case, just a reboot and bluetooth / audio was back to normal.
gumb
-- 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, ...
Brief update: After the following reboots, everything still works fine, but the device isnt powered on automatically and does not connect automatically. But I'm sure I will find out... Am Freitag, 1. September 2023, 17:29:52 CEST schrieb Markus Feilner:
Hi there, installling pipewire- and its siblings seems to have done the needful. At least after first reboot, I could connect instantly through the Plasma widget and have sound. Will try to make it automatically connected after boot, though.
Thanks a lot for helping, maybe someone finds the commands I shared useful :-) Am Freitag, 1. September 2023, 17:05:57 CEST schrieb Markus Feilner:
Am Freitag, 1. September 2023, 10:37:57 CEST schrieb gumb:
On 01/09/2023 10:28, Markus Feilner wrote:
Hi there,
am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever
I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U
Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot.
Can't speak for Tumbleweed, but on Leap following the upgrade to 15.5 it was necessary to install pipewire-pulseaudio to get my PC communicating with my bluetooth amplifier as before. I'd have thought that change already went through long ago in Tumbleweed though. Do you have that package installed?
It was not installed, I'm doing this right now... requests removal of pulseaudio – I will report – after reboot – what happened. :-)
Nothing else needed configuring in my case, just a reboot and bluetooth / audio was back to normal.
gumb
-- 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 01/09/2023 20:29, Markus Feilner wrote:
Brief update: After the following reboots, everything still works fine, but the device isnt powered on automatically and does not connect automatically. But I'm sure I will find out...
Am Freitag, 1. September 2023, 17:29:52 CEST schrieb Markus Feilner:
Hi there, installling pipewire- and its siblings seems to have done the needful. At least after first reboot, I could connect instantly through the Plasma widget and have sound. Will try to make it automatically connected after boot, though.
Thanks a lot for helping, maybe someone finds the commands I shared useful :-) Am Freitag, 1. September 2023, 17:05:57 CEST schrieb Markus Feilner:
Am Freitag, 1. September 2023, 10:37:57 CEST schrieb gumb:
On 01/09/2023 10:28, Markus Feilner wrote:
Hi there,
am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever
I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U
Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot.
Can't speak for Tumbleweed, but on Leap following the upgrade to 15.5 it was necessary to install pipewire-pulseaudio to get my PC communicating with my bluetooth amplifier as before. I'd have thought that change already went through long ago in Tumbleweed though. Do you have that package installed?
It was not installed, I'm doing this right now... requests removal of pulseaudio – I will report – after reboot – what happened. :-)
Nothing else needed configuring in my case, just a reboot and bluetooth / audio was back to normal.
gumb
Maybe try pairing the devices again, it might reset something in the configuration. By the way, when you mentioned installing all pipewire packages, I was only implying the one package named 'pipewire-pulseaudio'. At least on Leap, installing just that one is enough to make bluetooth audio work again. gumb
Hello, In the Message; Subject : bluetooth audio only connects after several tries Message-ID : <4510419.LvFx2qVVIh@maldacena.feilner-it.net> Date & Time: Fri, 01 Sep 2023 10:28:31 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: [...] MF> Here's a script that I have to run - sometimes several times, and often I MF> still have to power on bluetooth and connect to the stereo manually, in the MF> KDE widget (strangely, bluetoothctl won't do the trick, most of the times). MF> Once connected, Bluetooth works as desired, until the next reboot. [...] MF> I know there's better ways of doing the following, esp. the sudo sections... MF> :-) MF> #!/bin/bash [...] MF> pactl set-default-sink bluez_sink.0C_A6_94_D1_77_5D.a2dp_sink Please show the following results before running your script; $ systemctl status bluetooth.service Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
As I keep on debugging, I seem to have found an error in journalctl that leads me further... among many informative lines of messages from bluetooth and pulseaudio, I found this one: Sep 01 16:55:48 maldacena.feilner-it.net pulseaudio[5809]: Assertion '! pa_hashmap_isempty(data.profiles)' failed at ../src/modules/bluetooth/module- bluez5-device.c:2261, function add_card(). Aborting. That's what happened right after reboot, no other script run. I only did a "bluetoothctl power on" followed by a "bluetoothctl connect ..." Then the log entry came, and I did a "killall -9 pulseaudio", then both bluetoothd, wireplumber and pulseaudio would work fine, no errors. Seems I found the core of the mistake. Sidenote: The "killall -9 pulseaudio" does not "stop" the daemon of pa running. But the new instance works, other than the first one. I'll keep looking into this. Thanks already for rubberducking... :-) Am Freitag, 1. September 2023, 10:28:31 CEST schrieb Markus Feilner:
Hi there,
am I the only one with problems getting bluetooth to work in a 1:1 setup? My Ryzen 7 machine should always autoconnect on boot to its dedicated stereo. Both turn on at the same time, no other machine connects to the BT reciever
I am running Tumbleweed with KDE, plasma and pulseaudio 16.1 on a kernel 6.4.11-1-default, the CPU is an AMD Ryzen 7 PRO 5850U
Here's a script that I have to run - sometimes several times, and often I still have to power on bluetooth and connect to the stereo manually, in the KDE widget (strangely, bluetoothctl won't do the trick, most of the times). Once connected, Bluetooth works as desired, until the next reboot.
I am still digging in the logfiles, but maybe these commands here are helpful for someone... Feel free to PM me if you have similar problems and / or send me links, any help is much appreciated.
I know there's better ways of doing the following, esp. the sudo sections... :-)
#!/bin/bash # sudo /sbin/modprobe -r btusb -r btintel sudo /sbin/modprobe btusb btintel sudo rfkill unblock bluetooth sudo service bluetooth restart sleep 3s bluetoothctl power on bluetoothctl connect 0C:A6:94:D1:77:5D sleep 3s sudo service bluetooth restart bluetoothctl connect 0C:A6:94:D1:77:5D pactl get-default-sink pactl set-default-sink bluez_sink.0C_A6_94_D1_77_5D.a2dp_sink
-- 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, ...
Hello, In the Message; Subject : Re: bluetooth audio only connects after several tries Message-ID : <5971340.lOV4Wx5bFT@maldacena.feilner-it.net> Date & Time: Fri, 01 Sep 2023 17:03:54 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: [...] MF> Then the log entry came, and I did a "killall -9 pulseaudio", then both MF> bluetoothd, wireplumber and pulseaudio would work fine, no errors. MF> Seems I found the core of the mistake. [...] You are fundamentally wrong. The wireplumber is a powerful session and policy manager for pipewire and has nothing to do with pulseaudio. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --
participants (3)
-
gumb -
Markus Feilner -
Masaru Nomiya