From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: GRUB EFI installation breakage
Date: Tue, 22 Aug 2017 15:34:54 +0200 [thread overview]
Message-ID: <87efs34tfl.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 70 bytes --]
Hello,
To reconfigure my system on UEFI, I had to apply this patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 474 bytes --]
modified gnu/bootloader/grub.scm
@@ -401,7 +401,8 @@ submenu \"GNU system, old configurations...\" {~%")
;; root partition.
(setenv "GRUB_ENABLE_CRYPTODISK" "y")
(unless (zero? (system* grub-install "--boot-directory" install-dir
- "--efi-directory" efi-dir))
+ ;; "--efi-directory" efi-dir
+ ))
(error "failed to install GRUB (EFI)")))))
[-- Attachment #3: Type: text/plain, Size: 731 bytes --]
Before that ‘grub-install’ would fail because ‘efi-dir’ would actually
be “/dev/sda”, which is what I have in the ‘device’ field of
‘grub-configuration’.
Removing the “--efi-directory” solves the problem because ‘grub-install’
automatically determines that the EFI directory is mounted at /boot/efi.
I think 2941b347b664a3d3114de0ac95e28db78db66144 is bogus because it
assumes that the second argument of the gexp’d lambda is ‘efi-dir’,
where in fact it is the ‘device’ field of the bootloader config.
So what is the preferred fix? Simply remove “--efi-directory” like I
did above, and rename ‘efi-dir’ to ‘device’ to avoid the ambiguity?
Thoughts?
Ludo’.
next reply other threads:[~2017-08-22 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 13:34 Ludovic Courtès [this message]
2017-08-22 14:47 ` GRUB EFI installation breakage Efraim Flashner
2017-08-22 20:00 ` Marius Bakke
2017-08-22 22:25 ` Ludovic Courtès
2017-08-23 9:14 ` Andy Wingo
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=87efs34tfl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=wingo@igalia.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).