From: Marius Bakke <mbakke@fastmail.com>
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: Thu, 22 Feb 2018 16:06:31 +0100 [thread overview]
Message-ID: <87mv019i88.fsf@fastmail.com> (raw)
In-Reply-To: <20180220220011.737ee227@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Also, grub-hybrid is supposed to use efi so the workaround shouldn't be used with it...
Right, I had forgotten about grub-hybrid. That complicates things.
> What do you think about my direct grub patch?
That works too :-) It just felt a little "heavy-handed". I'll let
Ricardo judge which approach to take.
I do wonder if we can do better though, and maybe even fix it properly.
Ricardo: Can you post the output of `find /sys/firmware/efi -maxdepth 1`
on the affected machine? With luck, we'll find a variable that is only
present on "real" EFI.
Can you also post the contents of '/sys/firmware/efi/runtime'?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-02-22 15:07 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
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 [this message]
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=87mv019i88.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--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 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).