* [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
@ 2019-06-16 19:49 voidlinux-github
2019-06-16 19:50 ` voidlinux-github
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: voidlinux-github @ 2019-06-16 19:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
New issue by ackalker on void-packages repository
https://github.com/void-linux/void-packages/issues/12499
Description: ### System
* xuname:
Void 5.1.10_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFFFF
* package:
efibootmgr-17_2
### Expected behavior
Installing a new kernel or force reconfiguring an already installed kernel should create or update a boot entry that actually boots that kernel.
### Actual behavior
The generated boot entry for booting EFISTUB kernel gets rejected by my UEFI firmware because the binary file name (for example `vmlinuz-5.1.10_1` lacks an `.efi` extension.
In contrast to what some documentation on the Internet says, the `.efi` extension is *not* optional; it is *required* by the UEFI specs for all EFI applications, no exceptions. Just because some UEFI versions on some mainboards will run EFI applications from files without an `.efi` extension doesn't mean this is true for all UEFI versions in general.
### Steps to reproduce the behavior
- Boot the system in UEFI mode
- Install `efibootmgr` package
- Make sure that `/etc/default/efibootmgr-kernel-hook` contains uncommented line `MODIFY_EFI_ENTRIES=1` and appropriate `OPTIONS="..."` value for that kernel
- Install or force reconfigure a kernel
- (optional) Reconfigure boot order using `efibootmgr -o ...`
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
2019-06-16 19:49 [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI voidlinux-github
@ 2019-06-16 19:50 ` voidlinux-github
2019-06-16 19:51 ` voidlinux-github
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-06-16 19:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/issues/12499#issuecomment-502480603
Comment:
I really think that the efibootmgr kernel hook should create a symlink with the .efi extension, this way the linux pkgs don't need to be modified.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
2019-06-16 19:49 [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI voidlinux-github
2019-06-16 19:50 ` voidlinux-github
@ 2019-06-16 19:51 ` voidlinux-github
2021-03-26 18:07 ` Dko1905
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: voidlinux-github @ 2019-06-16 19:51 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 187 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/issues/12499#issuecomment-502480657
Comment:
hmm wait, this is the ESP so no symlinks. Hmm
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
2019-06-16 19:49 [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI voidlinux-github
2019-06-16 19:50 ` voidlinux-github
2019-06-16 19:51 ` voidlinux-github
@ 2021-03-26 18:07 ` Dko1905
2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
4 siblings, 0 replies; 6+ messages in thread
From: Dko1905 @ 2021-03-26 18:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
New comment by Dko1905 on void-packages repository
https://github.com/void-linux/void-packages/issues/12499#issuecomment-808418824
Comment:
I have the same issue. It would be nice for this to be fixed.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
2019-06-16 19:49 [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI voidlinux-github
` (2 preceding siblings ...)
2021-03-26 18:07 ` Dko1905
@ 2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2022-04-15 2:12 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 293 bytes --]
New comment by github-actions[bot] on void-packages repository
https://github.com/void-linux/void-packages/issues/12499#issuecomment-1099786642
Comment:
Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [ISSUE] [CLOSED] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
2019-06-16 19:49 [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI voidlinux-github
` (3 preceding siblings ...)
2022-04-15 2:12 ` github-actions
@ 2022-04-29 2:13 ` github-actions
4 siblings, 0 replies; 6+ messages in thread
From: github-actions @ 2022-04-29 2:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
Closed issue by ackalker on void-packages repository
https://github.com/void-linux/void-packages/issues/12499
Description:
### System
* xuname:
Void 5.1.10_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFFFF
* package:
efibootmgr-17_2
### Expected behavior
Installing a new kernel or force reconfiguring an already installed kernel should create or update a boot entry that actually boots that kernel.
### Actual behavior
The generated boot entry for booting EFISTUB kernel gets rejected by my UEFI firmware because the binary file name (for example `vmlinuz-5.1.10_1` lacks an `.efi` extension.
### Steps to reproduce the behavior
- Boot the system in UEFI mode on machine with a 'strict' (standard compliant) UEFI firmware.
- Install `efibootmgr` package
- Make sure that `/etc/default/efibootmgr-kernel-hook` contains uncommented line `MODIFY_EFI_ENTRIES=1` and appropriate `OPTIONS="..."` value for that kernel
- Install or force reconfigure a kernel
- (optional) Reconfigure boot order using `efibootmgr -o ...`
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-04-29 2:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-16 19:49 [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI voidlinux-github
2019-06-16 19:50 ` voidlinux-github
2019-06-16 19:51 ` voidlinux-github
2021-03-26 18:07 ` Dko1905
2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).