OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core medium occasional DISPUTE

Update > Firmware finds nothing, or reboots without applying the BIOS/UEFI capsule

omarchy-4archendeavouroscachyos
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Cause is accurate against bin/omarchy-update-firmware, which is exactly: install fwupd if omarchy-cmd-missing fwupdmgr, then when /sys/firmware/efi exists sudo install -D /usr/lib/fwupd/efi/fwupdx64.efi /boot/EFI/arch/fwupdx64.efi, then fwupdmgr refresh --force and sudo fwupdmgr update. Every failure mode is corroborated by ArchWiki's Fwupd page: the uppercase-EFI warning verbatim ("The EFI directory must be in all upper-case; if you used lower-case, fwupd may detect the esp as esp/efi/"), the bind-mount trap verbatim ("deduces the wrong mount point if bind is used to mount the EFI system partition to /boot... results in a (misleading) file system is read-only error"), "In BIOS settings changing the boot order must be allowed" as the cause of a silent no-op, and the stuck/black reboot. The Secure Boot block is quoted correctly too: sbctl sign -s -o /usr/lib/fwupd/efi/fwupdx64.efi.signed /usr/lib/fwupd/efi/fwupdx64.efi, and [uefi_capsule] DisableShimForSecureBoot=true is the current fwupd-1.9+ location in /etc/fwupd/fwupd.conf (the wiki notes the pre-1.9 uefi_capsule.conf path). Two concrete defects. (1) sudo tee -a /etc/fwupd/fwupd.conf appends a second [uefi_capsule] group to a file that already ships that section. The wiki presents this as a config-file edit, not an append, and duplicating a group in a GKeyFile is at best undefined and at worst leaves the key silently inert, which is indistinguishable from the very symptom the record is diagnosing. Edit the existing section. (2) sudo fwupdmgr update <update_ID> is not a real argument: fwupdmgr update takes a DEVICE-ID or GUID from get-devices/get-updates. get-history shows what was attempted, not ids to feed back to update. The record also omits EspLocation, which the wiki gives as the fix for the "ESP not detected" case it raises in its own cause.

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

Never power-cycle, force-reset or unplug the machine during a firmware flash, even if the screen stays black for several minutes. That is how a board gets bricked. Run it only on AC power with a charged battery. A UEFI firmware update can discard existing NVRAM boot entries: after a successful BIOS update be ready to recreate one, e.g. sudo efibootmgr --create --disk /dev/nvme0n1 --part 1 --label Omarchy --loader '\EFI\Linux\omarchy_linux.efi', or boot the removable /EFI/BOOT/BOOTX64.EFI fallback. This is not part of the normal omarchy update pipeline and should not be run casually.

Symptom

Update > Firmware (or omarchy-update-firmware) either reports no updatable devices, or fails with one of:


failed to write file /boot/EFI/arch/fw/...: No space left on device
UEFI capsule updates not available or enabled in firmware setup
file system is read-only

or, most confusingly, reports success, prompts for a reboot, and after the reboot fwupdmgr get-devices still shows the old firmware version. On some laptops the reboot shows a black screen with no messages for minutes.

Cause

omarchy-update-firmware installs fwupd if missing, copies /usr/lib/fwupd/efi/fwupdx64.efi to /boot/EFI/arch/fwupdx64.efi when booted UEFI, then runs fwupdmgr refresh --force and sudo fwupdmgr update. Peripheral firmware (docks, SSDs, mice, Thunderbolt) is applied live. BIOS/UEFI firmware is **not**: fwupd stages a capsule on the ESP and the firmware applies it during the next boot. That staging silently fails or is ignored when the ESP is small or full, when the directory is efi/ rather than uppercase EFI/, when /boot is a bind mount (fwupd deduces the wrong mount point and reports a misleading read-only error), when efivars are unavailable, or when the firmware's boot order is locked so the capsule loader never runs: the classic "no error but no upgrade on reboot".

Fix


# 1. Preconditions
[ -d /sys/firmware/efi ] && echo "UEFI OK"      # nothing works in BIOS/CSM mode
findmnt /boot                                    # ESP must actually be mounted
df -h /boot                                      # capsules need tens of MB free
ls -d /boot/EFI                                  # must be UPPERCASE 'EFI'

# 2. Free space on a full ESP before anything else
sudo du -xhd2 /boot | sort -h | tail

# 3. Drive it step by step instead of through the menu
sudo systemctl restart fwupd.service
fwupdmgr get-devices
fwupdmgr refresh --force
fwupdmgr get-updates
sudo fwupdmgr update            # reboot when prompted; the screen may stay black for minutes

# 4. Nothing changed after the reboot - was it applied, or never run?
fwupdmgr get-history            # what was attempted and its result
fwupdmgr get-devices            # copy the Device ID of the device you want
sudo fwupdmgr update <DEVICE-ID>   # apply one device at a time

In the firmware setup, enable "allow boot order change" / disable "boot order lock". A locked boot order is the standard reason the capsule silently never runs.

If fwupd cannot find the ESP (or picks one on another disk), pin it in the [uefi_capsule] section of /etc/fwupd/fwupd.conf:


[uefi_capsule]
EspLocation=/boot

On Secure Boot systems fwupd chainloads through shim. With your own keys, sign it and tell fwupd to skip shim:


sudo sbctl sign -s -o /usr/lib/fwupd/efi/fwupdx64.efi.signed /usr/lib/fwupd/efi/fwupdx64.efi

Then **edit the [uefi_capsule] section that already exists** in /etc/fwupd/fwupd.conf. Do not append a second copy of the section header, or the key may never be read:


sudo grep -n '\[uefi_capsule\]\|DisableShimForSecureBoot' /etc/fwupd/fwupd.conf
sudoedit /etc/fwupd/fwupd.conf
#   under the existing [uefi_capsule] section, set (uncommenting if present):
#       DisableShimForSecureBoot=true
sudo systemctl restart fwupd.service

(On installs predating fwupd 1.9 this option lives in /etc/fwupd/uefi_capsule.conf instead.)

Verify

fwupdmgr get-devices shows the new version string for the device. fwupdmgr get-history lists the update with Status: Success.

Sources

firmware-update-fwupd-not-applied