OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
power-suspend medium very-common DISPUTE

Bring Bluetooth back when the adapter disappears after suspend

omarchyarchendeavouroscachyosmanjarolaptopintelmediatekbluetooth
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The escalation ladder is sound and mostly wiki-backed: btusb.enable_autosuspend=n, the modprobe -r/modprobe btusb cycle, and the rfkill check are all on wiki.archlinux.org/title/Bluetooth. bin/omarchy-restart-bluetooth is indeed just rfkill unblock bluetooth plus a listing (the record describes it correctly, unlike its own menu label). The Update > Hardware > Bluetooth mapping is confirmed in the menu JSON. usb_modeswitch and the Limine persistence step are correct. Three fixes needed. (1) Step 2 is stale as a *fix*: the Bluetooth page says 'As of bluez 5.65, BlueZ' default behavior is to power on all Bluetooth adapters when starting the service or resuming from suspend'. AutoEnable=true has been the default for years, so writing it changes nothing. It is only worth checking whether something set it to false. (2) Step 6's xhci_hcd unbind/bind is genuinely dangerous with no warning: unbinding the controller drops every USB device on it, including the keyboard and mouse, and any USB storage, mid-write. (3) The Arch wiki's targeted TLP fix for exactly the quoted hci0: link tx timeout symptom is USB_DENYLIST with the adapter's ID, which is far less costly than disabling USB autosuspend machine-wide.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

Step 6's xhci_hcd unbind disconnects EVERY device on that controller, your keyboard and mouse included, and any mounted USB storage, which risks filesystem damage. Unmount USB drives first (sudo umount /run/media/$USER/*) and run it from an SSH session or on a laptop with a built-in keyboard on a different controller. Disabling USB autosuspend system-wide (USB_AUTOSUSPEND=0) measurably increases idle battery drain.

Symptom

Bluetooth works until the first suspend. After resume the icon is gone and:


$ bluetoothctl show
No default controller available

The adapter isn't in lsusb any more either. It's as if someone unplugged it. dmesg shows Bluetooth: hci0: command 0x1001 tx timeout or hci0: link tx timeout. Only a full reboot brings it back.

Cause

Two different things wearing the same face. Either bluez lost the adapter and just needs re-powering (AutoEnable, rfkill soft-block restored on resume), or (the harder case) the btusb USB device genuinely failed to re-enumerate on the xHCI bus after resume, usually because of USB autosuspend on the controller. Common on Intel AX200/AX201/AX211 and MediaTek MT7921/MT7922 combo cards. There is also a distinct bluez-5.80 regression where already-paired LE devices reconnect with a different address and fail to re-pair.

Fix

Replace step 2 with:

**2. Confirm nothing disabled auto-power-on.** Since bluez 5.65 BlueZ powers on every adapter when the service starts *and* on resume from suspend, so this is already the default. You only need to check that it was not turned off:


grep -r -i autoenable /etc/bluetooth/

If you find AutoEnable=false, set it back (or delete the line):


# /etc/bluetooth/main.conf
[Policy]
AutoEnable=true

sudo systemctl restart bluetooth.service

In step 4, prefer the targeted TLP setting over the global one. The Arch Bluetooth/TLP pages document USB_DENYLIST for precisely this link tx timeout symptom. Get the ID from lsusb:


# /etc/tlp.d/20-bluetooth.conf
USB_DENYLIST="8087:0026"

Use USB_AUTOSUSPEND=0 only if the denylist entry does not hold.

In step 6, add before the controller rebind:

> **Warning.** Unbinding xhci_hcd drops *every* device on that controller at once: USB keyboard, mouse, dock, and any attached USB storage (unmount it first). Run this over SSH, or from a laptop's built-in (non-USB) keyboard, and never while the root filesystem or /home lives on USB. Identify which controller owns the adapter with lsusb -t before picking a PCI address, and confirm it is not the one your input devices are on.

Verify

sudo systemctl suspend, wake, then bluetoothctl show prints a controller with Powered: yes, lsusb still lists the adapter, and sudo journalctl -b -k | grep -i bluetooth has no tx timeout. Repeat three cycles. This failure is often intermittent on the first cycle only.

Sources

bluetooth-dead-after-resume