I have Arch Linux ARM installed on a Chromebook C201. I've been trying to get bluetooth working without success and I can't figure out where the problem is.
The output of
dmesg seems to indicate that the system is finding and initializing the onboard bluetooth controller successfully:
$ dmesg | grep Blue [ 4.058823] Bluetooth: Core ver 2.22 [ 4.058865] Bluetooth: HCI device and connection manager initialized [ 4.058873] Bluetooth: HCI socket layer initialized [ 4.058877] Bluetooth: L2CAP socket layer initialized [ 4.058886] Bluetooth: SCO socket layer initialized [ 4.061738] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 4.971101] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.971104] Bluetooth: BNEP filters: protocol multicast [ 4.971113] Bluetooth: BNEP socket layer initialized
As far as I can see, the kernel modules that are required for bluetooth also seem to have been loaded on boot:
$ lsmod | grep ^b bnep 20480 2 btsdio 16384 0 bluetooth 352256 9 btsdio,bnep
/sys/class/bluetooth I have the following:
$ ls /sys/class/bluetooth hci0
So, it looks like some sort of bluetooth device is there.
I have the
bluez-utils packages installed and I have enabled bluetoothd, which I have confirmed is running:
$ systemctl status bluetooth.service ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset:> Active: active (running) since Sun 2019-02-03 07:22:15 EST; 6h ago Docs: man:bluetoothd(8) Main PID: 324 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 2.4M CGroup: /system.slice/bluetooth.service └─324 /usr/lib/bluetooth/bluetoothd
I have also checked that the bluetooth controller is not being blocked by rfkill:
$ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no
However, if I try to run
blueman), no bluetooth adapters can be found:
$ bluetoothctl Agent registered [bluetooth]# list [bluetooth]#
I can't think of anything else to try. Is there something that I'm missing?
The only answer given didn't solve the issue, and there seems to have been very little response to this question, despite getting some extra visibility from the bounty. Should I infer, then, that everything that should be there seems to be correctly in place? Does that point to it being more likely to be a bug, perhaps in bluez or in the kernel module?