You are not logged in.
Hi,
Since moving to arch I've had issues trying to get bluetooth working, I've tried numerous solutions posted on other forums and stack overflow questions, but the problem persists.
> sudo lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. USB3.0-CRW
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader
Bus 001 Device 002: ID 04f2:b61e Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 004: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > sudo lsmod | grep bluetooth
bluetooth 876544 15 btrtl,btmtk,btintel,btbcm,bnep,btusb
ecdh_generic 16384 1 bluetooth
rfkill 36864 9 iwlmvm,bluetooth,thinkpad_acpi,cfg80211
crc16 16384 2 bluetooth,ext4 > rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth tpacpi_bluetooth_sw unblocked unblocked
2 wlan phy0 unblocked unblocked
4 bluetooth hci0 unblocked unblockedI have
bluetooth.serviceenabled and started, this is the output of it's status:
> sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Sat 2022-07-09 15:31:05 BST; 1 day 21h ago
Docs: man:bluetoothd(8)
Main PID: 621 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 18681)
Memory: 1.7M
CPU: 44ms
CGroup: /system.slice/bluetooth.service
└─621 /usr/lib/bluetooth/bluetoothd
Jul 09 15:31:05 arch bluetoothd[621]: Starting SDP server
Jul 09 15:31:05 arch bluetoothd[621]: Bluetooth management interface 1.22 initialized
Jul 10 12:03:33 arch bluetoothd[621]: src/adapter.c:index_removed() Ignoring index removal for a non-existent adapter
Jul 10 12:03:33 arch bluetoothd[621]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Invalid Index (0x11)
Jul 10 12:03:33 arch bluetoothd[621]: Failed to read exp features info: Invalid Index (0x11)
Jul 10 12:03:33 arch bluetoothd[621]: Failed to read info for index 0: Invalid Index (0x11)
Jul 10 22:36:30 arch bluetoothd[621]: src/adapter.c:index_removed() Ignoring index removal for a non-existent adapter
Jul 10 22:36:30 arch bluetoothd[621]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Invalid Index (0x11)
Jul 10 22:36:30 arch bluetoothd[621]: Failed to read exp features info: Invalid Index (0x11)
Jul 10 22:36:30 arch bluetoothd[621]: Failed to read info for index 0: Invalid Index (0x11)An interesting side note, sometimes when I shut the lid of the laptop and open it a few minutes later I see the bluetooth controller listed when I run
bluetoothctl show, not sure if this is helpful but this is the log from dmesg when this occurs:
> dmesg | grep Bluetooth
[ 2.791606] Bluetooth: Core ver 2.22
[ 2.791632] Bluetooth: HCI device and connection manager initialized
[ 2.791637] Bluetooth: HCI socket layer initialized
[ 2.791638] Bluetooth: L2CAP socket layer initialized
[ 2.791642] Bluetooth: SCO socket layer initialized
[ 2.831429] Bluetooth: hci0: Firmware revision 0.1 build 166 week 30 2021
[ 2.833370] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[ 2.833403] Bluetooth: hci0: Boot Address: 0x40800
[ 2.833404] Bluetooth: hci0: Firmware Version: 166-30.21
[ 2.833406] Bluetooth: hci0: Firmware already loaded
[ 2.899045] Bluetooth: hci0: MSFT filter_enable is already on
[ 2.941504] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.941506] Bluetooth: BNEP filters: protocol multicast
[ 2.941508] Bluetooth: BNEP socket layer initialized
[ 69.753753] Bluetooth: hci0: Timed out waiting for suspend events
[ 69.753753] Bluetooth: hci0: command 0xfc1e tx timeout
[ 69.753762] Bluetooth: hci0: Suspend timeout bit: 9
[ 69.753801] Bluetooth: hci0: Suspend notifier action (3) failed: -110
[ 75.831958] Bluetooth: hci1: Bootloader revision 0.1 build 42 week 52 2015
[ 75.833136] Bluetooth: hci1: Device revision is 2
[ 75.833143] Bluetooth: hci1: Secure boot is enabled
[ 75.833146] Bluetooth: hci1: OTP lock is enabled
[ 75.833149] Bluetooth: hci1: API lock is enabled
[ 75.833151] Bluetooth: hci1: Debug lock is disabled
[ 75.833153] Bluetooth: hci1: Minimum firmware build 1 week 10 2014
[ 75.833161] Bluetooth: hci1: Found device firmware: intel/ibt-17-16-1.sfi
[ 77.589496] Bluetooth: hci1: Waiting for firmware download to complete
[ 77.589898] Bluetooth: hci1: Firmware loaded in 1714726 usecs
[ 77.589953] Bluetooth: hci1: Waiting for device to boot
[ 77.603954] Bluetooth: hci1: Device booted in 13709 usecs
[ 77.663985] Bluetooth: hci1: Found Intel DDC parameters: intel/ibt-17-16-1.ddc
[ 77.666047] Bluetooth: hci1: Applying Intel DDC parameters completed
[ 77.668979] Bluetooth: hci1: Firmware revision 0.1 build 166 week 30 2021
[ 77.727861] Bluetooth: hci1: MSFT filter_enable is already on
[ 77.741223] Bluetooth: RFCOMM TTY layer initialized
[ 77.741228] Bluetooth: RFCOMM socket layer initialized
[ 77.741230] Bluetooth: RFCOMM ver 1.11If anyone has any ideas, or questions please let me know,
Thanks in advance!
Last edited by tonysala (2022-07-11 12:34:47)
Offline
I am also going through the same problem mine hardwares are surely different. But the main blocker seems to be "No default controller available"
`lsmod` consists of `btusb`,
lsusb | grep bluetooth -i
Bus 001 Device 003: ID 0a5c:21d7 Broadcom Corp. BCM43142 Bluetooth 4.0 bluetooth.service is active and running
There have been few problems like conflicts between two programs I don't have that too
systemctl list-unit-files | grep blue
bluetooth-mesh.service disabled disabled
bluetooth.service enabled disabled
dbus-org.bluez.service alias -
bluetooth.target static -Experiment at-least.
Offline
I solved the issue it might help you too. Actually, I searched for `yay bluetooth` because when I wanted to use wifi I was required to use a new package from yay(broadcom-wl, in my case). So similarly during search, I found a few packages which were named the same as my Broadcom Bluetooth card (bcm43142=card name, bcm43142a0-firmaware=package name). That surely makes some sense I searched with that term on forum and saw some people have been suggesting that so I installed it, even when it is marked as orphaned recently.
Rebooted,
bluetoothctl,
power on in the interactive menu as suggested in arch wiki.
So may be search for your firmware. Good luck!
Experiment at-least.
Offline