When i try bluetoothctl in the shell, it will show
[ws@End lib]$ bluetoothctl
Agent registered
[bluetooth]# scan on
No default controller available
if i try GUI bluetooth tools such as blueman, i couldn’t open the devices window of blueman
i’m sure about bluetooth is unlock by
[ws@End lib]$ rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
1 wlan phy0 unblocked unblocked
and here are my systemctl status bluetooth
[ws@End lib]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Wed 2023-09-20 17:28:13 CST; 24min ago
Docs: man:bluetoothd(8)
Main PID: 894 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 38044)
Memory: 2.4M
CPU: 36ms
CGroup: /system.slice/bluetooth.service
└─894 /usr/lib/bluetooth/bluetoothd
9月 20 17:28:13 End bluetoothd[894]: Bluetooth daemon 5.69
9月 20 17:28:13 End bluetoothd[894]: Starting SDP server
9月 20 17:28:13 End bluetoothd[894]: src/plugin.c:plugin_init() System does not support csip plugin
9月 20 17:28:13 End bluetoothd[894]: src/plugin.c:plugin_init() System does not support vcp plugin
9月 20 17:28:13 End bluetoothd[894]: src/plugin.c:plugin_init() System does not support mcp plugin
9月 20 17:28:13 End bluetoothd[894]: src/plugin.c:plugin_init() System does not support bass plugin
9月 20 17:28:13 End bluetoothd[894]: src/plugin.c:plugin_init() System does not support bap plugin
9月 20 17:28:13 End bluetoothd[894]: Bluetooth management interface 1.22 initialized
9月 20 17:28:13 End systemd[1]: Started Bluetooth service.
9月 20 17:28:30 End bluetoothd[894]: src/profile.c:register_profile() :1.70 tried to register 0000111f-0000-1000-8000-00805f9b34fb which is already registered
I guess there must be something wrong again, same things happened again.
here are my journal http://ix.io/4IsK
and sudo bluetoothctl does not work yet
$ sudo bluetoothctl
Agent registered
[bluetooth]# power on
No default controller available
[bluetooth]# discoverable on
No default controller available
OK, it works again, but i dont know why.
As i use eos and windows on a same pc, i found that when bluetooth failed on eos, it failed on windows too. So i need to reinstall driver for bluetooth on windows and reboot. Then bluetooth works on win, but still failed on eos. I also try some things but still failed. And when i close my pc, wait maybe 10-20 mins, and open pc with eos, now it works, amazing again.
And my laptop uses Intel ® Wi-Fi 6 AX101, so it seems not to work when using ibt-1040-0041.sfi or 1040-4150 to replace 1040-1050 which is lacked.
If i replace, first scan on command would find nothing, and command ''scan on" again will show:
[bluetooth]# Failed to start discovery: org.bluez.Error.InProgress
Here is a blog i find to try to fix my problem but failed.