Fix bluetoothctl reporting No default controller available
Re-audited on this Omarchy 4 workstation (omarchy 4.0.2-1, omarchy-settings 4.0.2-1, bluez 5.87-2, util-linux 2.42.2-1, kernel 7.1.9), which does have a working adapter: rfkill list shows 0: hci0: Bluetooth unblocked, bluetoothctl list shows one controller, bluetoothctl show reports Powered: yes, and systemctl status bluetooth shows the unit enabled and running. The Arch wiki Bluetooth page was refetched and its "bluetoothctl: No default controller available" section (around line 788 of the raw wikitext) does support the record's cold-power-cycle and btusb.enable_autosuspend=n claims, so the source audit was right. Two things are wrong for Omarchy 4. First and worst, the bootloader advice names two bootloaders Omarchy 4 does not have: pacman -Q grub systemd-boot reports neither is installed, /etc/default/grub does not exist, and /boot/loader/entries is not a thing on this machine. Omarchy 4 boots a UKI through Limine and the kernel cmdline comes from drop-ins under /etc/limine-entry-tool.d/, confirmed by reading omarchy-defaults.conf there and matching it against /proc/cmdline. A reader following the record on Omarchy would edit a file that does not exist and conclude the fix does not work. Replaced the primary route with /etc/modprobe.d/, which is bootloader independent and verified here: zgrep CONFIG_BT_HCIBTUSB /proc/config.gz gives =m, lsmod shows btusb loaded, and modinfo btusb lists enable_autosuspend:Enable USB autosuspend by default (bool). Second, the record misses the single most Omarchy-specific cause. Omarchy 4 stores the Bluetooth on/off state as an rfkill soft block on purpose: /usr/share/omarchy/bin/omarchy-bluetooth-power does rfkill block and rfkill unblock and its own comments state that a plain bluetoothctl power on fails while the block is set, and Panel.qml line 637 in the shell's Bluetooth panel invokes it. So on Omarchy the recovery is omarchy-bluetooth-power on or the menu's omarchy-restart-bluetooth, which is literally rfkill unblock bluetooth. Also corrected two smaller things: sudo systemctl enable --now bluetooth.service is a no-op on Omarchy 4 because /usr/share/omarchy/install/hardware/bluetooth.sh already enables it, and the record's ordering mixed diagnosis with remediation, so the fix now separates a read-only diagnostic block from the actions and says which reading points at which cause. One accuracy fix to the cause: an rfkill soft block usually leaves the controller listed with Powered: no rather than producing "No default controller available", so it is worth checking but is not the usual cause of that exact string. Left severity high and frequency common alone. NOT exercised: nothing was paired, connected, blocked, unblocked or restarted, and no module was unloaded, so the modprobe -r btusb and cold power cycle steps were verified from module metadata and the wiki, not run. I could not read /boot to check whether btusb is bundled into the initramfs, because /boot is a vfat ESP mounted dmask=0077 and I did not use sudo. If it were bundled, the modprobe drop-in would also need a UKI rebuild, but btusb is not a boot-critical module and the autodetect plus modconf hooks in /etc/mkinitcpio.conf.d/omarchy_hooks.conf would not normally pull it in.
sudo modprobe -r btusb drops every connected Bluetooth device at once. If you are using a Bluetooth keyboard or mouse, you lose the input you are typing on, so have a wired fallback attached first. The kernel command line branch touches boot configuration: on Omarchy 4 that is a drop-in under /etc/limine-entry-tool.d/ feeding a rebuilt UKI, and a typo there can leave the machine unbootable. Prefer the /etc/modprobe.d/btusb-autosuspend.conf file, which needs no rebuild and cannot affect boot. Check cat /proc/cmdline after the next boot if you take the kernel parameter route.
Symptom
bluetoothctl says No default controller available, the Bluetooth toggle in the panel does nothing, and bluetoothctl scan on errors with org.bluez.Error.NotReady. journalctl | grep hci may show command tx timeout or Reading Intel version command failed.
Cause
Four different faults produce the same message, and they need different fixes.
- **The kernel never bound a controller.**
btusb(or the PCI/UART driver for the part) did not load, or it loaded and the firmware blob it wants is missing./sys/class/bluetoothis then empty and bluetoothd has nothing to offer, so bluetoothctl reports no default controller. - **The controller firmware wedged.** Common on Intel combo Wi-Fi/Bluetooth cards, and notoriously after dual booting Windows, which leaves the part in a state a warm reboot does not clear. The journal shows
command tx timeoutorReading Intel version command failed. - **bluetoothd is not running.** On plain Arch
bluetooth.serviceis not enabled by default. On Omarchy 4 it is:/usr/share/omarchy/install/hardware/bluetooth.shrunssystemctl enable bluetooth.serviceat install, so this cause is usually already excluded there. - **An rfkill block.** This one normally presents differently. A soft block leaves the controller listed by
bluetoothctl listwithPowered: no, andbluetoothctl power onfails rather than the controller vanishing. It matters on Omarchy 4 because the rfkill block **is** how Omarchy stores the Bluetooth on/off state:/usr/share/omarchy/bin/omarchy-bluetooth-powerblocks and unblocks, the shell's Bluetooth panel calls it (/usr/share/omarchy/shell/plugins/panels/bluetooth/Panel.qml), and systemd-rfkill restores the block on the next boot from/var/lib/systemd/rfkill. So Bluetooth staying off across reboots on Omarchy is deliberate, not a fault.
Fix
**Diagnose before you fix.** These commands separate the four causes and none of them change anything:
ls /sys/class/bluetooth # expect hci0. Empty means the kernel bound nothing
bluetoothctl list # controllers bluetoothd knows about
rfkill list bluetooth # rfkill ships in util-linux, there is no separate package
systemctl status bluetooth.service
lsmod | grep -E 'btusb|btintel|bluetooth'
journalctl -b -k | grep -i -E 'hci|bluetooth|firmware'
Read them like this:
/sys/class/bluetoothempty **and** nobtusbinlsmod: the driver never bound. Find the part withlsusborlspci -nn | grep -i blue, then look in the journal for aDirect firmware load ... failedline naming the blob it wanted.- Controller listed,
bluetoothctl showsaysPowered: no,rfkill list bluetoothsaysSoft blocked: yes: a block, not a broken adapter. - Journal shows
command tx timeoutorReading Intel version command failed: the controller firmware is wedged, and no software fix will clear it.
**Clear a block.** On Omarchy 4 go through Omarchy's wrapper, because BlueZ refuses bluetoothctl power on while a block is set:
omarchy-bluetooth-power on # rfkill unblock, then wait for bluetoothd to power the adapter
omarchy-restart-bluetooth # what the Omarchy menu runs: rfkill unblock bluetooth, then show the state
On plain Arch:
sudo rfkill unblock bluetooth
bluetoothctl power on
**Start the service.** Only needed on plain Arch, since Omarchy 4 enables it at install:
sudo systemctl enable --now bluetooth.service
**Reload the driver** when the adapter is present but dead:
sudo modprobe -r btusb
sudo modprobe btusb
sudo systemctl restart bluetooth.service
**Cold power cycle** when the journal showed command tx timeout or Reading Intel version command failed. A reboot will not fix it. Shut down, unplug the power cable (and remove the battery if it is removable) for about 30 seconds, then boot. That is what forces the controller to reload its firmware.
**If the adapter disappears after suspend or after USB autosuspend**, turn autosuspend off for btusb with a modprobe drop-in rather than a kernel parameter. btusb is a module on the Arch kernel (CONFIG_BT_HCIBTUSB=m) and modinfo btusb lists enable_autosuspend as a bool, so this works whatever the bootloader is and cannot break boot:
printf 'options btusb enable_autosuspend=n\n' | sudo tee /etc/modprobe.d/btusb-autosuspend.conf
sudo modprobe -r btusb && sudo modprobe btusb
That file sits alongside /usr/lib/modprobe.d/bluetooth-usb.conf, which bluez ships with options btusb reset=1. Leave the bluez file alone, it is package owned.
If you would rather set it on the kernel command line, use the bootloader the machine actually has.
- **Omarchy 4** boots a unified kernel image through Limine. There is no
/boot/loader/entriesand no/etc/default/grub. Add a drop-in, whichlimine-entry-toolreads when the UKI is rebuilt:
# /etc/limine-entry-tool.d/99-btusb.conf
KERNEL_CMDLINE[default]+=" btusb.enable_autosuspend=n"
The rebuild happens on the next kernel or mkinitcpio update through /etc/pacman.d/hooks/90-mkinitcpio-install.hook. Confirm with cat /proc/cmdline after the next boot.
- **systemd-boot**: add it to the
optionsline of/boot/loader/entries/*.conf. - **GRUB**: add it to
GRUB_CMDLINE_LINUX_DEFAULTin/etc/default/grub, then runsudo grub-mkconfig -o /boot/grub/grub.cfg.
Verify
bluetoothctl list # prints a Controller line
bluetoothctl show | grep Powered # Powered: yes
rfkill list bluetooth # Soft blocked: no, Hard blocked: no
Then bluetoothctl scan on discovers nearby devices. On Omarchy 4, omarchy-bluetooth-power is-on exits 0 when any controller is powered, which is the check Omarchy's own panel uses. If you added the modprobe drop-in, confirm it took with:
cat /sys/module/btusb/parameters/enable_autosuspend # expect N