You are not logged in.
Hi, this is my first time in Arch Forum and I've looked in many posts for the solution but nothing.
I don't know why my bluetooth is dead.
Can anyone help me understand and solve the problem?
Thank you
Unit service.service could not be found.
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Sun 2024-04-07 00:01:57 CEST; 38min ago
Docs: man:bluetoothd(8)
Main PID: 395 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9387)
Memory: 3.1M (peak: 3.3M)
CPU: 52ms
CGroup: /system.slice/bluetooth.service
└─395 /usr/lib/bluetooth/bluetoothd
Apr 07 00:01:57 marale bluetoothd[395]: Starting SDP server
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support bap plugin
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support bass plugin
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support mcp plugin
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support vcp plugin
Apr 07 00:01:57 marale bluetoothd[395]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support micp plugin
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support ccp plugin
Apr 07 00:01:57 marale bluetoothd[395]: src/plugin.c:init_plugin() System does not support csip plugin
Apr 07 00:01:57 marale bluetoothd[395]: Bluetooth management interface 1.22 initialized
[alex@marale ~]$ blueman-applet
blueman-applet 00.40.45 WARNING PluginManager:93 load_plugin: Failed to start plugin GameControllerWakelock: Only X11 platform is supported
blueman-applet 00.40.45 WARNING DiscvManager:122 update_menuitems: warning: Adapter is None
Last edited by pescio75 (2024-04-09 09:39:17)
Offline
Your bluetoothd service is running. Does bluetoothctl work? The only problem is that applet doesn't support wayland
Offline
You don't want blueman-applet anyway, KDE has bluedevil and that's integrated into plasma.
As for looking at many posts... you must have missed https://bbs.archlinux.org/viewtopic.php?id=294310&p=3 which identified a regression in the 6.8.2 kernel and there are a bunch of "good" bisected kernels and the relevant issues identified and will likely get fixed in future stable kernels, or use on of the reverts provided there.
Offline
Your bluetoothd service is running. Does bluetoothctl work? The only problem is that applet doesn't support wayland
[alex@marale ~]$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# show
No default controller available
Offline
Have you looked at the thread V1del linked and tested if the issue was introduced in 6.8.2 and if so by which commit?
Offline
You don't want blueman-applet anyway, KDE has bluedevil and that's integrated into plasma.
As for looking at many posts... you must have missed https://bbs.archlinux.org/viewtopic.php?id=294310&p=3 which identified a regression in the 6.8.2 kernel and there are a bunch of "good" bisected kernels and the relevant issues identified and will likely get fixed in future stable kernels, or use on of the reverts provided there.
I uninstalled Blueman and I have two kernels but it doesn't work on both.
Linux marale 6.8.2-zen2-1-zen
Linux marale 6.6.25-1-lts
Offline
Yes all of this is expected.. please read the linked thread and check the bisection kernels posted there. One part of that puzzle got fixed in 6.8.4 maybe check whether an upgrade to that already fixes things.
Offline
I don't know if it can be useful
[alex@marale ~]$ sudo dmesg | grep -i blue
[sudo] password for alex:
[ 3.593451] Bluetooth: Core ver 2.22
[ 3.593495] NET: Registered PF_BLUETOOTH protocol family
[ 3.593498] Bluetooth: HCI device and connection manager initialized
[ 3.593503] Bluetooth: HCI socket layer initialized
[ 3.593506] Bluetooth: L2CAP socket layer initialized
[ 3.593510] Bluetooth: SCO socket layer initialized
[ 3.833458] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 3.838385] Bluetooth: hci0: Device revision is 5
[ 3.838392] Bluetooth: hci0: Secure boot is enabled
[ 3.838393] Bluetooth: hci0: OTP lock is enabled
[ 3.838395] Bluetooth: hci0: API lock is enabled
[ 3.838396] Bluetooth: hci0: Debug lock is disabled
[ 3.838398] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 3.848635] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 4.661225] Bluetooth: hci0: Failed to send firmware data (-38)
[ 4.661248] Bluetooth: hci0: Intel reset sent to retry FW download
[ 4.941769] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.941774] Bluetooth: BNEP filters: protocol multicast
[ 4.941778] Bluetooth: BNEP socket layer initialized
[ 6.837580] Bluetooth: hci0: command 0xfca6 tx timeout
[ 6.837598] Bluetooth: hci0: Reading supported features failed (-110)
[ 6.837604] Bluetooth: hci0: Error reading debug features
[ 6.837610] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Offline
Is the issue still present after you updated the kernel to linux-zen 6.8.4.zen1-1 and rebooted into that kernel? If so is the issue present if you downgrade the kernel to linux-zen 6.8.1.zen1-1?
Last edited by loqs (2024-04-08 16:32:46)
Offline
Is the issue still present after you updated the kernel to linux-zen 6.8.4.zen1-1 and rebooted into that kernel? If so is the issue present if you downgrade the kernel to linux-zen 6.8.1.zen1-1?
I only have these
linux-lts-6.6.25-1-x86_64.pkg.tar.zst
linux-zen-6.8.2.zen2-1-x86_64.pkg.tar.zst
I cleared the cache recently
Offline
Offline
alex@marale ~]$ uname -a
Linux marale 6.8.4-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:08 +0000 x86_64 GNU/Linux
thank you for the help, i updated but bluetooth is not working
Offline
Try this kernel: https://bbs.archlinux.org/viewtopic.php … 4#p2162664
Offline
Now it works, with the reboot after the update. Thank you all for your help
Offline
again it doesn't work, I don't understand maybe it's a hardware issue
Offline