From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] efibootmgr kernel hook does not create entry
Date: Mon, 22 Aug 2022 17:58:58 +0200 [thread overview]
Message-ID: <20220822155858.YlXo4V5ioL_Fh_LzdCv4reGxKrTBSy2O699FtNZZX6Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38533@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Closed issue by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/38533
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.16_1 x86_64-musl GenuineIntel uptodate rrnDFFFFFFFFF
### Package(s) Affected
efibootmgr-18_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Cannot find any.
### Expected behaviour
The kernel hook does the job of creating a new entry.
### Actual behaviour
No entry is created: more precisely, it creates an entry, but does not add it to the bootorder.
This is from inside the installer chroot (both the working way and the broken one).
The package itself works if I use
`doas efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "Void Linux with test kernel" --loader /vmlinuz-5.18.16_1 --unicode 'loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e8681333=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard initrd=\initramfs-5.18.16_1.img' --verbose`
I'm using
```
$ cat /etc/default/efibootmgr-kernel-hook
# Options for the kernel hook script installed by the efibootmgr package.
MODIFY_EFI_ENTRIES=1
# Kernel command-line options.
OPTIONS="loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e8681333=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard"
# Disk where EFI Partition is. Default is /dev/sda
DISK="/dev/nvme0n1"
# Partition number of EFI Partition. Default is 1
PART=1
```
### Steps to reproduce
`xbps-reconfigure -f linux5.18`
next prev parent reply other threads:[~2022-08-22 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 13:06 [ISSUE] " dkwo
2022-08-08 14:09 ` dkwo
2022-08-08 15:24 ` dkwo
2022-08-11 21:58 ` prez
2022-08-11 21:58 ` prez
2022-08-12 16:36 ` TeusLollo
2022-08-12 16:38 ` TeusLollo
2022-08-13 3:07 ` prez
2022-08-13 8:32 ` dkwo
2022-08-22 12:18 ` sgn
2022-08-22 15:12 ` TeusLollo
2022-08-22 15:13 ` TeusLollo
2022-08-22 15:41 ` Duncaen
2022-08-22 15:58 ` dkwo [this message]
2022-08-22 15:58 ` dkwo
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=20220822155858.YlXo4V5ioL_Fh_LzdCv4reGxKrTBSy2O699FtNZZX6Y@z \
--to=dkwo@users.noreply.github.com \
--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).