bluetoothctl power on fails, KDE GUI works ?
Hi, what is the difference between "bluetoothctl power on" and the "Activate Bluetooth" Switch in KDE's GUI? Only the latter works for me after boot. Once activated through the GUI, also bluetootctl will work fine. I want to have it active on boot, thus I need the script command... Thanks! -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
Hello, In the Message; Subject : bluetoothctl power on fails, KDE GUI works ? Message-ID : <4882172.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Tue, 09 Jul 2024 08:49:04 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> Hi, MF> what is the difference between "bluetoothctl power on" and the "Activate MF> Bluetooth" Switch in KDE's GUI? Only the latter works for me MF> after boot. Once activated through the GUI, also bluetootctl will MF> work fine. I want to have it active on boot, thus I need the MF> script command... I don't know which distro you are using, but power should be on at boot time. What is the following result right after boot? $ sudo systemctl status bluetooth.service Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
$ sudo systemctl status bluetooth.service "Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)" Running Tumbleweed. Am Mittwoch, 10. Juli 2024, 10:08:10 MESZ schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : bluetoothctl power on fails, KDE GUI works ? Message-ID : <4882172.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Tue, 09 Jul 2024 08:49:04 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> Hi,
MF> what is the difference between "bluetoothctl power on" and the "Activate MF> Bluetooth" Switch in KDE's GUI? Only the latter works for me MF> after boot. Once activated through the GUI, also bluetootctl will MF> work fine. I want to have it active on boot, thus I need the MF> script command...
I don't know which distro you are using, but power should be on at boot time.
What is the following result right after boot?
$ sudo systemctl status bluetooth.service
Best Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard."
-- Employers don’t practice what they preach on skills-based hiring --
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
That's exactly my issue. Systemctl starts the service, but it does not power on the adapter. Sytemctl says: "Active: active (running) since Wed 2024-07-10 11:13:41 CEST; 11min ago" but "power on" in bluetoothctl throws an error - have to reboot now to reproduce it. After boot, I cannot power on the adapter with bluetoothctl, but the KDE tool is able to "Activate" it. So I would like to know what other magic the KDE tool does to power on the bluetooth adapter... Am Mittwoch, 10. Juli 2024, 11:25:32 MESZ schrieb Markus Feilner:
$ sudo systemctl status bluetooth.service "Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)"
Running Tumbleweed.
Am Mittwoch, 10. Juli 2024, 10:08:10 MESZ schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : bluetoothctl power on fails, KDE GUI works ? Message-ID : <4882172.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Tue, 09 Jul 2024 08:49:04 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> Hi,
MF> what is the difference between "bluetoothctl power on" and the "Activate MF> Bluetooth" Switch in KDE's GUI? Only the latter works for me MF> after boot. Once activated through the GUI, also bluetootctl will MF> work fine. I want to have it active on boot, thus I need the MF> script command...
I don't know which distro you are using, but power should be on at boot time.
What is the following result right after boot?
$ sudo systemctl status bluetooth.service
Best Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and
intentional changes in their hiring practices ― and
change is
hard."
-- Employers don’t practice what they preach on skills-based hiring
--
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
After a clean reboot at a fresh KDE session: mfeilner@maldacena:~> bluetoothctl Waiting to connect to bluetoothd...[bluetooth]# Agent registered [bluetooth]# power on [bluetooth]# Failed to set power on: org.bluez.Error.Failed [bluetooth]# as root: maldacena:/home/mfeilner # systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled) Active: active (running) since Wed 2024-07-10 11:30:08 CEST; 10min ago Docs: man:bluetoothd(8) Main PID: 1171 (bluetoothd) Status: "Running" - "activates" Bluetooth in KDE - mfeilner@maldacena:~> bluetoothctl Waiting to connect to bluetoothd...[bluetooth]# Agent registered [bluetooth]# power on [bluetooth]# Changing power on succeeded Weird. power is already on, according to KDE Bluetooth tool. Seems like a disconnect between bluetoothctl and KDE...? journalctl -xe yields only these bluetooth errors:: (...) Jul 10 11:41:01 maldacena.feilner-it.net plasmashell[2416]: kf.bluezqt: PendingCall Error: "" Jul 10 11:41:13 maldacena.feilner-it.net plasmashell[2416]: file:///usr/share/ plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml: 65:13: QML To> (...) and dmesg does not report any error: [ 24.086339] [ T2644] Bluetooth: RFCOMM TTY layer initialized [ 24.086351] [ T2644] Bluetooth: RFCOMM socket layer initialized [ 24.086355] [ T2644] Bluetooth: RFCOMM ver 1.11 Any help appreciated, I will keep you updated. My goal is to have this machine autoconnect to the Bluetooth receiver on my amp upon boot. It did work some months ago, but it stopped... Am Mittwoch, 10. Juli 2024, 11:29:14 MESZ schrieb Markus Feilner:
That's exactly my issue. Systemctl starts the service, but it does not power on the adapter.
Sytemctl says: "Active: active (running) since Wed 2024-07-10 11:13:41 CEST; 11min ago"
but "power on" in bluetoothctl throws an error - have to reboot now to reproduce it. After boot, I cannot power on the adapter with bluetoothctl, but the KDE tool is able to "Activate" it. So I would like to know what other magic the KDE tool does to power on the bluetooth adapter...
Am Mittwoch, 10. Juli 2024, 11:25:32 MESZ schrieb Markus Feilner:
$ sudo systemctl status bluetooth.service
"Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)"
Running Tumbleweed.
Am Mittwoch, 10. Juli 2024, 10:08:10 MESZ schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : bluetoothctl power on fails, KDE GUI works ? Message-ID : <4882172.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Tue, 09 Jul 2024 08:49:04 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> Hi,
MF> what is the difference between "bluetoothctl power on" and the "Activate MF> Bluetooth" Switch in KDE's GUI? Only the latter works for me MF> after boot. Once activated through the GUI, also bluetootctl will MF> work fine. I want to have it active on boot, thus I need the MF> script command...
I don't know which distro you are using, but power should be on at boot time.
What is the following result right after boot?
$ sudo systemctl status bluetooth.service
Best Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and
intentional changes in their hiring practices ― and
change is
hard."
-- Employers don’t practice what they preach on skills-based hiring
--
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
Hello, In the Message; Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <2701465.vuYhMxLoTh@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:45:18 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> After a clean reboot at a fresh KDE session: MF> mfeilner@maldacena:~> bluetoothctl MF> Waiting to connect to bluetoothd...[bluetooth]# Agent registered MF> [bluetooth]# power on MF> [bluetooth]# Failed to set power on: org.bluez.Error.Failed MF> [bluetooth]# [...] This means that power is already on. Why is it not powered on, you say? Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
Hello, In the Message; Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <2511289.XAFRqVoOGU@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:29:14 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> That's exactly my issue. Systemctl starts the service, but it MF> does not power on the adapter. MF> Sytemctl says: MF> "Active: active (running) since Wed 2024-07-10 11:13:41 CEST; 11min ago" Regardless of what you say, this is not right. In the Message; Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <4881002.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:25:32 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> $ sudo systemctl status bluetooth.service MF> "Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: MF> disabled)" [...] BTW. MF> but "power on" in bluetoothctl throws an error - have to reboot now to MF> reproduce it. After boot, I cannot power on the adapter with MF> bluetoothctl, but the KDE tool is able to "Activate" it. So I MF> would like to know what other magic the KDE tool does to power on MF> the bluetooth adapter... [...] This is not right, again. Please show the results of; 1. $ dmesg | grep -i blue 2. $ inxi -Eaz Best Regards. --- ┏━━┓彡 Masaru Nomiya 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 --
Hi, and thanks a lot! Here's dmesg and inxi output I will also send the results of the commands after my next reboot. But believe me, the only thing both bluetoothctl and KDE are agreeing on after reboot is that the bluetooth adapter is not powered on. :-) I'm only reporting what I am seeing. 1) mfeilner@maldacena:~> dmesg | grep -i blue [ 9.620080] [ T929] Bluetooth: Core ver 2.22 [ 9.620257] [ T929] NET: Registered PF_BLUETOOTH protocol family [ 9.620263] [ T929] Bluetooth: HCI device and connection manager initialized [ 9.620272] [ T929] Bluetooth: HCI socket layer initialized [ 9.620278] [ T929] Bluetooth: L2CAP socket layer initialized [ 9.620292] [ T929] Bluetooth: SCO socket layer initialized [ 9.994715] [ T624] Bluetooth: hci0: Found device firmware: intel/ ibt-20-1-3.sfi [ 9.994726] [ T624] Bluetooth: hci0: Boot Address: 0x24800 [ 9.994727] [ T624] Bluetooth: hci0: Firmware Version: 132-3.24 [ 9.994729] [ T624] Bluetooth: hci0: Firmware already loaded [ 10.002478] [ T624] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. [ 10.478945] [ T1171] Bluetooth: MGMT ver 1.22 [ 24.086339] [ T2644] Bluetooth: RFCOMM TTY layer initialized [ 24.086351] [ T2644] Bluetooth: RFCOMM socket layer initialized [ 24.086355] [ T2644] Bluetooth: RFCOMM ver 1.11 2) this is after having enabled bluetooth adapter with KDE tools (and in use): I will reboot and send the output of these commands later... mfeilner@maldacena:~> inxi -Eaz Bluetooth: Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:4 chip-ID: 8087:0029 class-ID: e001 Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c mfeilner@maldacena:~> Am Mittwoch, 10. Juli 2024, 12:11:08 MESZ schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <2511289.XAFRqVoOGU@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:29:14 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> That's exactly my issue. Systemctl starts the service, but it MF> does not power on the adapter.
MF> Sytemctl says: MF> "Active: active (running) since Wed 2024-07-10 11:13:41 CEST; 11min ago"
Regardless of what you say, this is not right.
In the Message;
Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <4881002.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:25:32 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> $ sudo systemctl status bluetooth.service MF> "Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: MF> disabled)" [...]
BTW.
MF> but "power on" in bluetoothctl throws an error - have to reboot now to MF> reproduce it. After boot, I cannot power on the adapter with MF> bluetoothctl, but the KDE tool is able to "Activate" it. So I MF> would like to know what other magic the KDE tool does to power on MF> the bluetooth adapter... [...]
This is not right, again.
Please show the results of;
1.
$ dmesg | grep -i blue
2.
$ inxi -Eaz
Best Regards.
--- ┏━━┓彡 Masaru Nomiya 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 --
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
And this is inxi -Eaz after a fresh reboot: mfeilner@maldacena:~> inxi -Eaz Bluetooth: Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:4 chip-ID: 8087:0029 class-ID: e001 Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no mfeilner@maldacena:~> mfeilner@maldacena:~> bluetoothctl Waiting to connect to bluetoothd...[bluetooth]# Agent registered [bluetooth]# power on [bluetooth]# Failed to set power on: org.bluez.Error.Failed [bluetooth]# power off [bluetooth]# Changing power off succeeded [bluetooth]# power on [bluetooth]# Failed to set power on: org.bluez.Error.Failed As i said, activating BT from KDE settings or systray works fine. Same is happening here on my work laptop. Am Mittwoch, 10. Juli 2024, 20:19:17 MESZ schrieb Markus Feilner:
Hi, and thanks a lot!
Here's dmesg and inxi output
I will also send the results of the commands after my next reboot. But believe me, the only thing both bluetoothctl and KDE are agreeing on after reboot is that the bluetooth adapter is not powered on. :-) I'm only reporting what I am seeing.
1)
mfeilner@maldacena:~> dmesg | grep -i blue [ 9.620080] [ T929] Bluetooth: Core ver 2.22 [ 9.620257] [ T929] NET: Registered PF_BLUETOOTH protocol family [ 9.620263] [ T929] Bluetooth: HCI device and connection manager initialized [ 9.620272] [ T929] Bluetooth: HCI socket layer initialized [ 9.620278] [ T929] Bluetooth: L2CAP socket layer initialized [ 9.620292] [ T929] Bluetooth: SCO socket layer initialized [ 9.994715] [ T624] Bluetooth: hci0: Found device firmware: intel/ ibt-20-1-3.sfi [ 9.994726] [ T624] Bluetooth: hci0: Boot Address: 0x24800 [ 9.994727] [ T624] Bluetooth: hci0: Firmware Version: 132-3.24 [ 9.994729] [ T624] Bluetooth: hci0: Firmware already loaded [ 10.002478] [ T624] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. [ 10.478945] [ T1171] Bluetooth: MGMT ver 1.22 [ 24.086339] [ T2644] Bluetooth: RFCOMM TTY layer initialized [ 24.086351] [ T2644] Bluetooth: RFCOMM socket layer initialized [ 24.086355] [ T2644] Bluetooth: RFCOMM ver 1.11
2) this is after having enabled bluetooth adapter with KDE tools (and in use): I will reboot and send the output of these commands later...
mfeilner@maldacena:~> inxi -Eaz Bluetooth: Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:4 chip-ID: 8087:0029 class-ID: e001 Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2 lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c mfeilner@maldacena:~>
Am Mittwoch, 10. Juli 2024, 12:11:08 MESZ schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <2511289.XAFRqVoOGU@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:29:14 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> That's exactly my issue. Systemctl starts the service, but it MF> does not power on the adapter.
MF> Sytemctl says: MF> "Active: active (running) since Wed 2024-07-10 11:13:41 CEST; 11min ago"
Regardless of what you say, this is not right.
In the Message;
Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <4881002.OV4Wx5bFTl@maldacena.feilner-it.net> Date & Time: Wed, 10 Jul 2024 11:25:32 +0200
[MF] == Markus Feilner <mfeilner@feilner-it.net> has written:
MF> $ sudo systemctl status bluetooth.service MF> "Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: MF> disabled)" [...]
BTW.
MF> but "power on" in bluetoothctl throws an error - have to reboot now to MF> reproduce it. After boot, I cannot power on the adapter with MF> bluetoothctl, but the KDE tool is able to "Activate" it. So I MF> would like to know what other magic the KDE tool does to power on MF> the bluetooth adapter... [...]
This is not right, again.
Please show the results of;
1.
$ dmesg | grep -i blue
2.
$ inxi -Eaz
Best Regards.
--- ┏━━┓彡 Masaru Nomiya 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
--
-- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
Hello, Sorry for late reply. In the Message; Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <4933552.31r3eYUQgx@majorana.feilner-it.home> Date & Time: Thu, 11 Jul 2024 01:42:04 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> And this is inxi -Eaz after a fresh reboot: mfeilner@maldacena:~> inxi -Eaz MF> Bluetooth: MF> Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 MF> speed: 12 Mb/s lanes: 1 MF> mode: 1.1 bus-ID: 3-3:4 chip-ID: 8087:0029 class-ID: e001 MF> Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running MF> rfk-block: MF> hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11 status: MF> discoverable: no MF> pairing: no mfeilner@maldacena:~> mfeilner@maldacena:~> bluetoothctl MF> Waiting to connect to bluetoothd...[bluetooth]# Agent registered MF> [bluetooth]# power on MF> [bluetooth]# Failed to set power on: org.bluez.Error.Failed MF> [bluetooth]# power off MF> [bluetooth]# Changing power off succeeded MF> [bluetooth]# power on MF> [bluetooth]# Failed to set power on: org.bluez.Error.Failed MF> As i said, activating BT from KDE settings or systray works fine. MF> Same is happening here on my work laptop. MF> Am Mittwoch, 10. Juli 2024, 20:19:17 MESZ schrieb Markus Feilner: MF> > Hi, and thanks a lot! MF> > MF> > Here's dmesg and inxi output MF> > MF> > I will also send the results of the commands after my next reboot. But MF> > believe me, the only thing both bluetoothctl and KDE are agreeing on after MF> > reboot is that the bluetooth adapter is not powered on. :-) I'm only MF> > reporting what I am seeing. MF> > MF> > MF> > 1) MF> > MF> > mfeilner@maldacena:~> dmesg | grep -i blue MF> > [ 9.620080] [ T929] Bluetooth: Core ver 2.22 MF> > [ 9.620257] [ T929] NET: Registered PF_BLUETOOTH protocol family MF> > [ 9.620263] [ T929] Bluetooth: HCI device and connection manager MF> > initialized MF> > [ 9.620272] [ T929] Bluetooth: HCI socket layer initialized MF> > [ 9.620278] [ T929] Bluetooth: L2CAP socket layer initialized MF> > [ 9.620292] [ T929] Bluetooth: SCO socket layer initialized MF> > [ 9.994715] [ T624] Bluetooth: hci0: Found device firmware: intel/ MF> > ibt-20-1-3.sfi MF> > [ 9.994726] [ T624] Bluetooth: hci0: Boot Address: 0x24800 MF> > [ 9.994727] [ T624] Bluetooth: hci0: Firmware Version: 132-3.24 MF> > [ 9.994729] [ T624] Bluetooth: hci0: Firmware already loaded MF> > [ 10.002478] [ T624] Bluetooth: hci0: HCI LE Coded PHY feature bit is MF> > set, but its usage is not supported. MF> > [ 10.478945] [ T1171] Bluetooth: MGMT ver 1.22 MF> > [ 24.086339] [ T2644] Bluetooth: RFCOMM TTY layer initialized MF> > [ 24.086351] [ T2644] Bluetooth: RFCOMM socket layer initialized MF> > [ 24.086355] [ T2644] Bluetooth: RFCOMM ver 1.11 MF> > MF> > 2) this is after having enabled bluetooth adapter with KDE tools (and in MF> > use): I will reboot and send the output of these commands later... MF> > MF> > mfeilner@maldacena:~> inxi -Eaz MF> > Bluetooth: MF> > Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 MF> > speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-3:4 chip-ID: 8087:0029 MF> > class-ID: e001 MF> > Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2 MF> > lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c MF> > mfeilner@maldacena:~> [...] Thanks. This is strange; Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. I thought it was an Intel's problem, so I checked and found; https://community.intel.com/t5/Wireless/AX200-Bluetooth-LE-stopped-working-o... As you see, Intel's customer support said they would look into the cause, but when a customer told them that he reinstalled Fedora and it fixed the problem, it was treated as a solution. Since the problem has not been fundamentally solved, I think it would be better to ask the question again. Best Regards. --- ┏━━┓彡 Masaru Nomiya 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 --
Thank you! That's interesting... and weird... But what does KDE do different from bluetoothctl? KDE is able to activate the adapter, where bluetoothctl is not. If I can envoke that via script, that would fix my problem. Having read the link, I'll try to dive into the rfkill blocks and see if that is making any differences... there are blocks, yes. maldacena:/home/mfeilner # rfkill list 0: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no 1: acer-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2: hci0: Bluetooth Soft blocked: yes Hard blocked: no 3: phy0: Wireless LAN Soft blocked: yes Hard blocked: no maldacena:/home/mfeilner # I'll keep you updated. Am Donnerstag, 11. Juli 2024, 02:41:16 MESZ schrieb Masaru Nomiya:
Hello, (...) Thanks.
This is strange;
Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
I thought it was an Intel's problem, so I checked and found;
https://community.intel.com/t5/Wireless/AX200-Bluetooth-LE-stopped-working-> on-recent-Linux-kernels/m-p/1564621
As you see, Intel's customer support said they would look into the cause, but when a customer told them that he reinstalled Fedora and it fixed the problem, it was treated as a solution.
Since the problem has not been fundamentally solved, I think it would be better to ask the question again.
Best Regards.
--- ┏━━┓彡 Masaru Nomiya 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 --
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
Ok, step by step I'm getting there. Just documenting here, maybe that helps others. rfkill unblock bluetooth helped: I ran it as root, then bluetoothctl power on was successful. The connect however did not work, but it worked with the KDE bluetooth tool - I will see into that later. Currently I am looking into why the block is active on boot - I found this very old thread, maybe there's some clues in here. https://unix.stackexchange.com/questions/127705/automatically-run-rfkill-unb... Anyhow, I have a suspicion: The update/upgrade from tlp to tuned threw some errors on my systems, months ago. Maybe that's where something went wrong.. will keep you updated. Am Donnerstag, 11. Juli 2024, 08:17:07 MESZ schrieb Markus Feilner:
Thank you! That's interesting... and weird...
But what does KDE do different from bluetoothctl? KDE is able to activate the adapter, where bluetoothctl is not. If I can envoke that via script, that would fix my problem.
Having read the link, I'll try to dive into the rfkill blocks and see if that is making any differences... there are blocks, yes.
maldacena:/home/mfeilner # rfkill list 0: acer-wireless: Wireless LAN Soft blocked: yes Hard blocked: no 1: acer-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2: hci0: Bluetooth Soft blocked: yes Hard blocked: no 3: phy0: Wireless LAN Soft blocked: yes Hard blocked: no maldacena:/home/mfeilner #
I'll keep you updated.
Am Donnerstag, 11. Juli 2024, 02:41:16 MESZ schrieb Masaru Nomiya:
Hello,
(...)
Thanks.
This is strange;
Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is
not supported.
I thought it was an Intel's problem, so I checked and found;
https://community.intel.com/t5/Wireless/AX200-Bluetooth-LE-stopped-working -> on-recent-Linux-kernels/m-p/1564621
As you see, Intel's customer support said they would look into the cause, but when a customer told them that he reinstalled Fedora and it fixed the problem, it was treated as a solution.
Since the problem has not been fundamentally solved, I think it would be better to ask the question again.
Best Regards.
--- ┏━━┓彡 Masaru Nomiya 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
--
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
After all, this line is a shell workaround for me. sudo rfkill unblock bluetooth && bluetoothctl power on Run after boot (e.g. in my KDE start script) it fixes my problem. However, I'm still trying to find out where the default settings for rfkill are defined. It used to be tlp, but with tuned I can't find them. I know there's kernel parameters for that, but I dont want/need to engage there .... works4me I guess. Thanks for helping! Am Donnerstag, 11. Juli 2024, 08:30:43 MESZ schrieb Markus Feilner:
Ok, step by step I'm getting there. Just documenting here, maybe that helps others.
rfkill unblock bluetooth helped:
I ran it as root, then bluetoothctl power on was successful. The connect however did not work, but it worked with the KDE bluetooth tool - I will see into that later. Currently I am looking into why the block is active on boot - I found this very old thread, maybe there's some clues in here.
https://unix.stackexchange.com/questions/127705/automatically-run-rfkill-unb lock-on-startup
Anyhow, I have a suspicion: The update/upgrade from tlp to tuned threw some errors on my systems, months ago. Maybe that's where something went wrong..
will keep you updated.
Am Donnerstag, 11. Juli 2024, 08:17:07 MESZ schrieb Markus Feilner:
Thank you! That's interesting... and weird...
But what does KDE do different from bluetoothctl? KDE is able to activate the adapter, where bluetoothctl is not. If I can envoke that via script, that would fix my problem.
Having read the link, I'll try to dive into the rfkill blocks and see if that is making any differences... there are blocks, yes.
maldacena:/home/mfeilner # rfkill list 0: acer-wireless: Wireless LAN
Soft blocked: yes Hard blocked: no
1: acer-bluetooth: Bluetooth
Soft blocked: yes Hard blocked: no
2: hci0: Bluetooth
Soft blocked: yes Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: yes Hard blocked: no
maldacena:/home/mfeilner #
I'll keep you updated.
Am Donnerstag, 11. Juli 2024, 02:41:16 MESZ schrieb Masaru Nomiya:
Hello,
(...)
Thanks.
This is strange;
Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is
not supported.
I thought it was an Intel's problem, so I checked and found;
https://community.intel.com/t5/Wireless/AX200-Bluetooth-LE-stopped-worki ng -> on-recent-Linux-kernels/m-p/1564621
As you see, Intel's customer support said they would look into the cause, but when a customer told them that he reinstalled Fedora and it fixed the problem, it was treated as a solution.
Since the problem has not been fundamentally solved, I think it would be better to ask the question again.
Best Regards.
--- ┏━━┓彡 Masaru Nomiya 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
--
-- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
Hello, In the Message; Subject : Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <2141389.9o76ZdvQCi@maldacena.feilner-it.net> Date & Time: Thu, 11 Jul 2024 08:43:46 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> After all, this line is a shell workaround for me. MF> sudo rfkill unblock bluetooth && bluetoothctl power on MF> Run after boot (e.g. in my KDE start script) it fixes my problem. MF> However, I'm still trying to find out where the default settings for rfkill are MF> defined. It used to be tlp, but with tuned I can't find them. I know there's MF> kernel parameters for that, but I dont want/need to engage there MF> .... works4me I guess. [...] Wouldn't auto-execution be a better way to create a Systemd Unit file? Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
Am Donnerstag, 11. Juli 2024, 09:43:24 MESZ schrieb Masaru Nomiya:
Wouldn't auto-execution be a better way to create a Systemd Unit file?
I guess so, but for a different use case. Bluetooth-Audio and other things are or should only be present (or it makes only sense) if there's a desktop environment. And the bluetooth settings (devices) are user-only, or are they system-wide? So if am not wrong, the problem is "WHY ON EARTH is my system soft-blocking Bluetooth on boot and WHY ON EARTH can KDE fix it with one click, but bluetoothctl can't? Answer to the second question: because there's a rfkill block and KDE obviously removes it upon click. -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
Hello, In the Message; Subject : SOLVED Re: bluetoothctl power on fails, KDE GUI works ? Message-ID : <4595166.LvFx2qVVIh@majorana.feilner-it.home> Date & Time: Thu, 11 Jul 2024 18:31:06 +0200 [MF] == Markus Feilner <mfeilner@feilner-it.net> has written: MF> Am Donnerstag, 11. Juli 2024, 09:43:24 MESZ schrieb Masaru Nomiya: [...] MF> So if am not wrong, the problem is "WHY ON EARTH is my system MF> soft-blocking Bluetooth on boot and WHY ON EARTH can KDE fix it MF> with one click, but bluetoothctl can't? MF> Answer to the second question: because there's a rfkill block and KDE MF> obviously removes it upon click. In Linux, systemd-rfkill.service runs at system startup and shutdown, but this does not work for your Intel AX200, which is a problem. If I were you, I would ask Intel customer support. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
Am Freitag, 12. Juli 2024, 06:48:13 MESZ schrieb Masaru Nomiya:
In Linux, systemd-rfkill.service runs at system startup and shutdown, but this does not work for your Intel AX200, which is a problem.
If I were you, I would ask Intel customer support.
Thank you! That's a cool and specific answer to my questions... and I guess KDE does integrate rfkill, too, so that's why it works and bluetoothctl doesnt. -- -- Best Regards - Mit freundlichen Grüßen, Markus Feilner, Feilner IT - 20 years of open services - Digital Sustainability, Sovereignty, Sobriety Open Source Strategy, Knowledge Management, Documentation Trainings, Workshops, Coaching, Networking, Politics, Journalism 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, ... Once you see something, you can't unsee it. And once you've seen it, keeping quiet, saying nothing, becomes as political an act as speaking out. (Arundhati Roy)
participants (2)
-
Markus Feilner -
Masaru Nomiya