OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
boot-kernel high occasional DISPUTE

Omarchy: Limine panics on a stale /EFI/Linux/arch-linux.efi entry after upgrading

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

Issue 7989 is real and the title matches the record's cause exactly ('omarchy-upgrade-to-quattro leaves archinstall's /EFI/Linux/arch-linux.efi Limine entry in place, so the default boot entry panics'), and normalize_limine_config() does exist in bin/omarchy-upgrade-to-quattro. The hand-edit works, but it is the fragile route: any subsequent omarchy update replaces /boot/limine.conf anyway. Also default_entry: 1 is offered as the example while Omarchy's shipped template uses default_entry: 2. Limine's index is 1-based (confirmed in CONFIG.md), so pasting 1 may silently select a different entry than intended.

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

Editing limine.conf on the ESP with no working entry left will leave the machine unbootable without a live USB. Copy the file to limine.conf.bak first and verify at least one entry's path: resolves to a file that exists on the ESP.

Symptom

After upgrading to Omarchy Quattro (4.x), the Limine countdown expires and the machine panics instead of booting:


PANIC: efi: Failed to open image with path 'boot():/EFI/Linux/arch-linux.efi'

The menu still lists an entry titled Arch Linux (linux) that no longer works.

Cause

archinstall originally wrote a Limine entry pointing at the unified kernel image /EFI/Linux/arch-linux.efi. Omarchy's upgrade path deletes that UKI when it takes over kernel image generation, but normalize_limine_config() does not strip the now-dangling entry from /boot/limine.conf. If that stale entry is the default, the timeout selects a file that is not there. Tracked as basecamp/omarchy#7989.

Fix

At the Limine menu, arrow to the working **Omarchy** entry and boot it. Then take the supported route, which rewrites the config from Omarchy's template and drops the dangling entry for you:


ls -l /boot/EFI/Linux/            # confirm arch-linux.efi is really gone
sudo omarchy-refresh-limine       # backs up to /boot/limine.conf.bak, regenerates, runs limine-update

If you would rather edit by hand:


sudo cp /boot/limine.conf /boot/limine.conf.bak
sudoedit /boot/limine.conf

Delete the whole stanza:


/Arch Linux (linux)
    protocol: efi
    path: boot():/EFI/Linux/arch-linux.efi

default_entry is a **1-based index into the entries that remain after your edit**. Count them rather than copying a number. Verify by booting once with a visible menu:


timeout: 5
default_entry: 1

Then apply:


sudo limine-update          # re-reads /boot/limine.conf
sudo limine-mkinitcpio      # rebuilds the UKIs on the ESP

A hand-edited /boot/limine.conf does not survive the next omarchy update, but that is fine here, because the refresh regenerates from the template, which never contained the stale entry.

Verify

Reboot and let the timeout expire without touching the keyboard. The machine boots straight into Omarchy. grep -n 'arch-linux.efi' /boot/limine.conf returns nothing.

Sources

omarchy-limine-panic-stale-arch-linux-efi