Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Installer fails with “Not booted with EFI” despite UEFI setup
Reported by Satbir6 · filed Apr 22, 2026Closed upstream on 2026-04-22. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
SN: MP2KDFWL, PN: 82Y9009KIN, BIOS: M3CN46WW
What's wrong?
📋 Description
When booting the Omarchy installer (Limine-based), the installation fails with:
Not booted with EFI or running in a container
Additional errors shown:
Limine config conflicts
Boot partition path issues
This occurs even though the system is configured for UEFI.
🖥️ Environment
Firmware / BIOS
Secure Boot: Disabled
USB Boot: Enabled
Platform Mode: Setup Mode
Expected boot mode: UEFI
Disk Layout (before install)
Disk 0 (Windows – untouched)
EFI partition (~260 MB)
Windows (C:)
Recovery partition
Disk 1 (target disk)
2 GB EFI partition (manually created)
~474 GB primary partition
🔍 Observed Behaviour
Installer reports non-EFI boot
Fails to proceed due to EFI requirement
Limine-related errors appear (config + paths)
🤔 Expected Behaviour
Installer should detect UEFI environment correctly
Proceed with EFI-based installation
Automatically manage partitioning
🧪 Troubleshooting Performed
1. Verified boot mode
Ran:
ls /sys/firmware/efi
In failing case: directory missing → system is actually booting in Legacy/CSM mode
2. Identified boot menu issue
Boot menu shows two entries:
USB Name (Legacy)
UEFI: USB Name (Correct)
Selecting the non-UEFI entry reproduces the issue.
- USB creation issue (Rufus)
Initial USB created with:
GPT ✅
UEFI target ✅
NTFS ❌
Likely problem:
Rufus uses UEFI:NTFS workaround
Limine-based systems appear incompatible with this in some cases
4. Disk layout issue
Pre-created EFI partition (2 GB) on target disk
Non-standard layout may confuse installer
✅ Workaround (Confirmed)
✔️ Using Ventoy
Install Ventoy on USB
Copy ISO directly (no extraction)
Boot via:
UEFI: Ventoy USB
Select ISO from Ventoy menu
✔️ Clean disk before install
Using diskpart:
select disk 1
clean
convert gpt
Leave disk fully unallocated.
✔️ Let installer handle partitions
Do not pre-create:
EFI
Root
Swap
📌 Key Findings
Installer error is misleading — system can be UEFI-capable but booted in Legacy mode
Limine appears sensitive to:
NTFS-based boot media (Rufus default)
Incorrect EFI boot path
Pre-partitioned disks may introduce additional failure points
❓ Open Questions
Should the installer detect and warn explicitly about Legacy boot vs UEFI?
Is Limine expected to work with Rufus NTFS setups?
Could installer validate EFI presence more clearly before failing?
🔁 Repro Steps (Likely)
Create USB with Rufus (NTFS)
Boot via non-UEFI USB entry
Start installer
Observe EFI error
View raw text
### System details SN: MP2KDFWL, PN: 82Y9009KIN, BIOS: M3CN46WW ### What's wrong? 📋 Description When booting the Omarchy installer (Limine-based), the installation fails with: Not booted with EFI or running in a container Additional errors shown: Limine config conflicts Boot partition path issues This occurs even though the system is configured for UEFI. 🖥️ Environment Firmware / BIOS Secure Boot: Disabled USB Boot: Enabled Platform Mode: Setup Mode Expected boot mode: UEFI Disk Layout (before install) Disk 0 (Windows – untouched) EFI partition (~260 MB) Windows (C:) Recovery partition Disk 1 (target disk) 2 GB EFI partition (manually created) ~474 GB primary partition 🔍 Observed Behaviour Installer reports non-EFI boot Fails to proceed due to EFI requirement Limine-related errors appear (config + paths) 🤔 Expected Behaviour Installer should detect UEFI environment correctly Proceed with EFI-based installation Automatically manage partitioning 🧪 Troubleshooting Performed 1. Verified boot mode Ran: ls /sys/firmware/efi In failing case: directory missing → system is actually booting in Legacy/CSM mode 2. Identified boot menu issue Boot menu shows two entries: USB Name (Legacy) UEFI: USB Name (Correct) Selecting the non-UEFI entry reproduces the issue. 3. USB creation issue (Rufus) Initial USB created with: GPT ✅ UEFI target ✅ NTFS ❌ Likely problem: Rufus uses UEFI:NTFS workaround Limine-based systems appear incompatible with this in some cases 4. Disk layout issue Pre-created EFI partition (2 GB) on target disk Non-standard layout may confuse installer ✅ Workaround (Confirmed) ✔️ Using Ventoy Install Ventoy on USB Copy ISO directly (no extraction) Boot via: UEFI: Ventoy USB Select ISO from Ventoy menu ✔️ Clean disk before install Using diskpart: select disk 1 clean convert gpt Leave disk fully unallocated. ✔️ Let installer handle partitions Do not pre-create: EFI Root Swap 📌 Key Findings Installer error is misleading — system can be UEFI-capable but booted in Legacy mode Limine appears sensitive to: NTFS-based boot media (Rufus default) Incorrect EFI boot path Pre-partitioned disks may introduce additional failure points ❓ Open Questions Should the installer detect and warn explicitly about Legacy boot vs UEFI? Is Limine expected to work with Rufus NTFS setups? Could installer validate EFI presence more clearly before failing? 🔁 Repro Steps (Likely) Create USB with Rufus (NTFS) Boot via non-UEFI USB entry Start installer Observe EFI error
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.