public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gordon Pettey <petteyg359@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] 2024-02-01-grub-upgrades: add news item
Date: Tue, 6 Feb 2024 08:28:22 -0600	[thread overview]
Message-ID: <CAHY5Mee+z9Zn_0Mo_ckh85NVL3mUFzHmtGa8tpswCZKM_2FCxQ@mail.gmail.com> (raw)
In-Reply-To: <baf76b3b-c6be-4b82-b5e6-99ab080b56c3@bricart.de>

On Tue, Feb 6, 2024 at 5:44 AM Christian Bricart <christian@bricart.de> wrote:
>
> Am 28.01.24 um 17:25 schrieb Mike Gilbert:
> > […]
> > +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)
>
> despite x64, the path is always /boot/grub/i386-pc/*.mod for
> GRUB_PLATFORMS=pc
>
> Christian

Also odd to conflate -pc and -efi setups in the same news item. If you
installed to EFI, your modules are installed in
/boot/grub/x86_64-efi/. If you installed "pc", e.g. old BIOS boot, you
won't have those .efi files.


  reply	other threads:[~2024-02-06 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 16:25 [gentoo-dev] [PATCH] 2024-02-01-grub-upgrades: add news item Mike Gilbert
2024-02-05 23:44 ` Sam James
2024-02-06  6:49   ` [gentoo-dev] Typo: " Nils Freydank
2024-02-06 11:44 ` [gentoo-dev] [PATCH] " Christian Bricart
2024-02-06 14:28   ` Gordon Pettey [this message]
2024-02-06 19:27   ` 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=CAHY5Mee+z9Zn_0Mo_ckh85NVL3mUFzHmtGa8tpswCZKM_2FCxQ@mail.gmail.com \
    --to=petteyg359@gmail.com \
    --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