OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network critical common DISPUTE

Restore Wi-Fi after an upgrade leaves NetworkManager pointing at a removed iwd backend

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

Cause is verified: omarchy migrations/1786567036.sh does exit early unless wpa_supplicant.service is literally masked ([[ $state == masked* ]] || exit 0), and install/hardware/network.sh only does systemctl disable iwd.service. But the fix greps only /etc/NetworkManager/conf.d/ while wifi.backend is equally often set in /etc/NetworkManager/NetworkManager.conf itself or in /usr/lib/NetworkManager/conf.d/, and it then hardcodes mv .../wifi_backend.conf{,.bak} which aborts with 'No such file' on the installs where the drop-in is named 10-iwd-backend.conf. It also never verifies wpa_supplicant can actually be D-Bus-activated.

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

Deleting rather than renaming the drop-in loses any other device settings it contained. Keep the .bak until Wi-Fi is confirmed working.

Symptom

After upgrading Omarchy to Quattro (4.x) there is no Wi-Fi at all. The Wi-Fi icon/panel shows nothing, and nmcli device status shows the wireless device stuck at unavailable forever:


DEVICE   TYPE   STATE         CONNECTION
wlp2s0   wifi   unavailable   --

systemctl status iwd says Unit iwd.service could not be found. Meanwhile the kernel log is perfectly healthy: iwlwifi ... loaded firmware version ..., base HW address: ..., no rfkill block, WIFI-HW enabled, WIFI enabled.

Cause

Older Omarchy (2.x/3.x) drove Wi-Fi with iwd and dropped a NetworkManager config fragment selecting it as the Wi-Fi backend (/etc/NetworkManager/conf.d/wifi_backend.conf or 10-iwd-backend.conf, filename varies by era). The Quattro migration removes the iwd package but the drop-in survives, so NetworkManager is configured to use a backend daemon that no longer exists on disk. Every Wi-Fi device therefore sits at unavailable. The shipped migration only fires when wpa_supplicant.service is *masked*. On installs where it was merely disabled, the migration exits early and records itself as applied.

Fix


# 1. Find every place the backend can be pinned, not just conf.d
grep -rn 'wifi\.backend' /etc/NetworkManager/ /usr/lib/NetworkManager/ 2>/dev/null

# 2. Move aside whichever drop-in(s) matched, by their real names
for f in $(grep -rls 'wifi\.backend' /etc/NetworkManager/conf.d/ 2>/dev/null); do
  sudo mv -v "$f" "$f.bak"
done
# If the setting is in /etc/NetworkManager/NetworkManager.conf instead, comment it out:
sudo sed -i 's/^\s*wifi\.backend\s*=/#&/' /etc/NetworkManager/NetworkManager.conf

# 3. Make sure the supplicant is installed and unmasked (NM D-Bus-activates it)
pacman -Q wpa_supplicant || sudo pacman -Syu --needed wpa_supplicant
sudo systemctl unmask wpa_supplicant.service
sudo systemctl unmask --runtime wpa_supplicant.service 2>/dev/null || true

sudo systemctl restart NetworkManager
nmcli device status

Only if a saved profile is still pinned to the old iwd-era interface name:


nmcli -g NAME,TYPE connection show | grep wifi
sudo nmcli connection modify "<profile>" connection.interface-name ""
sudo nmcli connection up "<profile>"

Verify

nmcli device status shows the Wi-Fi device as disconnected (not unavailable), and nmcli device wifi list returns access points. systemctl status wpa_supplicant shows it D-Bus activated on demand.

Sources

nm-wifi-backend-iwd-orphaned-after-quattro