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 (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6C70415815E for ; Mon, 5 Feb 2024 23:44:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 18F31E2A24; Mon, 5 Feb 2024 23:44:21 +0000 (UTC) Received: from smtp.gentoo.org (mail.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (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 C1C95E29E9 for ; Mon, 5 Feb 2024 23:44:20 +0000 (UTC) References: <20240128162531.1360-1-floppym@gentoo.org> User-agent: mu4e 1.10.8; emacs 30.0.50 From: Sam James To: gentoo-dev@lists.gentoo.org Cc: pr@gentoo.org Subject: Re: [gentoo-dev] [PATCH] 2024-02-01-grub-upgrades: add news item Date: Mon, 05 Feb 2024 23:44:10 +0000 Organization: Gentoo In-reply-to: <20240128162531.1360-1-floppym@gentoo.org> Message-ID: <87plxa8oj3.fsf@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: 051367f7-49b7-42e3-b80d-b7f140cb2151 X-Archives-Hash: ecf40402d308cbb0868eb4f4f62eaad3 Mike Gilbert writes: > Signed-off-by: Mike Gilbert > --- > .../2024-02-01-grub-upgrades.en.txt | 40 +++++++++++++++++++ > 1 file changed, 40 insertions(+) > create mode 100644 2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt > LGTM. > diff --git a/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt > new file mode 100644 > index 0000000..f7aaa72 > --- /dev/null > +++ b/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt > @@ -0,0 +1,40 @@ > +Title: GRUB upgrades > +Author: Mike Gilbert > +Posted: 2024-02-01 > +Revision: 1 > +News-Item-Format: 2.0 > +Display-If-Installed: sys-boot/grub > + > +When booting with GRUB, it is important that the core image and modules > +have matching versions. Usually, running grub-install is sufficient to > +ensure this. > + > +On the UEFI platform, grub-install allows the core image to be placed in > +two different locations: > + > +EFI/gentoo/grubx64.efi > +This is the location used by grub-install without options. > + > +EFI/BOOT/BOOTX64.EFI > +This is the location used by grub-install --removable. > + > +On upgrades, it is common for users to mismatch the grub-install options > +they used for the current and previous versions of grub. This will cause > +a stale core image to exist. For example: > + > +/boot/efi/EFI/BOOT/BOOTX64.EFI (grub 2.06 core image) > +/boot/efi/EFI/gentoo/grubx64.efi (grub 2.12 core image) > +/boot/grub/x86_64-pc/*.mod (grub 2.12 modules) > + > +Booting this system using BOOTX64.EFI image would likely fail due to a > +symbol mismatch between the core image and modules. [1] > + > +Re-runing grub-install both with and without the --removable option > +should ensure a working GRUB installation. > + > +However, this will clobber any BOOTX64.EFI image provded by other > +loaders. If dual-booting using another boot loader, users must take care > +not to replace BOOTX64.EFI if it is not provided by GRUB. > + > +References: > +[1] https://bugs.gentoo.org/920708