From: Danny Milosavljevic <dannym@scratchpost.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>, 30311@debbugs.gnu.org
Subject: bug#30311: efi-less grub install fails
Date: Tue, 20 Feb 2018 23:00:27 +0100 [thread overview]
Message-ID: <20180220230027.1884531a@scratchpost.org> (raw)
In-Reply-To: <87lgfnqqlc.fsf@elephly.net>
Hi Ricardo,
On Tue, 20 Feb 2018 22:49:19 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:
> So the value “/sys/firmware/non-efi” might as well be
> “/does-not-exist”?
Yes.
> Your patch subject says “Make sure that non-EFI grub doesn't try to use
> EFI”, but the problem I had was that GRUB insisted on being passed a
> “--target” option.
> That was with a GRUB installation on a system in
> legacy mode. Do you mean that this failed because GRUB erroneously
> attempted an EFI installation?
Yes, I think so.
There's a default-platform function in grub which determines the default
platform to use at runtime if you don't specify one. It one checks for
the existence of /sys/firmware/efi, and if so, returns "i386-efi" or
"x86_64-efi" (see ./grub-core/osdep/linux/platform.c).
Grub's "configure" script has the ability to select which platform you
want to compile. For the "grub" package, we choose i386, and for the
"grub-efi" package, we choose i386-efi.
The "grub-hybrid" package unions the "grub" and "grub-efi" packages,
preferring files from the "grub-efi" package. I think this
configuration is what upstream actually tests (only).
In the "grub" package we then had the situation that it was compiled
for i386 (not EFI) but THEIR OWN default-platform function specified
to use i386-efi which is some seriously strange stuff.
Do you think that this was not the cause?
next prev parent reply other threads:[~2018-02-20 22:01 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
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 [this message]
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=20180220230027.1884531a@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30311@debbugs.gnu.org \
--cc=rekado@elephly.net \
--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).