Fix the linux-firmware split: "exists in filesystem" blocks the upgrade
The news item is https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requires-manual-intervention/ (2025-06-21, Jan Alexander Steffens), fetched as HTML. It gives exactly the two commands the record quotes and adds a scope the record omits: the conflict fires only when upgrading from linux-firmware 20250508.788aadc8-2 or earlier, and the four error lines in the symptom are reproduced verbatim from it. The split is confirmed current on this machine: pacman -Q shows linux-firmware 20260810-2 as an empty package depending on linux-firmware-amdgpu, -atheros, -broadcom, -cirrus, -intel, -mediatek, -nvidia, -other, -radeon, -realtek, with -whence installed and liquidio, marvell, mellanox, nfp, qcom, qlogic as optdepends, matching the core/any/linux-firmware JSON and the packaging .SRCINFO. /usr/lib/firmware/nvidia/ad103 through ad107 are symlinks to ad102 owned by linux-firmware-nvidia here, which is the layout change the news describes. Two things were wrong for Omarchy 4. First, the second command, pacman -Syu linux-firmware, is refused by /usr/share/libalpm/hooks/00-omarchy-update-guard.hook, whose /usr/bin/omarchy-update-pacman-guard exits 1 whenever the pacman command line carries both S and u unless OMARCHY_ALLOW_DIRECT_PACMAN=1 or OMARCHY_UPDATE_PACMAN=1 is set (read on this machine). The first command, pacman -Rdd, is a Remove operation and the hook only triggers on Operation = Upgrade, so it runs untouched. Second, routing the reinstall through omarchy update instead would leave the machine without firmware: pacman -Qii linux-firmware shows Required By none and only Optional For linux, so a plain -Syu never pulls it back, and omarchy-update-system-pkgs-when-conflicted only clears exists-in-filesystem lines whose package is omarchy, omarchy-dev, omarchy-settings or omarchy-settings-dev, so omarchy update cannot resolve the linux-firmware-nvidia conflict either. The manual initramfs rebuild is redundant on both platforms: 90-mkinitcpio-install.hook (Omarchy overrides it with /etc/pacman.d/hooks/90-mkinitcpio-install.hook from limine-mkinitcpio-hook, running limine-mkinitcpio-install) triggers on usr/lib/firmware/*, so the transaction rebuilds the initramfs or UKI itself. On Omarchy, mkinitcpio -P goes through the /usr/local/bin/mkinitcpio wrapper, which warns that it does not update Limine entries and offers limine-mkinitcpio. The problem is historical for any install made after June 2025: every Omarchy 4 ISO ships the split already, so a fresh install never sees it, but an older Omarchy or Arch machine that last updated before 2025-06-21 hits it on its next update, and omarchy update reports it as a failed transaction. The remedy itself was not exercised: no machine here has a pre-split linux-firmware to upgrade from.
Between pacman -Rdd linux-firmware and the reinstall your system has NO firmware files in /usr/lib/firmware. Do not reboot, suspend, or let the machine lose power in that window, because you would boot without GPU/Wi-Fi firmware and possibly without a usable display.
Symptom
sudo pacman -Syu refuses to proceed, leaving the system on old firmware (and, if the kernel already updated in a previous partial run, potentially unbootable):
error: failed to commit transaction (conflicting files)
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem
Errors occurred, no packages were upgraded.
Cause
In linux-firmware 20250613.12fe085f-5 (Arch news, 2025-06-21) upstream Arch split the monolithic linux-firmware package into vendor packages (linux-firmware-amdgpu, -atheros, -broadcom, -cirrus, -intel, -mediatek, -nvidia, -other, -radeon, -realtek, plus -whence and optional -liquidio, -marvell, -mellanox, -nfp, -qcom, -qlogic), leaving linux-firmware as an empty package that depends on the default set. The same release picked up upstream's reorganised NVIDIA firmware symlink layout (ad103, ad104, ad106 and ad107 became symlinks to ad102). pacman cannot replace the old directories with the new package's symlinks, so the transaction aborts with conflicting files.
This fires only when the installed linux-firmware is 20250508.788aadc8-2 or older, meaning the machine has not updated since June 2025. Any Arch or Omarchy install made after that date already has the split and never sees it. On Omarchy, omarchy update runs the same pacman -Syu and its conflict handler only clears files under Omarchy's own package names, so the update ends with "Something went wrong during the update" and the firmware conflict printed above it.
Fix
Arch's news item gives the two-step remedy: remove the old package without touching dependents, then reinstall it as part of a full upgrade. Do **not** reboot between the two commands.
**Plain Arch / EndeavourOS / CachyOS:**
sudo pacman -Rdd linux-firmware
sudo pacman -Syu linux-firmware
**Omarchy 4:** the first command is a remove and passes Omarchy's pacman guard, but the second is a -Syu and the guard refuses it. Bypass the guard for that one transaction:
sudo pacman -Rdd linux-firmware
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu linux-firmware
Do not substitute omarchy update for the second step. Nothing depends on linux-firmware (the kernel lists it only as an optional dependency), so a plain system upgrade after -Rdd leaves the machine with no firmware installed. Name the package explicitly.
-Rdd removes the package without checking dependencies and without running its scripts, so the firmware files are absent until the second command completes. The reinstall pulls in the new vendor packages, and the mkinitcpio pacman hook (on Omarchy, limine-mkinitcpio-hook's version, which rebuilds the UKI) triggers on usr/lib/firmware/*, so the initramfs is rebuilt inside the same transaction. Watch for Updating linux initcpios... in the output. Only if that line is missing, rebuild by hand:
sudo mkinitcpio -P # Arch / EndeavourOS / CachyOS
sudo limine-mkinitcpio # Omarchy 4 (mkinitcpio -P alone does not update the Limine UKI)
Verify
pacman -Qs linux-firmware lists the new vendor packages (e.g. linux-firmware-nvidia, linux-firmware-amdgpu, linux-firmware-intel), and sudo pacman -Syu completes with no conflicting-files error.
Sources
- https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requires-manual-intervention/
- https://archlinux.org/news/
- https://archlinux.org/feeds/news/
- https://archlinux.org/packages/core/any/linux-firmware/json/
- https://gitlab.archlinux.org/archlinux/packaging/packages/linux-firmware/-/raw/main/.SRCINFO
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-update-pacman-guard
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-update-system-pkgs
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-update-system-pkgs-when-conflicted