Add the missing Limine boot entry after a suspiciously fast install
The scenario and the chroot recovery shape are sound, and /boot/limine.conf is the correct path (13 references across the repo vs 1 legacy reference to /boot/limine/limine.conf). limine-mkinitcpio is real. But pacman -S limine limine-mkinitcpio-hook is wrong as written: archlinux.org shows only limine (extra, 12.6.1) in the official repos. limine-mkinitcpio-hook is not an official package, it comes from the AUR / the [omarchy] repo (it is listed in install/omarchy-other.packages). From a plain Arch ISO chroot that command fails unless the [omarchy] repo and its keyring are already configured. The mkinitcpio -P + limine-mkinitcpio pair is redundant (limine-mkinitcpio rebuilds initramfs/UKI for all kernels itself), and the recovery omits limine-update, which is what actually writes the entries. limine bios-install /dev/nvme0n1 on an NVMe UEFI install is very unlikely to be what anyone wants and deserves a stronger caveat.
Chroot bootloader surgery on the wrong device wipes the ESP. Double-check lsblk -f before mounting, and never run limine bios-install against a UEFI-only install.
Symptom
Install finishes suspiciously fast ("under 3 minutes"), with an error that flashes past too quickly to read. On reboot the machine lands in the Limine boot menu but the only entry is a generic **EFI** option, with no Omarchy/Arch kernel entry at all. Reported on both AMD and NVIDIA hardware.
Cause
The Omarchy installer's Limine step failed (commonly the initramfs/UKI generation or the Limine config write), so no kernel boot entry was created. The installer's error handling swallowed it and the run "completed".
Fix
Boot the Omarchy/Arch ISO, mount and chroot into the installed system:
cryptsetup open /dev/nvme0n1p2 cryptroot # your LUKS partition
mount -o subvol=@ /dev/mapper/cryptroot /mnt
mount /dev/nvme0n1p1 /mnt/boot # your ESP
arch-chroot /mnt
Inside the chroot, regenerate the initramfs/UKI and the Limine entries. limine-mkinitcpio does the initramfs rebuild for every kernel and updates the boot entries in one pass, so you do not need a separate mkinitcpio -P:
limine-mkinitcpio
limine-update
cat /boot/limine.conf # confirm a kernel entry now exists
ls /boot/EFI/Linux/ # confirm the UKI (omarchy_linux.efi) exists
exit
umount -R /mnt
reboot
If the tooling is missing, install it. Only limine is in the official Arch repos. limine-mkinitcpio-hook comes from the AUR or the [omarchy] repo, so on a plain Arch ISO chroot you need that repo configured (or build it from the AUR) first:
pacman -S limine
pacman -S limine-mkinitcpio-hook limine-entry-tool # requires the [omarchy] repo or AUR
If /boot/limine.conf is missing entirely, restore Omarchy's default and rebuild:
cp /usr/share/omarchy/default/limine/limine.conf /boot/limine.conf
limine-mkinitcpio
limine-update
Do NOT run limine bios-install on a UEFI machine. Omarchy installs are UEFI (Secure Boot off, ESP at /boot), and BIOS-installing Limine to the disk is only correct for a genuine legacy-BIOS install.
Verify
ls /boot/EFI/Linux/ (or /boot/limine.conf) contains a kernel/UKI entry, and the Limine menu shows a named Omarchy entry on next boot.