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

Fix 'Limine config not found' when the installer wrote a working one

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

The path confusion is real. /boot/limine.conf is Omarchy's actual location and a legacy /boot/limine/limine.conf reference does still exist in the tree (bin/omarchy-upgrade-to-quattro:476). But the proposed fix cannot work on a normal Omarchy install. /boot IS the EFI System Partition (record 9 in this same set mounts /dev/nvme0n1p1 at /mnt/boot), and the ESP is vfat. vfat does not support symbolic links, so sudo ln -sf /boot/limine.conf /boot/limine/limine.conf fails with 'Operation not permitted'. It will never satisfy the path check. A bind mount or a copy is required instead, and the copy has to be kept in sync or the bootloader reads a stale config.

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

Do not move or delete the real limine.conf. Symlink to it. Removing it leaves the machine unbootable.

Symptom

Install or update aborts with:


Error: Limine config not found at /boot/limine/limine.conf

even though the installer clearly wrote a working /boot/limine.conf. Reported on Omarchy 3.2 installs.

Cause

The limine-snapper integration script has a fallback branch that assumes the config lives at /boot/limine/limine.conf (the BIOS layout). On installs where Limine's config was written to /boot/limine.conf (or /boot/EFI/BOOT/limine.conf), the path check misses and the script bails.

Fix

Find where the config actually is:


sudo find /boot -name 'limine.conf' 2>/dev/null
findmnt /boot        # note the FSTYPE - on Omarchy this is usually vfat (the ESP)

On Omarchy the real file is /boot/limine.conf.

Do NOT try to symlink it into place. /boot is the EFI System Partition and is formatted vfat, which has no symlink support, so ln -s there fails outright. If you need the legacy /boot/limine/limine.conf path to resolve, use a bind mount, which works on vfat and disappears on reboot (so it cannot silently rot):


sudo mkdir -p /boot/limine
sudo mount --bind /boot/limine.conf /boot/limine/limine.conf

Re-run the failing step, then unmount:


omarchy update
sudo umount /boot/limine/limine.conf

The real fix is to update. The path detection was corrected upstream, and current Omarchy consistently uses /boot/limine.conf:


omarchy update

If your Limine config genuinely is at a different location, regenerate Omarchy's canonical one rather than papering over the path:


omarchy-refresh-limine     # moves the old file to /boot/limine.conf.bak, rewrites it,
                           # then runs limine-update and limine-snapper-sync

Verify

sudo limine-mkinitcpio runs without the "Limine config not found" error, and snapshot entries appear in the boot menu.

Sources

limine-snapper-wrong-config-path