Where Is the Limine Config File?
Where Limine looks for limine.conf across ESP and boot volumes, and why duplicate copies get ignored.
Last updated
Limine scans an ordered list of candidate spots for its config on every boot. EFI builds check the bootloader directory first with fallbacks across the ESP. BIOS builds walk boot volume roots after that.
That order means stray duplicates shadow the file you actually edited. Keep one canonical copy per firmware mode and delete the rest. The Linux visible path shifts with the ESP mount, so resolve it before editing. Timeout values share the same file, so one edit covers every menu entry. Keep a fallback entry for rescue boots.
Where Limine stores this, by platform
/boot/efi/EFI/BOOT/limine.conf
First choice config beside the EFI binary with ESP fallbacks after it. BIOS builds use boot volume roots. Keep one copy to avoid shadowing.
Frequently asked questions
Limine ignores my limine.conf edits. Why?
Keep exactly one config in the highest priority spot for your firmware mode. Earlier candidates in the scan order shadow later ones silently. List every ESP and boot copy before assuming edits apply.
Do UEFI and BIOS installs share one limine.conf spot?
UEFI builds read the EFI BOOT tree on the ESP while BIOS builds read the boot volume roots. Protocol entries work on both, but paths resolve per firmware. Match the file spot to the installed binary flavor.
Notice an outdated path? Let us know.