summaryrefslogtreecommitdiff
path: root/metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt')
-rw-r--r--metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt b/metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
index f7aaa72bebc7..dc122c1c2315 100644
--- a/metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
+++ b/metadata/news/2024-02-01-grub-upgrades/2024-02-01-grub-upgrades.en.txt
@@ -1,7 +1,7 @@
Title: GRUB upgrades
Author: Mike Gilbert <floppym@gentoo.org>
Posted: 2024-02-01
-Revision: 1
+Revision: 2
News-Item-Format: 2.0
Display-If-Installed: sys-boot/grub
@@ -24,7 +24,7 @@ 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)
+/boot/grub/x86_64-efi/*.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]
@@ -32,7 +32,7 @@ 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
+However, this will clobber any BOOTX64.EFI image provided 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.