From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
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 22:49:19 +0100 [thread overview]
Message-ID: <87lgfnqqlc.fsf@elephly.net> (raw)
In-Reply-To: <20180220224317.36920bcb@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
>> I don’t understand this patch. How does it work?
>>
>> What is the effect of replacing /sys/firmware/efi with
>> /sys/firmware/non-efi?
>
> It won't find EFI since it's looking in the wrong place.
>
> That's what we want :)
So the value “/sys/firmware/non-efi” might as well be
“/does-not-exist”?
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?
I’m thoroughly confused.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-20 21:50 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgfnqqlc.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=30311@debbugs.gnu.org \
--cc=dannym@scratchpost.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.