unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 30311@debbugs.gnu.org
Subject: bug#30311: efi-less grub install fails
Date: Thu, 01 Feb 2018 00:55:29 +0100	[thread overview]
Message-ID: <87y3kdoa6m.fsf@gnu.org> (raw)
In-Reply-To: <idjmv0t503l.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Wed, 31 Jan 2018 19:55:58 +0100")

Heya,

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:

> “guix system init” fails with a configuration file that specifies
> grub-bootloader (not grub-efi-bootloader).
>
> “grub-install” reports an error about “lib/grub/x86_64-efi/modinfo.sh”
> not being available.  It suggests passing “--target” or “--device”.
>
> Our invocation of grub-install does not include a “--target” argument.
> Only after I edited it to pass “--target=i386-pc” did “guix system init”
> pass.
>
> This is on an x86_64 laptop where “legacy” BIOS booting is enabled.

To complement from what we’ve discussed on IRC:

  • It’s a UEFI laptop with legacy-BIOS enabled, but UEFI still.

  • AIUI the installation image boots in UEFI mode on UEFI machines, and
    then ‘grub-install’ (probably via ‘efivar’ or /sys or similar)
    detects that it’s UEFI, decides that the target is thus
    “x86_64-efi”, and fails because it lacks the EFI files.

I can think of two possible workarounds:

  1. Default to ‘grub-hybrid’.  But in that case, you’d have done a UEFI
     install unconditionally.

  2. For ‘grub-bootloader’ (not EFI), always pass ‘--target=i386-pc’.

Danny, Marius, thoughts?  :-)

Ludo’.

  parent reply	other threads:[~2018-01-31 23:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 18:55 bug#30311: efi-less grub install fails Ricardo Wurmus
2018-01-31 23:34 ` Danny Milosavljevic
2018-02-01 12:40   ` Marius Bakke
2018-02-18 11:28     ` Ricardo Wurmus
2018-01-31 23:55 ` Ludovic Courtès [this message]
2018-02-18 16:20 ` Mark H Weaver
2018-02-18 16:49   ` Danny Milosavljevic
2018-02-20 21:40     ` Ricardo Wurmus
2018-02-20 21:43       ` Danny Milosavljevic
2018-02-20 21:49         ` Ricardo Wurmus
2018-02-20 22:00           ` Danny Milosavljevic
2018-03-26 21:15             ` Danny Milosavljevic
2018-02-20  3:21   ` Marius Bakke
2018-02-20  3:46     ` Marius Bakke
2018-02-20 20:54       ` Danny Milosavljevic
2018-02-20 21:00       ` Danny Milosavljevic
2018-02-22 15:06         ` Marius Bakke
2018-02-22 15:47           ` Ricardo Wurmus
2018-02-23 11:30             ` Marius Bakke

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=87y3kdoa6m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=30311@debbugs.gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).