From: Martin Castillo <castilma@uni-bremen.de>
To: help-guix@gnu.org
Subject: Re: Create new EFI guixSD installaton from existing bios guixsd installation
Date: Thu, 17 Feb 2022 14:33:22 +0100 [thread overview]
Message-ID: <b1f9dd82-e7d4-3fda-b7d2-2ab73b3d15bd@uni-bremen.de> (raw)
In-Reply-To: <62567e4e-795f-8606-60b9-f6f5fa8190ac@uni-bremen.de>
[-- Attachment #1.1: Type: text/plain, Size: 1204 bytes --]
I'm back.
On 17.02.22 01:40, Martin Castillo wrote:
> But here I did not know how to proceed? There is no grub-install in this
> chrooted /gnu/store(, which is weird, because a complete system should
> contain all files to update itself, right?).
>
> What am I missing?
> Or can you only create an EFI system installation when you're already
> running on one?
So I ran the install image in qemu with EFI firmware and ran through the
graphical installer. The guided graphical install failed, manually
running guix system init worked. You can find the outputs under [1].
Looks like a bug, but I have no idea how to give you more info.
To summarize:
1. I wish it would be possible to system init an efi system from a bios
system.
2. The guided gui installer should not fail when installing inside qemu
with EFI. The qemu cmdline was
$ qemu-system-x86_64 -m 2048 -smp 3 -enable-kvm \
-bios /usr/share/edk2-ovmf/x64/OVMF.fd \
-nic user,model=virtio-net-pci -boot menu=on,order=d \
-drive file=/dev/nbd1 \
-drive media=cdrom,file=guix-system-install-1.3.0.x86_64-linux.iso
Martin
[1]: https://seafile.zfn.uni-bremen.de/d/e9acc264718f4ae7b703/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2022-02-17 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 0:40 Create new EFI guixSD installaton from existing bios guixsd installation Martin Castillo
2022-02-17 13:33 ` Martin Castillo [this message]
2022-02-17 14:06 ` pelzflorian (Florian Pelz)
-- strict thread matches above, loose matches on Subject: below --
2022-02-17 0:03 Martin Castillo
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=b1f9dd82-e7d4-3fda-b7d2-2ab73b3d15bd@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=help-guix@gnu.org \
/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).