Re: How to diagnose Bluetooth trouble?

[Ignas Lapėnas]

> bluetoothctl power on
>
> produces the error message "No default controller available"
>
> and
>
> bluetoothctl list
>
> comes up blank.
>
> I've checked with lsmod, and the bluetooth kernel module is loaded.
>
> What's the next move, please?

Most information I could find is summarized here:

https://wiki.archlinux.org/title/Bluetooth#bluetoothctl:_No_default_controller_available

Since you're with guix, journalctl command should be replaced with
something like this.

sudo cat /var/log/messages | grep hci

to check if you're blocked by rfkill the command should simply be rfkill

-- 
Hope that helps,
Ignas