From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 9E0D815802C for ; Wed, 18 Dec 2024 21:47:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F33A8E085B; Wed, 18 Dec 2024 21:47:52 +0000 (UTC) Received: from s1.swsch.de (s1.swsch.de [IPv6:2a01:4f8:a0:8074::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E6E12E07C5 for ; Wed, 18 Dec 2024 21:47:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xss.de; s=s1; h=Content-Type:MIME-Version:Reply-To:Message-Id:Date:Subject:To:From: Content-Transfer-Encoding:Sender:Cc; bh=2q3ZLhJo7qwI/HO96PQXhR2ZlhjzrUAPXL7Wf553L3E=; b=GopDlEdWfn9v866ocM+SVAnQ+n jIBAWBXQFfA1m3fRyT5Au+qw5QUl8p8iJYlpDtys1OEKLeb4A1aJidnN6OA7FvufqnzTy0z+6Vm/s 0dJM60U2ebm6X8eeWlSWPqUiM1VJu1AtrM32Y3jdM9f1gOmGSaM/uAaCHl6YswMFqaQ8=; Received: from [2003:d4:474f:1001:d01d:318e:dd6f:7296] by s1.swsch.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1tO1tV-000000000XK-0auo for gentoo-user@lists.gentoo.org; Wed, 18 Dec 2024 22:47:49 +0100 From: "Stefan Schmiedl" To: gentoo-user@lists.gentoo.org Subject: Re[2]: [gentoo-user] Fun with systemd-boot Date: Wed, 18 Dec 2024 21:47:48 +0000 Message-Id: In-Reply-To: References: <3620457.iIbC2pHGDl@cube> <2293940.iZASKD2KPV@rogueboard> User-Agent: eM_Client/10.1.4588.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------=_MBCC26BE36-981B-42BE-A11F-952584D94B7E" X-Archives-Salt: 6a01079b-5781-41a8-aaea-3349bf26f026 X-Archives-Hash: fcc11349e9a2745d19ed7674a8cb2698 --------=_MBCC26BE36-981B-42BE-A11F-952584D94B7E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable ------ Original Message ------ >From "Alan Mackenzie" 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=3D/efi/EFI/gentoo/ VERSION=3D${1-6.8.10} KERNEL=3D"vmlinuz-${VERSION}-gentoo-dist" INITRD=3D"initramfs-${VERSION}-gentoo-dist.img" cp /boot/${KERNEL} /boot/${INITRD} ${BASE} efibootmgr --create-only --create --disk /dev/sdd --part 1 --label=20 "gentoo ${VERSION}" --loader "\\EFI\\gentoo\\${KERNEL}" --unicode=20 "initrd=3D\\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=20 sequence and cleaning up old kernels. I never had to enter the UEFI BIOS on this=20 VM. HTH, s. --------=_MBCC26BE36-981B-42BE-A11F-952584D94B7E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
------ 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

=
=C2=A0
Also, none of the documentation was explicit in s= aying 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 b= een 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`
- ke= rnel and initramfs end up in /boot
- `efi-update 6.12.5`

where efi-update is<= /span>

#!/bin/zsh
BASE=3D/efi/EFI/gentoo/
VERSION=3D${1-6.8.10}
KERNEL=3D"vmlin= uz-${VERSION}-gentoo-dist"
INITRD=3D"initramfs-${VERSION}-gentoo-dist.img"
cp /boot/${KERNEL} /boot/${INITRD} ${BASE}
efibootmgr --create-only --create --disk /dev/sdd --part 1 --l= abel "gentoo ${VERSION}" --loader "\\EFI\\gentoo\\${KERNEL}" --unicode "ini= trd=3D\\EFI\\gentoo\\${INITRD}"
echo "try:=C2=A0 =C2=A0efibootmgr -n XXXX"
echo "use:=C2=A0 =C2=A0efibootmgr -o XXXX,YYYY,..."
echo "del:=C2=A0 =C2=A0efibootmgr -B -b XXXX"=C2=A0

The last three lines are to remind of which options t= o use for managing
the kernel for the nex= t boot only (try), changing the permament boot sequence
and cleaning up old kernels. I never had to enter the UEFI B= IOS on this VM.

HTH,
s.
--------=_MBCC26BE36-981B-42BE-A11F-952584D94B7E--