From: "Stefan Schmiedl" <s@xss.de>
To: gentoo-user@lists.gentoo.org
Subject: Re[2]: [gentoo-user] Fun with systemd-boot
Date: Wed, 18 Dec 2024 21:47:48 +0000 [thread overview]
Message-ID: <em46d8b8a8-f659-449d-92ce-836dacbbb427@127beca5.com> (raw)
In-Reply-To: <Z2M_PuMoVS4zGh5J@MAC.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
------ Original Message ------
From "Alan Mackenzie" <acm@muc.de>
To gentoo-user@lists.gentoo.org
Date 18.12.2024 22:31:42
Subject Re: [gentoo-user] Fun with systemd-boot
>
>Also, none of the documentation was explicit in saying that with
>efibootmgr, you have to go into the BIOS setup to select the kernel you
>want to boot. Nothing wrong with that, but if I'd know first, I wouldn't
>have bothered getting it working. (Sorry, it's been a strenuous
>evening.)
After a bit of wiki browsing and experimentation I have ended up with
the following process for a gentoo VM using UEFI boot:
- `emerge gentoo-kernel-bin`
- kernel and initramfs end up in /boot
- `efi-update 6.12.5`
where efi-update is
#!/bin/zsh
BASE=/efi/EFI/gentoo/
VERSION=${1-6.8.10}
KERNEL="vmlinuz-${VERSION}-gentoo-dist"
INITRD="initramfs-${VERSION}-gentoo-dist.img"
cp /boot/${KERNEL} /boot/${INITRD} ${BASE}
efibootmgr --create-only --create --disk /dev/sdd --part 1 --label
"gentoo ${VERSION}" --loader "\\EFI\\gentoo\\${KERNEL}" --unicode
"initrd=\\EFI\\gentoo\\${INITRD}"
echo "try: efibootmgr -n XXXX"
echo "use: efibootmgr -o XXXX,YYYY,..."
echo "del: efibootmgr -B -b XXXX"
The last three lines are to remind of which options to use for managing
the kernel for the next boot only (try), changing the permament boot
sequence
and cleaning up old kernels. I never had to enter the UEFI BIOS on this
VM.
HTH,
s.
[-- Attachment #2: Type: text/html, Size: 4608 bytes --]
next prev parent reply other threads:[~2024-12-18 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 12:13 [gentoo-user] Fun with systemd-boot Alan Mackenzie
2024-12-18 12:50 ` Arsen Arsenović
2024-12-18 13:41 ` Alan Mackenzie
2024-12-18 14:18 ` Joost Roeleveld
2024-12-18 14:30 ` Peter Humphrey
2024-12-18 15:58 ` Michael
2024-12-18 21:31 ` Alan Mackenzie
2024-12-18 21:47 ` Stefan Schmiedl [this message]
2024-12-19 10:59 ` Michael
2024-12-19 15:46 ` Alan Mackenzie
2024-12-19 16:38 ` Michael
2024-12-28 22:01 ` Wols Lists
2024-12-19 11:36 ` Peter Humphrey
2024-12-28 21:53 ` Wols Lists
2024-12-29 12:51 ` Peter Humphrey
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=em46d8b8a8-f659-449d-92ce-836dacbbb427@127beca5.com \
--to=s@xss.de \
--cc=gentoo-user@lists.gentoo.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