Limine panics with 'efi: LoadImage failure' on the Omarchy kernel entry (switch from UKI to protocol: linux)
The cause and fix hold. /etc/limine-entry-tool.d/omarchy-uki.conf sets ENABLE_UKI=yes, /etc/limine-entry-tool.conf ships it as no, and /etc/default/limine loads after every drop-in. #12045 (MSI X870E, EFI_ACCESS_DENIED under Secure Boot, sbctl FQ0001, CachyOS protocol: linux on the same board, stale snapshot entries) and #12143 (Yoga 11e, EFI_INVALID_PARAMETER, the exact /etc/default/limine plus arch-chroot limine-mkinitcpio path, no full reboot confirmed) were read in full and match the fix and its caveats. The chroot recipe it points to mounts the ESP at /mnt/boot, and limine-entry-tool skips /proc/cmdline inside a chroot and takes KERNEL_CMDLINE from /etc/default/limine, which Omarchy populates. The previous audit note was wrong on one point: it said Limine under Secure Boot relies on enrolled config hashes refreshed by 90-limine-enroll-config. That hook only enrolls when ENABLE_ENROLL_LIMINE_CONFIG=yes (enroll_config() in limine-common-functions), and Omarchy leaves it at the default no. Limine's USAGE.md says that with no enrolled checksum Limine treats Secure Boot as inactive. So after the switch, firmware verifies the Limine binary but nothing verifies the kernel and initramfs Limine loads under protocol: linux. A reader enabling Secure Boot for dual-boot should know that, so the danger now says it and names the setting. Not exercised: nothing rebuilt, no Secure Boot change.
Only the MSI report confirmed a full reboot after the change. The Bay Trail report confirmed only that the protocol: linux entry was generated. Keep the Omarchy ISO at hand for the first reboot. Old snapshot entries still use the UKI and are not a working fallback on affected firmware.
Under Secure Boot, a protocol: linux entry is loaded by Limine itself rather than by the firmware. Limine's documentation says it checks those files only when a config checksum is enrolled, and Omarchy leaves ENABLE_ENROLL_LIMINE_CONFIG at its default of no. After this change Secure Boot verifies the signed Limine binary and nothing verifies the kernel and initramfs. The option and its requirements are described in the comments of /etc/limine-entry-tool.conf.
Symptom
Choosing the normal Omarchy entry in Limine halts immediately:
PANIC: efi: LoadImage failure (0x800000000000000f)
Stacktrace:
[0x6a2b8c2f] <panic+0x15f>
[0x6a2d534c] <chainload+0x38c>
[0x6a2d160b] <boot+0x16b>
[0x6a2cf028] <_menu+0xe18>
End of trace. System halted.
Reported with 0x800000000000000f (EFI_ACCESS_DENIED) on an MSI X870E board after enabling Secure Boot with sbctl, and with 0x8000000000000002 (EFI_INVALID_PARAMETER) on a fresh install on a Bay Trail ThinkPad Yoga 11e with Secure Boot off. The kernel never starts.
Cause
Omarchy forces UKI mode with /etc/limine-entry-tool.d/omarchy-uki.conf (ENABLE_UKI=yes, owned by omarchy-settings), overriding limine-entry-tool's own default of ENABLE_UKI=no in /etc/limine-entry-tool.conf. A UKI entry is protocol: efi, so Limine hands the image to the firmware's LoadImage(). Some firmware fails that call. The MSI report ties it to the board family sbctl tracks as FQ0001, and a second install on the same board using protocol: linux boots fine under Secure Boot. With protocol: linux Limine loads the kernel and initramfs itself and never calls LoadImage().
Fix
Turn UKI generation off in /etc/default/limine. That file loads after every drop-in, so it beats omarchy-uki.conf (owned by omarchy-settings) without editing a package-owned file. Then rebuild:
echo 'ENABLE_UKI=no' | sudo tee -a /etc/default/limine
sudo limine-mkinitcpio
sudo grep -n -A4 'protocol' /boot/limine.conf | head -20 # expect protocol: linux, path:, module_path:
If the installed system cannot boot at all, do the same from the Omarchy ISO. Unlock and mount it as in chroot-recovery-btrfs-missing-subvol, then:
echo 'ENABLE_UKI=no' >> /mnt/etc/default/limine
arch-chroot /mnt limine-mkinitcpio
The MSI reporter (#12045) confirmed this boots under Secure Boot. The Bay Trail reporter (#12143) confirmed only that the protocol: linux entry was generated, not that the machine then booted, so treat it as the thing to try rather than a known fix on older firmware.
With Secure Boot enabled, check the signing state before rebooting:
sudo sbctl verify
Snapshot entries created before the change still point at the old UKI and will panic the same way. Snapshots taken afterwards use the new format.
Verify
sudo grep -c 'protocol: linux' /boot/limine.conf is at least 1, the Omarchy entry boots without a panic, and cat /proc/cmdline shows the expected cryptdevice=/root= parameters.