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

Direct Boot hides the Limine menu, so snapshot rollback is unreachable when an update breaks the desktop

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

The main mechanism is correct and well sourced: bin/omarchy-setup-direct-boot does efibootmgr --create --disk --part --label "Omarchy" --loader "\\EFI\\Linux\\$uki_file" (efibootmgr prepends new entries to BootOrder), the confirm prompt is verbatim "Setup direct boot (so snapshot booting must be done via bios)?", re-running detects the entry and offers "Disable direct boot (remove Omarchy EFI entry)?" then efibootmgr --bootnum "$boot_num" --delete-bootnum, and default/limine/limine.conf really ships #timeout: 3 commented out (Limine's own default of 5s then applies, as the record says). ArchWiki's Limine page confirms limine-snapper-sync is the thing that writes snapshot entries and that running limine-snapper-sync by hand is a documented check step. But the second half of the cause is factually wrong against current upstream: the script's probe is uki_file=$(sudo find /boot/EFI/Linux/ -name "omarchy*.efi" -printf "%f\n" 2>/dev/null | head -1). It already runs under sudo, so "the script's find runs without sudo" is not true, and the cited issue #6651 ("Quattro, beta 1: Setup -> Direct boot reports Error: No Omarchy UKI found") is CLOSED, i.e. fixed. Telling readers "the file is there, the script just cannot see it" sends them chasing a bug that no longer exists. The record also misses the reason Direct Boot most visibly refuses to run today: the script hard-exits on american megatrends and apple BIOS vendors before it ever looks for a UKI, and the record's manual efibootmgr --create fallback walks straight past that deliberate safety check with no warning.

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

Never delete an EFI boot entry you have not identified. efibootmgr --delete-bootnum on the wrong Boot#### can leave the machine with nothing bootable. Confirm a Limine/Arch entry exists in efibootmgr output *before* rebooting after a deletion. If in doubt, reorder with --bootorder instead of deleting. omarchy-setup-direct-boot deliberately refuses to run on American Megatrends and Apple firmware because they mishandle custom EFI entries. Do not work around that by creating the entry by hand on those machines. Also remember a snapshot restore recovers / but not /home, so ~/.config stays as-is after a rollback.

Symptom

After enabling Setup > Direct Boot, the green "Omarchy Bootloader" menu never appears. The machine goes straight from the vendor logo into Omarchy. Later, when an update breaks the desktop and the manual says "restart and select a pre-update snapshot from the boot menu", there is no boot menu to select from. Users report being stuck at a black screen or login loop with no visible way back.

A related report: Setup > Direct Boot itself fails with Error: No Omarchy UKI found in /boot/EFI/Linux/ even though sudo ls /boot/EFI/Linux/ clearly shows omarchy_linux.efi.

Cause

omarchy-setup-direct-boot creates a firmware boot entry with efibootmgr --create --label Omarchy --loader '\EFI\Linux\<uki>.efi', and efibootmgr places new entries at the head of BootOrder. The firmware then loads the unified kernel image directly and Limine never runs. Limine is what renders the snapshot entries that limine-snapper-sync writes into /boot/limine.conf. The confirmation prompt says as much: "Setup direct boot (so snapshot booting must be done via bios)?". Some users reach the same state a different way, by setting timeout: 0 in /boot/limine.conf (Omarchy ships it commented out as #timeout: 3, so Limine's own 5s default applies). Separately, the script refuses to run at all on some machines, and these are the current reasons: it hard-exits when /sys/class/dmi/id/bios_vendor matches *american megatrends* ("may not safely support custom EFI entries") or *apple*, when not booted UEFI, or when efibootmgr is not functional. Error: No Omarchy UKI found in /boot/EFI/Linux/ means the probe sudo find /boot/EFI/Linux/ -name 'omarchy*.efi' matched nothing: the ESP is not mounted at /boot, or the install boots a separate kernel+initramfs rather than a UKI, or the UKI is not named omarchy*.efi. This is **not** a sudo/permissions problem: the script's find already runs under sudo, and the beta bug that did have that symptom (issue #6651) is fixed and closed.

Fix


# Right now, to reach a snapshot once: use the firmware's one-time boot menu
#   (F12 / F8 / F9 / Esc, vendor-specific) and pick the Limine/Arch/disk entry
#   rather than the "Omarchy" entry.

# Permanent: run the same menu item again - it detects the entry and offers removal
omarchy-setup-direct-boot            # menu: Setup > Direct Boot

# Or by hand
sudo efibootmgr                      # note BootOrder and the Boot#### of "Omarchy"
sudo efibootmgr --bootnum 0003 --delete-bootnum      # remove it
sudo efibootmgr --bootorder 0001,0003                # or just demote it

# Make sure Limine still has a visible menu and current snapshot entries
sudo grep -n '^ *#\?timeout' /boot/limine.conf
#   commented out  -> Limine's own default (5s) applies
#   timeout: 0     -> menu is skipped; change it to 'timeout: 3'
sudo sed -i 's/^timeout: 0$/timeout: 3/' /boot/limine.conf
sudo limine-snapper-sync
sudo limine-snapper-list             # the entries that should appear in the menu
sudo snapper -c root list

If omarchy-setup-direct-boot refuses to run, read which check stopped it. The message is specific, and two of them are deliberate refusals, not bugs:


cat /sys/class/dmi/id/bios_vendor
#   American Megatrends / Apple -> the script exits on purpose. AMI firmware may
#   not safely handle custom EFI entries and Apple uses its own boot manager.
#   Do NOT hand-roll the entry to get around this.
[ -d /sys/firmware/efi ] && echo UEFI || echo "BIOS/CSM - direct boot N/A"
sudo efibootmgr >/dev/null && echo "efibootmgr OK"

Error: No Omarchy UKI found in /boot/EFI/Linux/ means the probe genuinely matched nothing. It already runs as sudo find, so this is not a permissions artefact (that beta bug, issue #6651, is fixed). Check what is actually there:


findmnt /boot                        # is the ESP mounted where you think?
sudo ls -l /boot/EFI/Linux/          # need a file matching omarchy*.efi

If the listing is empty or the kernel is a separate vmlinuz + initramfs rather than a UKI, there is nothing for direct boot to point at, so configure a UKI first (limine-mkinitcpio-hook / limine-update) instead of creating the entry by hand.

Verify

sudo efibootmgr no longer shows "Omarchy" first in BootOrder. Rebooting shows the "Omarchy Bootloader" menu. Snapshot entries with dates and the Omarchy version in the bottom-left corner are listed.

Sources

direct-boot-hides-limine-snapshot-menu