0

I am simply trying to get Bluetooth to work on the latest version of Arch build for the Raspberry Pi Zero W (original, not 2).

I have the latest version of Arch(armv6) successfully running on the rpi zero W. I am sshed into it, via it's wireless interface.

When I try to do bluetoothctl scan on I get an error No default controller available. Further more, I don't have any hciconfig. Take note from the output below that the service appears to be up and running successfully. (which I got to work after issuing the command modprobe btusb)

[root@alarmpi bin]# systemctl status bluetooth.service
* bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2021-11-30 06:18:27 UTC; 1min 2s ago
       Docs: man:bluetoothd(8)
   Main PID: 1021 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 383)
        CPU: 211ms
     CGroup: /system.slice/bluetooth.service
             `-1021 /usr/lib/bluetooth/bluetoothd

Nov 30 06:18:27 alarmpi systemd[1]: Starting Bluetooth service...
Nov 30 06:18:27 alarmpi bluetoothd[1021]: Bluetooth daemon 5.62
Nov 30 06:18:27 alarmpi systemd[1]: Started Bluetooth service.
Nov 30 06:18:27 alarmpi bluetoothd[1021]: Starting SDP server
Nov 30 06:18:27 alarmpi bluetoothd[1021]: Bluetooth management interface 1.18 initialized
[root@alarmpi bin]# bluetoothctl scan on
No default controller available
[root@alarmpi bin]# hciconfig
bash: hciconfig: command not found

1
  • @ukBaz, [root@alarmpi bluez-5.58]# systemctl restart hciuart.service Failed to restart hciuart.service: Unit hciuart.service not found.
    – Matthew
    Nov 30, 2021 at 13:39

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.