From: Vagrant Cascadian <vagrant@debian.org>
To: Efraim Flashner <efraim@flashner.co.il>,
paul <goodoldpaul@autistici.org>
Cc: help-guix@gnu.org
Subject: Re: Pinebook Pro boot from NVME
Date: Sun, 15 Oct 2023 10:21:39 -0700 [thread overview]
Message-ID: <878r833ios.fsf@contorta> (raw)
In-Reply-To: <ZSuFJyZIlfTjF3v3@3900XT>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On 2023-10-15, Efraim Flashner wrote:
> On Thu, Oct 12, 2023 at 11:27:37PM +0200, paul wrote:
>> Could you please elaborate on the correct way to boot a Guix system with tow
>> boot? I'm not very experienced but, since I run tow boot, how can I build a
>> correct image without u-boot?
>
> Here's a link¹ to my pinebookpro config. The short version is you need
> to change the bootloader to use grub-efi (apparently I went with
> grub-efi-removable-bootloader but I don't remember why)
>
> (bootloader
> (bootloader-configuration
> (bootloader grub-efi-removable-bootloader)
> (targets '("/boot/efi"))
> (keyboard-layout keyboard-layout)))
Presumably used grub-efi-removable-bootloader because the u-boot
implementation does not support using EFI variables, and so you have to
use the generic boot location (e.g. ../efi/boot/bootaa64.efi
vs. ../efi/guix/grubaa64.efi).
I would imagine tow-boot would also support the syslinux-style menus
(extlinux.conf) generated by guix as well... there was some way to
generate them without actually installing u-boot (although tow-boot
should make installing u-boot irrelevent and neither helpful nor
harmful).
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-10-15 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 9:42 Pinebook Pro boot from NVME paul via
2023-10-12 4:41 ` Vagrant Cascadian
2023-10-12 21:27 ` paul
2023-10-15 6:22 ` Efraim Flashner
2023-10-15 17:21 ` Vagrant Cascadian [this message]
2023-10-17 22:02 ` paul via
2023-10-18 10:22 ` Efraim Flashner
2023-10-19 12:30 ` paul via
2023-10-28 21:19 ` Vagrant Cascadian
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=878r833ios.fsf@contorta \
--to=vagrant@debian.org \
--cc=efraim@flashner.co.il \
--cc=goodoldpaul@autistici.org \
--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.
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.