From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI
Date: Sun, 16 Jun 2019 21:49:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12499@inbox.vuxu.org> (raw)
[-- 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 ...`
next reply other threads:[~2019-06-16 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 19:49 voidlinux-github [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12499@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).