From: Dmitry Matveyev <public@greenfork.me>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: guix deploy: modinfo.sh doesn't exist error
Date: Mon, 23 Jan 2023 13:27:14 +0600 [thread overview]
Message-ID: <87ilgxhfk6.fsf@greenfork.me> (raw)
In-Reply-To: <87edrmh8jd.fsf@nckx>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hi, Tobias!
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> Dmitry Matveyev 写道：
>> /gnu/store/ch9q9w5zbvgq8srr6dscq6hdf03pfqb4-grub-efi-2.06…
>
> Note the ‘-efi’.
>
>> …/lib/grub/i386-pc/modinfo.sh
>
> Note the ‘i386-pc’, i.e., non-UEFI.
>
> This GRUB thinks it's installing in BIOS/CSM mode, but was not built to support
> this, and fails.
>
> Is the ‘minimal ISO image’ booted in UEFI mode, that is, does /sys/firmware/efi
> exist there?
>
> If so, is the ESP actually mounted at /boot/efi?
It was indeed not booted in the UEFI mode, as I gathered from Vultr's
tutorial[1] on installing Gentoo, the volumes should use MBR anyway, so
my attempt to use both UEFI for ISO image and installation failed as
well.
[1]: https://www.vultr.com/docs/installing-gentoo-linux-on-a-vultr-server/
I have changed both ISO and deploy config to using MBR, now it is a
different error, so some progress at least. Thank you!
Best,
Dmitry.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
prev parent reply other threads:[~2023-01-23 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 15:20 guix deploy: modinfo.sh doesn't exist error Dmitry Matveyev
2023-01-22 15:45 ` Tobias Geerinckx-Rice
2023-01-23 7:27 ` Dmitry Matveyev [this message]
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=87ilgxhfk6.fsf@greenfork.me \
--to=public@greenfork.me \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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.
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).