unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Nathan Dehnel <ncdehnel@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 69515@debbugs.gnu.org
Subject: bug#69515: grub-efi-bootloader doesn't make multiple boot entries with efibootmgr if multiple targets are specified
Date: Sun, 3 Mar 2024 16:45:10 -0600	[thread overview]
Message-ID: <CAEEhgEt2AyEnF92aMgRhm-XrkTc8RdmQHwa2iKL9qsGhqzHkSQ@mail.gmail.com> (raw)
In-Reply-To: <87jzmjojox.fsf@gmail.com>

The configure makes only one boot entry, and if I remove one of the
disks, it disappears from the BIOS boot options. If I make another
boot entry manually with efibootmgr, it appears as a second boot
option.

On Sun, Mar 3, 2024 at 1:31 AM Oleg Pykhalov <go.wigust@gmail.com> wrote:
>
> Hi,
>
> Nathan Dehnel <ncdehnel@gmail.com> writes:
>
> >   (bootloader
> >    (bootloader-configuration
> >      (bootloader grub-efi-bootloader)
> >      (targets '("/boot/efi1" "/boot/efi2"))
> >
> > This creates multiple boot partitions, but doesn't register all of
> > them with the BIOS/create multiple boot entries
>
> It appears that the reason for the issue is that the EFI file is
> identical on both targets. Could this behavior actually be considered a
> bug? Consider the scenario of a multi-disk system; have you attempted to
> remove one of the disks and observe the boot process to determine if the
> duplicated EFI file is causing unexpected behavior?
>
> Regards,
> Oleg.




      reply	other threads:[~2024-03-03 22:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 23:01 bug#69515: grub-efi-bootloader doesn't make multiple boot entries with efibootmgr if multiple targets are specified Nathan Dehnel
2024-03-03  7:31 ` Oleg Pykhalov
2024-03-03 22:45   ` Nathan Dehnel [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEEhgEt2AyEnF92aMgRhm-XrkTc8RdmQHwa2iKL9qsGhqzHkSQ@mail.gmail.com \
    --to=ncdehnel@gmail.com \
    --cc=69515@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).