Stop Wi-Fi dropping every few minutes by disabling power save
The fix is work Omarchy 4 already does, which the record does not mention. Confirmed on this machine: /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf exists, pacman -Qo reports it owned by omarchy-settings 4.0.2-1, it contains [connection] with wifi.powersave = 2, and NetworkManager --print-config reports wifi.powersave=2 as the effective value on networkmanager 1.58.1-1. It is also in upstream v4.0.3 at etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf, so it is not a local artefact. /usr/share/omarchy/migrations/1784914435.sh additionally runs iw dev <iface> set power_save off on every wireless interface, and its own comment states why: NetworkManager applies wifi.powersave only when a connection activates. That matches what I measured, iw dev wlo1 get power_save prints Power save: on on this machine despite the drop-in, because wlo1 is disconnected. The record's verify step would therefore read as a failure on a correctly configured machine.
Load order is wrong in the record and confirmed wrong here. NetworkManager --print-config lists its conf.d files as {20-omarchy-dns.conf, omarchy-wifi-powersave.conf}, and NetworkManager.conf(5) says later files override earlier ones, so the record's 20-wifi-powersave.conf is read before the package file and loses to it. Harmless while both set 2, but the record is teaching a name that cannot win. I also checked pacman -Qii omarchy-settings: that conf is not in the backup list, so editing it in place is overwritten on upgrade with no .pacnew, which the record's danger field does not cover. A second mechanism the record misses is that nm-settings-nmcli(5) defines 802-11-wireless.powersave as default (0), ignore (1), disable (2), enable (3), and NetworkManager.conf(5) states a [connection] default is only consulted when the per-profile property asks for it, so a profile saved with 3 defeats any drop-in. That is the one way this still bites a stock Omarchy 4 machine, and the record does not mention it.
wlan0 does not exist on Omarchy 4. Confirmed on this machine, the only wireless interface is wlo1, with no net.ifnames=0 on the kernel cmdline, so both the live test and the verify command as written fail outright. The Intel modprobe advice is half dead. modinfo -p iwlwifi on kernel 7.1.9 shows power_save with default: disable, so power_save=0 is a no-op, and a GitHub code search of torvalds/linux master finds iwlwifi_mod_params.power_save read only in drivers/net/wireless/intel/iwlwifi/dvm/mac80211.c, meaning iwldvm 5000 and 6000 series cards only. options iwlmvm power_scheme=1 is real, confirmed consumed in mvm/power.c and mvm/mac80211.c, but kernel 7.1.9 also ships iwlmld for BE200 class parts, and modinfo -p iwlmld reports its own power_scheme with values 1-active and 2-balanced. The record names only iwlmvm, so the exact hardware Omarchy's drop-in comment calls out is the hardware it misses.
Both cited GitHub URLs are dead and neither issue supports the cause. https://github.com/basecamp/omarchy/issues/3882 and .../2925 both return HTTP 404 to curl -sL, because the repo is now omacom/omarchy. Read in full with gh issue view 3882 -R omacom/omarchy --comments: the body is the record's symptom verbatim on Omarchy 3.2.2, but the thread converges on Portmaster, on NetworkManager and systemd-networkd both running, and on several users saying the problem started when they installed NetworkManager at all. One comment offers sudo iw dev wlan0 set power_save off with nobody confirming it, and another user states that disabling power save did not work. Issue 2925 is a different problem entirely, network dead after suspend, with DNS, tailscaled and NordVPN named, and one commenter merely proposing to try power save without ever reporting a result. Both threads are Omarchy 3, which shipped iwd, so the record's NetworkManager fix did not even apply to those machines. iwd is not installed here and systemd-networkd is disabled and inactive. I am keeping 3882 under its omacom URL because it is the source of the symptom text and removing both would leave the record with only a man page, and dropping 2925, which supports nothing the record claims.
Frequency drops from very-common to occasional, because on Omarchy 4 the distribution already applies the fix and only an overriding per-connection value or a removed drop-in can reproduce it. Severity stays medium. Not exercised: this workstation has an Intel Wireless-AC 9560 CNVi part (8086:a370, subsystem 8086:0034, driver iwlwifi) but wlo1 is down and the machine runs on eno2, and I was told not to change any NetworkManager or radio state, so I did not associate, did not measure any disconnect rate, and did not test any modprobe option or reboot.
Turning Wi-Fi power save off costs idle battery, though the amount is small. Omarchy's own drop-in describes the trade as a fraction of a watt against 20 to 300 ms latency spikes on an idle link.
Two traps matter more than the power. Do not edit /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf in place: it belongs to omarchy-settings and is not a pacman backup file, so the next upgrade overwrites the edit without producing a .pacnew and your change disappears with no warning. And if you add your own drop-in, check where its name sorts. NetworkManager reads conf.d/*.conf in filename order with later files winning, so a numeric prefix such as 20- loses to omarchy-wifi-powersave.conf and silently has no effect.
Symptom
"Every 5 or so minutes, my wifi disconnects, no matter what WiFi I'm on." The connection reassociates by itself after a delay, or needs a manual reconnect. It is worse on battery, and on phone hotspots the drop happens most often while the screen is idle. On a stock Omarchy 4 install this is unlikely to be power save, because Omarchy already ships a NetworkManager drop-in that turns power save off. Reach for this record on plain Arch, or on Omarchy only after checking that something has overridden that drop-in or that a per-connection setting is defeating it.
Cause
With no configuration, NetworkManager leaves wifi.powersave at ignore and the driver default stands, which on most Intel, Realtek and MediaTek parts means 802.11 power save is on. The radio sleeps between beacons, and access points with aggressive client timeouts, phone hotspots especially, age the station out so the driver has to reassociate.
Two things change that picture on Omarchy 4. First, omarchy-settings installs /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf with wifi.powersave = 2, so power save is already off out of the box and this cause is already handled. Second, NetworkManager only consults that global default when the connection profile's own 802-11-wireless.powersave is 0 (default). A profile saved with 3 (enable) or 1 (ignore) beats the drop-in, which is the remaining way a stock Omarchy 4 machine can still suffer this.
Fix
First check whether the machine already has this handled. On Omarchy 4 it does:
cat /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf
pacman -Qo /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf
NetworkManager --print-config | sed -n '/^\[connection\]/,/^$/p'
If wifi.powersave=2 is already the effective value, stop. Adding another drop-in changes nothing and the cause is elsewhere.
Find the real interface name. Omarchy 4 uses predictable names such as wlo1 or wlp3s0, and wlan0 does not exist:
for w in /sys/class/net/*/wireless; do basename "$(dirname "$w")"; done
iw dev | awk '/Interface/ {print $2}'
Use that name everywhere below in place of wlo1.
Check the per-connection value, because it overrides the global default unless it is 0:
nmcli -g NAME connection show --active
nmcli -g 802-11-wireless.powersave connection show "<profile>"
0 is default (use the global value), 1 is ignore, 2 is disable, 3 is enable. Anything other than 0 is what you need to change:
sudo nmcli connection modify "<profile>" 802-11-wireless.powersave 2
sudo nmcli connection up "<profile>"
**Plain Arch, or Omarchy where the shipped drop-in has been removed.** Add a drop-in whose name sorts after any existing one, because NetworkManager reads /etc/NetworkManager/conf.d/*.conf in filename order and later files win. A file called 20-wifi-powersave.conf sorts before omarchy-wifi-powersave.conf and would lose to it:
sudo tee /etc/NetworkManager/conf.d/zz-wifi-powersave.conf >/dev/null <<'EOF'
[connection]
wifi.powersave = 2
EOF
sudo nmcli general reload conf
Do not edit /etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf itself. It is owned by omarchy-settings and is not in that package's backup list, so an upgrade overwrites your edit silently and leaves no .pacnew behind.
NetworkManager applies wifi.powersave only when a connection activates, so the running session needs one more step. Omarchy's own migration at /usr/share/omarchy/migrations/1784914435.sh does exactly this:
sudo iw dev wlo1 set power_save off
That is not persistent by itself. It is a live test and a way to settle the current session, not the fix.
**Intel driver level, only if the NetworkManager route did not help.** Identify which Intel driver the card uses first, because the parameter differs and two of the three commonly cited options do nothing:
basename "$(readlink -f /sys/class/net/wlo1/device/driver)"
ls /sys/module | grep -E '^iwl(mvm|mld|dvm)$'
For iwlmvm (7260 and newer through AX210):
sudo tee /etc/modprobe.d/iwlwifi-power.conf >/dev/null <<'EOF'
options iwlmvm power_scheme=1
EOF
sudo reboot
For iwlmld, which kernel 7.1 uses for BE200 class cards, the parameter lives on that module instead and accepts only 1 (active) or 2 (balanced):
sudo tee /etc/modprobe.d/iwlwifi-power.conf >/dev/null <<'EOF'
options iwlmld power_scheme=1
EOF
sudo reboot
Do not bother with options iwlwifi power_save=0. Its default is already false, and the only in-tree consumer is drivers/net/wireless/intel/iwlwifi/dvm/mac80211.c, so it reaches nothing newer than the 5000 and 6000 series cards.
Verify
Read the effective NetworkManager value, which does not depend on being connected:
NetworkManager --print-config | sed -n '/^\[connection\]/,/^$/p'
nmcli -g 802-11-wireless.powersave connection show "<profile>"
Then check the radio itself, but only while the link is up, because NetworkManager applies the setting on activation and a disconnected interface still reports the driver default:
iw dev wlo1 link # must show a connected BSS first
iw dev wlo1 get power_save # expect: Power save: off
Finally, count the drops over a long idle period rather than grepping for a word that appears in routine log lines:
journalctl -u NetworkManager --since '2 hours ago' \
| grep -cE 'state change: (activated|ip-config) -> (deactivating|disconnected)'
Sources
- https://man.archlinux.org/man/NetworkManager.conf.5
- https://github.com/omacom/omarchy/issues/3882
- https://github.com/omacom/omarchy/blob/v4.0.3/etc/NetworkManager/conf.d/omarchy-wifi-powersave.conf
- https://man.archlinux.org/man/nm-settings-nmcli.5
- https://raw.githubusercontent.com/torvalds/linux/master/drivers/net/wireless/intel/iwlwifi/iwl-drv.c
- https://raw.githubusercontent.com/torvalds/linux/master/drivers/net/wireless/intel/iwlwifi/iwl-modparams.h
- https://raw.githubusercontent.com/torvalds/linux/master/drivers/net/wireless/intel/iwlwifi/mvm/power.c