Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Depending on capitalization of --loader argument, --unicode fails #214

Open
Amilton78 opened this issue Aug 24, 2024 · 2 comments
Open

Depending on capitalization of --loader argument, --unicode fails #214

Amilton78 opened this issue Aug 24, 2024 · 2 comments

Comments

@Amilton78
Copy link

If I run efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Gentoo via Shim" -l '\EFI\gentoo\shimx64.efi' -u '\EFI\gentoo\bzImage.efi'
It tries to add \EFI\gentoo\bzImage.efi as another file to boot resulting in
Boot0003* Gentoo via Shim HD(1,GPT,c12a7328-f81f-11d2-ba4b-00a0c93ec93b,0x800,0x200000)/File(\EFI\gentoo\shimx64.efi) File(.\EFI\gentoo\bzImage.efi)

But if I instead run efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Gentoo via Shim" -l '\efi\gentoo\shimx64.efi' -u '\EFI\gentoo\bzImage.efi'
Notice the "\efi" instead of "\EFI"
It generates a proper entry
Boot0003* Gentoo via Shim HD(1,GPT,c12a7328-f81f-11d2-ba4b-00a0c93ec93b,0x800,0x200000)/File(\efi\gentoo\shimx64.efi)\EFI\gentoo\bzImage.efi with "\EFI\gentoo\bzImage.efi" as an argument

I'm running efibootmgr 18-r1

@Amilton78
Copy link
Author

It seems to work properly on 17-r1

@Amilton78
Copy link
Author

After updating back to 18-r1, I'm not sure what's happening here, the entry still is Boot0003* Gentoo via Shim HD(1,GPT,c12a7328-f81f-11d2-ba4b-00a0c93ec93b,0x800,0x200000)/File(\EFI\gentoo\shimx64.efi) File(.\EFI\gentoo\bzImage.efi),
so it might just be an error when printing the boot entry, and not when writing it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant