Skip to content

efi/uuid() chainload fails on secondary ESP — boot(n): works reliably as workaround (Limine 9.3.4) #513

Open
@everyoneexe

Description

@everyoneexe

Problem

Trying to boot Windows 11 UEFI via Limine using uuid() or efi protocol fails with path is incorrect or leads to a reboot loop.

Configuration that does not work:

/Windows 11 (UEFI)
    protocol: efi
    path: uuid:4e93cb13-e988-484d-9945-4a878d6d58eb:/EFI/Microsoft/Boot/bootmgfw.efi

Even though the file exists and is readable from /mnt/EFI/Microsoft/Boot/bootmgfw.efi (on /dev/nvme0n1p1), Limine fails to boot it.


Setup

  • Limine: v9.3.4
  • Windows ESP: /dev/nvme0n1p1
    PARTUUID=4e93cb13-e988-484d-9945-4a878d6d58eb
  • Limine ESP: /dev/nvme0n1p4
  • Secure Boot: Disabled

What Worked

This minimal config boots Windows 11 perfectly:

/Windows 11 (UEFI)
    protocol: efi
    path: boot(1):/EFI/Microsoft/Boot/bootmgfw.efi
  • boot(1): refers to the first ESP on disk (Windows’ ESP)
  • boot(): defaults to Limine’s own ESP
  • uuid(): fails in this case — either “path incorrect” or reboot loop

✅ So far, boot(n): seems to be the most reliable method for EFI chainloading from other ESPs.


Suggestion

This should either be documented officially (if not already), or uuid() support should be improved for cross-ESP EFI chainload cases.


Verified Environment

  • Arch Linux (Limine installed on its own ESP)
  • Windows 11 UEFI (dualboot)
  • Limine boot menu successfully displays and boots both entries

Thanks for the amazing work on Limine!

Metadata

Metadata

Assignees

No one assigned

    Labels

    unconfirmed-bugA bug that has not been properly reproduced yet.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions