Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Wifi (Intel BE213 on Dell XPS 13) doesn't work out of the box - linux-firmware on install media too old
Reported by anthonylinks · filed Aug 5, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
System details: Dell XPS 13, Intel Wi-Fi 7 BE213 (PCI 8086:4d40, subsystem 8086:4314)
What's wrong?
On a fresh Omarchy install on a Dell XPS 13 with the Intel BE213 Wi-Fi 7 card, Wi-Fi does not work out of the box and stays broken across reboots. dmesg/journalctl -k 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-c100.ucode failed with error -2
iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-bz-b0-wh-b0-102.ucode failed with error -2
iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-bz-b0-wh-b0-101.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-c101Root cause: the install media ships linux-firmware 20260410-1, which doesn't include a bz-b0-wh-b0 ucode in the range BE213's driver will accept. Since there's no other NIC on this laptop, this leaves the machine with zero network — no wifi, no way to pacman -Syu to fix it — a chicken-and-egg problem for anyone without a spare USB-Ethernet adapter or a second machine handy.
What fixed it: sideloading two specific packages from a USB drive and installing them directly with pacman -U (not -Syu, since there was no network on the machine at all at that point):
sudo pacman -U linux-7.1.5.arch1-2-x86_64.pkg.tar.zst
sudo pacman -U linux-firmware-intel-20260622-1-any.pkg.tar.zst...then a reboot, after which:
iwlwifi 0000:00:14.3: loaded firmware version 102.07fca168.0 bz-b0-wh-b0-c102.ucode op_mode iwlmldNote that a regular pacman -Syu run earlier (once temporary network access was available) had already updated every other linux-firmware-* split package to 20260622-1 but left linux-firmware-intel on the original 20260410-1 — that specific subpackage needed to be sideloaded separately to get the fix.
Ask: could Omarchy either (a) bundle a newer linux-firmware/linux-firmware-intel on install media going forward so brand-new Intel Wi-Fi hardware works out of the box, or (b) document this recovery path (get a wired/USB-tethered connection or sideload linux-firmware-intel + a current kernel from another machine) somewhere findable for people who hit a fully wifi-less fresh install? Happy to provide more detail — I have full boot logs from the affected machine.
View raw text
**System details**: Dell XPS 13, Intel Wi-Fi 7 BE213 (PCI `8086:4d40`, subsystem `8086:4314`) **What's wrong?** On a fresh Omarchy install on a Dell XPS 13 with the Intel BE213 Wi-Fi 7 card, Wi-Fi does not work out of the box and stays broken across reboots. `dmesg`/`journalctl -k` 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-c100.ucode failed with error -2 iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-bz-b0-wh-b0-102.ucode failed with error -2 iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-bz-b0-wh-b0-101.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 ``` **Root cause**: the install media ships `linux-firmware` `20260410-1`, which doesn't include a `bz-b0-wh-b0` ucode in the range BE213's driver will accept. Since there's no other NIC on this laptop, this leaves the machine with zero network — no wifi, no way to `pacman -Syu` to fix it — a chicken-and-egg problem for anyone without a spare USB-Ethernet adapter or a second machine handy. **What fixed it**: sideloading two specific packages from a USB drive and installing them directly with `pacman -U` (not `-Syu`, since there was no network on the machine at all at that point): ``` sudo pacman -U linux-7.1.5.arch1-2-x86_64.pkg.tar.zst sudo pacman -U linux-firmware-intel-20260622-1-any.pkg.tar.zst ``` ...then a reboot, after which: ``` iwlwifi 0000:00:14.3: loaded firmware version 102.07fca168.0 bz-b0-wh-b0-c102.ucode op_mode iwlmld ``` Note that a regular `pacman -Syu` run earlier (once temporary network access was available) had already updated every other `linux-firmware-*` split package to `20260622-1` but left `linux-firmware-intel` on the original `20260410-1` — that specific subpackage needed to be sideloaded separately to get the fix. **Ask**: could Omarchy either (a) bundle a newer `linux-firmware`/`linux-firmware-intel` on install media going forward so brand-new Intel Wi-Fi hardware works out of the box, or (b) document this recovery path (get a wired/USB-tethered connection or sideload `linux-firmware-intel` + a current kernel from another machine) somewhere findable for people who hit a fully wifi-less fresh install? Happy to provide more detail — I have full boot logs from the affected machine.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 03:58 UTC