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

Fix a brand-new Intel Wi-Fi card that finds no usable firmware

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

Read omacom/omarchy issue 6551 in full. It supports the symptom, the chicken-and-egg cause and the sideload recovery, and it is the record's only source. Three defects, two of them Omarchy-specific. First, sudo pacman -Syu linux linux-firmware linux-firmware-intel cannot run on Omarchy 4. I read /usr/share/libalpm/hooks/00-omarchy-update-guard.hook and /usr/bin/omarchy-update-pacman-guard on this machine: the hook is PreTransaction with AbortOnFail, and the script aborts any pacman command line carrying both a sync and a sysupgrade flag, so the record's headline fix is refused. Second, sudo mkinitcpio -P fails hard here. /etc/mkinitcpio.d/ is empty on this install and mkinitcpio 41.1-1 line 986 reads [[ -e "${_optpreset[0]}" ]] || die 'No presets found in %s', so the command dies rather than rebuilding anything. The step is also unnecessary on plain Arch: the only initramfs MODULES on Omarchy come from /etc/mkinitcpio.conf.d/ and are nvidia* plus thunderbolt, no iwlwifi, and Wi-Fi firmware is read from the mounted root after the initramfs has handed off. The rebuild is driven by the pacman hook /etc/pacman.d/hooks/90-mkinitcpio-install.hook, owned by limine-mkinitcpio-hook 1.37.1-1, when the kernel package is installed. Third, the danger field's remedy was run a full pacman -Syu, which is the blocked command, so the danger was telling the reader to do the thing the guard refuses. Confirmed on this machine: linux-firmware 20260810-2 is a metapackage and linux-firmware-intel 20260810-2 is a separate package that owns /usr/lib/firmware/iwlwifi-bz-b0-wh-b0-c102.ucode.zst, the exact ucode the reporter ended up loading, so the split-package advice is right and current. From the Arch package API, linux-firmware in core is 20260910-1 and depends on twelve linux-firmware-* splits including -intel, which is 139 MB compressed. The record's version-pinned sideload filenames were the reporter's from August and are now stale, so the fix now shows current versions and how to look them up. I kept and made explicit the point the record had right and that matters: the ucode that worked, c102, is ABOVE the old driver's stated maximum of c101, so a newer kernel and newer firmware are both required and firmware alone would have been rejected. I qualified the claim that a pacman -Syu left linux-firmware-intel behind: that is one reporter's observation on one machine and is not how a full upgrade behaves, per the Arch wiki on partial upgrades, so the fix now says to check the installed version rather than presenting it as expected behaviour. Frequency moved from common to occasional: upstream labelled the issue device specific, it has zero comments, and it needs install media older than a just-released card plus no second NIC. Severity stays critical because a fresh install has no network at all. Cited URL replaced: the basecamp/omarchy/issues/6551 path returned 404 on two of three attempts before redirecting once, so it is not a reliable citation and the canonical omacom URL replaces it. NOT exercised: I have no BE213 card and did not install, sideload, reboot or run mkinitcpio here, so the recovery path itself is from the issue and from reading the guard and mkinitcpio sources, not from a live run.

The cause above was rewritten on 2026-09-11 to match this note; the fix was corrected by the audit itself.
RISK

Installing single packages with pacman -U from a stale snapshot is a partial upgrade. A kernel installed that way also replaces the module tree under /usr/lib/modules, so the running kernel loses its modules and anything not already loaded will fail to load until you reboot. Install the kernel and its firmware in one transaction, reboot straight away, then take a full upgrade as soon as you have real network: omarchy update on Omarchy, sudo pacman -Syu on plain Arch. Never reach for pacman -Sy linux-firmware-intel, which is a partial upgrade in its own right.

Symptom

Fresh install on new hardware (e.g. Dell XPS 13 with Intel Wi-Fi 7 BE213) has no Wi-Fi at all, across reboots. journalctl -k | grep iwlwifi shows:


iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 7 BE213 160MHz
iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-bz-b0-wh-b0-c101.ucode failed with error -2
iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-bz-b0-wh-b0-100.ucode failed with error -2
iwlwifi 0000:00:14.3: no suitable firmware found!
iwlwifi 0000:00:14.3: minimum version required: iwlwifi-bz-b0-wh-b0-100
iwlwifi 0000:00:14.3: maximum version supported: iwlwifi-bz-b0-wh-b0-c101

Cause

The linux-firmware-intel split package on the install media predates the ucode revision the running iwlwifi driver will accept for that card. Firmware acceptance is a range and both ends move. The driver declares a minimum and a maximum version it will load, and on the reported machine the ucode that eventually worked, iwlwifi-bz-b0-wh-b0-c102.ucode, sits ABOVE the old driver's stated maximum of c101. That is why a newer kernel and newer firmware are both needed and newer firmware alone is not enough. With no second NIC in the laptop this is a chicken-and-egg problem: there is no network to fetch either package over. linux-firmware is a metapackage that depends on twelve linux-firmware-* split packages, and the Intel one is a separate 139 MB download, so it can lag behind the rest on a mirror. The original reporter saw one pacman -Syu update every other split and leave linux-firmware-intel behind. A full upgrade should not do that, so treat it as a single unexplained observation and check the installed version directly rather than assuming the upgrade covered it.

Fix

Get any temporary network first. A USB Ethernet dongle works, or USB tethering from a phone (Settings > Personal Hotspot > USB on iOS), where the phone appears as a usb0 or enp0s... device that NetworkManager will DHCP automatically. Then take a full upgrade, which pulls the new kernel and the new firmware together.

On Omarchy:


omarchy update

On plain Arch, EndeavourOS or CachyOS:


sudo pacman -Syu

Do NOT run sudo pacman -Syu linux linux-firmware linux-firmware-intel on Omarchy. An ALPM hook aborts any pacman command line carrying both a sync and a sysupgrade flag:


Woah partner...

This looks like a direct pacman system upgrade. Omarchy updates should normally
run through:

  omarchy update

If you genuinely need to bypass it for one transaction:


sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu

With no network at all, download a matching kernel and firmware pair on another machine and install them in ONE transaction, so the initramfs and boot entry are rebuilt once against a consistent set:


sudo pacman -U \
  /run/media/$USER/USB/linux-7.1.9.arch1-2-x86_64.pkg.tar.zst \
  /run/media/$USER/USB/linux-firmware-intel-20260910-1-any.pkg.tar.zst
sudo reboot

Use whatever versions are current rather than the ones above, and check on the machine doing the downloading:


curl -s https://archlinux.org/packages/core/any/linux/json/ | grep -o '"pkgver": "[^"]*"'
curl -s https://archlinux.org/packages/core/any/linux-firmware-intel/json/ | grep -o '"pkgver": "[^"]*"'

Do not run sudo mkinitcpio -P afterwards. On Omarchy 4 /etc/mkinitcpio.d/ is empty, so it dies with ==> ERROR: No presets found in /etc/mkinitcpio.d and rebuilds nothing. It is unnecessary on plain Arch too. Installing the kernel package fires /etc/pacman.d/hooks/90-mkinitcpio-install.hook, which on Omarchy comes from limine-mkinitcpio-hook and rebuilds the UKI, and Wi-Fi firmware is not in the initramfs in any case because iwlwifi is read from the mounted root long after the initramfs has handed off.

Verify


journalctl -k | grep iwlwifi
nmcli device wifi list
pacman -Q linux linux-firmware-intel

The kernel log carries a loaded line in place of no suitable firmware found!, for example iwlwifi 0000:00:14.3: loaded firmware version 102.07fca168.0 bz-b0-wh-b0-c102.ucode op_mode iwlmld, nmcli device wifi list returns networks, and pacman -Q linux-firmware-intel shows the version you installed rather than the one from the install media.

Sources

iwlwifi-no-suitable-firmware-new-intel-card