OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
pacman-aur high common DISPUTE

Fix the linux-firmware-nvidia file conflict during an upgrade

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

The cited news item is real and is the right one: https://archlinux.org/news/linux-firmware-2025061312fe085f-5-upgrade-requires-manual-intervention/ (2025-06-21, Jan Alexander Steffens), listed on https://archlinux.org/news/ and fetched as HTML. It confirms the split in 20250613.12fe085f-5, the 20250508.788aadc8-2 or earlier floor, the four ad103 to ad107 error lines verbatim, and the two-command remedy, so symptom and cause hold. The split is current on this machine: pacman -Q shows linux-firmware 20260810-2 as an empty package whose Depends On lists the ten vendor packages, pacman -Qii linux-firmware shows Required By none and Optional For linux, and ls -l /usr/lib/firmware/nvidia/ shows ad103, ad104, ad106 and ad107 as symlinks to ad102 owned by linux-firmware-nvidia, which is the layout change that makes pacman abort. The fix is wrong for Omarchy 4. Read on this machine, /usr/share/libalpm/hooks/00-omarchy-update-guard.hook fires on Operation = Upgrade, PreTransaction, AbortOnFail, and /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, so the second command, sudo pacman -Syu linux-firmware, is refused on a machine that has anything else to upgrade, which by definition this one has. The first command, pacman -Rdd, is a Remove operation the hook never triggers on, so it passes. Routing the second step through omarchy update instead would leave the machine with no firmware, because nothing requires linux-firmware and a plain -Syu does not reinstall a removed optional dependency. The manual mkinitcpio -P is redundant on both platforms (the initramfs hook, on Omarchy /etc/pacman.d/hooks/90-mkinitcpio-install.hook from limine-mkinitcpio-hook 1.37.1-1, triggers on usr/lib/firmware/* and runs limine-mkinitcpio-install) and on Omarchy 4 it is the wrong command: /usr/local/bin/mkinitcpio wraps it and warns that -P does not update Limine boot entries, offering limine-mkinitcpio. This record is a duplicate of linux-firmware-split-exists-in-filesystem in boot-kernel, corrected on 2026-09-06 with the same news item, the same four symptom lines, the same cause and the same Omarchy 4 fix. The nvidia subpackage is not a distinct problem: the news item names linux-firmware-nvidia as the only package that conflicts, so every hit of the split looks exactly like this one. Reconcile rather than reject: the problem is real, but the corpus should carry one record for it, or this pacman-aur entry should point at the boot-kernel one. The remedy itself was not exercised, since no machine here has a pre-split linux-firmware to upgrade from.

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

pacman -Rdd removes the package with no dependency checks. Between the two commands you have NO firmware installed. If you reboot or lose power in that window the machine may come up with no Wi-Fi, no GPU acceleration, or fail to boot. Run both commands back to back.

Symptom

sudo pacman -Syu fails on the linux-firmware update with:


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
error: failed to commit transaction (conflicting files)

Hits anyone who had not upgraded since June 2025.

Cause

linux-firmware was split into per-vendor subpackages (linux-firmware-nvidia etc.) in 20250613.12fe085f-5. Upgrading from 20250508.788aadc8-2 or earlier makes the new subpackage collide with directories still owned by the monolithic package. Announced as a required manual intervention on archlinux.org.

Fix

Run the two commands from the Arch news item back to back. Do not reboot between them.

**Plain Arch / EndeavourOS / CachyOS:**


sudo pacman -Rdd linux-firmware
sudo pacman -Syu linux-firmware

**Omarchy 4:** pacman -Rdd is a Remove operation and passes Omarchy's pacman guard untouched, but pacman -Syu carries both -S and -u, so /usr/bin/omarchy-update-pacman-guard aborts it. Bypass the guard for that one transaction and name the package explicitly. Nothing depends on linux-firmware (the kernel lists it only as an optional dependency), so an omarchy update after the removal would finish with no firmware installed:


sudo pacman -Rdd linux-firmware
sudo env OMARCHY_ALLOW_DIRECT_PACMAN=1 pacman -Syu linux-firmware

The mkinitcpio pacman hook triggers on usr/lib/firmware/*, so the initramfs (on Omarchy 4, the Limine UKI) is rebuilt inside the same transaction. Look 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 -Q | grep linux-firmware lists the new split packages, and ls /usr/lib/firmware/nvidia/ is populated. Reboot and confirm the GPU/Wi-Fi still initialise.

Sources

linux-firmware-nvidia-exists-in-filesystem