Fix Wi-Fi or Bluetooth staying off at boot or after resume with TLP installed
Checked on this Omarchy 4.0.2-1 workstation on 2026-09-12 and against the Arch TLP and Power management wiki pages and TLP's own radio and introduction settings pages. What held: the masking advice is the Arch TLP page's own instruction, DEVICES_TO_ENABLE_ON_STARTUP is real and takes wifi and bluetooth, /etc/tlp.d/*.conf is a supported drop-in directory, and the NetworkManager and iwd snippets are copied correctly from the Power management page. rfkill, iw and /var/lib/systemd/rfkill all exist here, rfkill coming from util-linux 2.42.2-1, and the state directory holds one file per radio. What was wrong. First, the Omarchy framing: TLP is not installed and is referenced nowhere in /usr/share/omarchy or in the upstream quattro tree, so the record read as an Omarchy default when TLP is user-added. Second, the NetworkManager advice is redundant on Omarchy 4, which already ships /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf owned by omarchy-settings 4.0.2-1 setting wifi.powersave = 2. Per man 5 NetworkManager.conf on this machine, conf.d files are read in order with later files overriding earlier ones, so the record's powersave.conf does win over omarchy-wifi-powersave.conf on name order, but only by luck, and a numeric-prefixed name such as 00-powersave.conf would silently lose. Third, the verify step names wlan0, which does not exist under predictable naming: this machine's interface is wlo1, and iw dev wlo1 get power_save reports Power save: on despite Omarchy's file, because the interface is down and unassociated and NetworkManager applies wifi.powersave per connection at activation. Fourth, the cause called it a race between TLP and systemd-rfkill, where TLP's own documentation says the two implement identical functionality and names RESTORE_DEVICE_STATE_ON_STARTUP as deprecated since TLP 1.10, with Arch on 1.10.2. Fifth, the danger said hardware kill-switch state, where systemd-rfkill saves the soft block. The record also used systemctl restart tlp.service where TLP documents sudo tlp start. Frequency lowered from common to occasional because on this corpus's primary target the problem cannot occur until the user installs TLP by hand. NOT exercised: I installed nothing, masked nothing and restarted no unit on this workstation, and I have no Wi-Fi association here to test the power_save value on a live link.
Masking systemd-rfkill means the soft block state of each radio is no longer saved across reboots, so a radio you switched off comes back or stays off according to TLP alone. A hardware kill switch is physical and is unaffected either way. Disabling Wi-Fi power saving costs battery life on a laptop.
Symptom
After installing TLP, Wi-Fi is off every time I boot and I have to toggle it on by hand, or Bluetooth never comes back after resume. rfkill list shows the device soft-blocked.
Cause
Two things save and restore radio state, and only one of them can win. systemd-rfkill saves each rfkill switch at shutdown and restores it at boot, keeping the state under /var/lib/systemd/rfkill. On this machine that directory holds pci-0000:00:14.3:wlan and pci-0000:00:14.0-usb-0:14:1.0:bluetooth. TLP does the same job through its radio device switching settings. TLP's own documentation records that Debian and Ubuntu mask systemd-rfkill.service because it implements identical functionality, and the Arch wiki tells every TLP user to mask both the service and the socket to avoid conflicts and to let TLP's radio switching work properly. Whichever one ran last decides the state you get, which is why the radio seems to come back at random.
Separately, TLP does not bring a radio up that Linux left down. DEVICES_TO_ENABLE_ON_STARTUP is unset by default, and RESTORE_DEVICE_STATE_ON_STARTUP, which used to cover this, is deprecated as of TLP 1.10. Arch ships tlp 1.10.2.
None of this is Omarchy's doing. Omarchy 4 does not install TLP and does not reference it anywhere in /usr/share/omarchy or in the upstream quattro tree, so TLP on an Omarchy machine is something you added.
Fix
Mask systemd's rfkill state handling so TLP is the only thing touching the radios:
sudo systemctl mask systemd-rfkill.service systemd-rfkill.socket
Then tell TLP to bring the radios up at boot:
# /etc/tlp.d/00-enable-wifi-at-startup.conf
DEVICES_TO_ENABLE_ON_STARTUP="wifi bluetooth"
sudo tlp start
sudo tlp start is TLP's documented way to apply a config change, alongside a reboot or an AC transition. Mind the read order: /etc/tlp.d/*.conf is read in alphabetical order and /etc/tlp.conf is read last, so an uncommented DEVICES_TO_ENABLE_ON_STARTUP in /etc/tlp.conf beats the drop-in. Every parameter in a stock /etc/tlp.conf is commented out, so the drop-in applies unless you have edited that file.
If latency or dropouts on Wi-Fi are the actual problem, that is Wi-Fi power saving rather than rfkill, and it is a separate setting.
**On Omarchy 4 it is already disabled and you do not need to add anything.** omarchy-settings 4.0.2-1 owns this file:
# /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf
[connection]
wifi.powersave = 2
**On plain Arch**, create it yourself:
# /etc/NetworkManager/conf.d/powersave.conf
[connection]
wifi.powersave=2
sudo systemctl restart NetworkManager
2 means power saving globally disabled. If you do write your own drop-in on Omarchy, mind the file name. NetworkManager reads /etc/NetworkManager/conf.d/*.conf in order and a later file overrides an earlier one, so a name that sorts after omarchy-wifi-powersave.conf wins, and a name that sorts before it, such as 00-powersave.conf, loses to Omarchy's file.
With iwd instead of wpa_supplicant, which is plain Arch only because Omarchy 4 installs neither iwd nor any wifi.backend setting and NetworkManager therefore defaults to wpa_supplicant:
# /etc/iwd/main.conf
[DriverQuirks]
PowerSaveDisable=*
Verify
rfkill list shows no soft block after a reboot. For the power saving check, use the real interface name: Arch and Omarchy use predictable interface names and wlan0 is usually not one of them. On this workstation it is wlo1.
iw dev
iw dev wlo1 get power_save
Run that while the interface is associated. NetworkManager applies wifi.powersave per connection at activation time, so an interface that is down reports the driver default instead. On this machine wlo1 is down and iw dev wlo1 get power_save prints Power save: on even though omarchy-wifi-powersave.conf sets wifi.powersave = 2.