From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/
Date: Tue, 6 Feb 2024 00:03:40 +0000 (UTC) [thread overview]
Message-ID: <1707177697.65b494db54e9228fbb4dd0c647f9dd11998c3f4c.floppym@gentoo> (raw)
commit: 65b494db54e9228fbb4dd0c647f9dd11998c3f4c
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 28 16:23:22 2024 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Tue Feb 6 00:01:37 2024 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=65b494db
2024-02-01-grub-upgrades: add news item
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>
.../2024-02-01-grub-upgrades.en.txt | 40 ++++++++++++++++++++++
1 file changed, 40 insertions(+)
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 <floppym@gentoo.org>
+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
next reply other threads:[~2024-02-06 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 0:03 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 19:27 [gentoo-commits] data/gentoo-news:master commit in: 2024-02-01-grub-upgrades/ Mike Gilbert
2024-02-06 19:30 Mike Gilbert
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=1707177697.65b494db54e9228fbb4dd0c647f9dd11998c3f4c.floppym@gentoo \
--to=floppym@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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