unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Stefan <stefan-guix@vodafonemail.de>
To: phodina <phodina@protonmail.com>
Cc: Vagrant Cascadian <vagrant@debian.org>, help-guix@gnu.org
Subject: Re: U-Boot for Raspberry Pi
Date: Tue, 2 Nov 2021 14:24:38 +0100	[thread overview]
Message-ID: <6B4DB50F-085E-416D-A643-68BAE94B88AD@vodafonemail.de> (raw)
In-Reply-To: <HF8plhKYtvUJ0wEB3kslvhXIH490W6sM-ZtUBHYJMGOcnMNoq76ZGGEq4DRGjSQqbm-beS8QDLFmHsyQxwtgsbyQVzxzZ7lEbrPoZGUsUig=@protonmail.com>

Hi!

> Thanks for your amazing work! I've applied the patches and it builds the system.

Welcome, and thanks for the feedback.

> However, I ran into several issues.

Your troubles might indicate that you didn’t properly mount the ext4 and FAT file systems below /mnt. You should follow the manual regarding an EFI system¹: Mount the ext4 partition of the microSD card at /mnt and the FAT partition of the microSD card at /mnt/boot/efi – you will have to call ‘mkdir -p /mnt/boot/efi’ after mounting the ext4 partition and before mounting the FAT partition.

> Do you have different suggestion on how to invoke the guix system init command?

Please separate build and installation. First build guix as described in the manual² without any sudo but inside its build environment with the amount of cores you like to use:

$ guix environment --pure guix
$ ./bootstrap
$ ./configure --localstatedir=/var
$ make -j 4
$ exit

Then use the new guix outside its build environment to initialize the system with sudo:

$ sudo -E ./pre-inst-env guix system init --system=aarch64-linux gnu/system/examples/raspberry-pi-64.tmpl /mnt

The --system flag is needed in your case executing the command on a host PC. However, I built and installed my system directly on the Raspberry, so I didn’t use it. Also --skip-checks was not necessary in my case. But building guix with only 1 GB is meanwhile close to impossible.

Is there possibly an issue with checks when installing for another system? It could also be that these checks got “improved” but fail in this case. At least additional initrd modules are not needed. So just add the --skip-checks option, if guix complains otherwise.

I hope this will solve your issues.

The certificate issues could have been due to your unconventional use of sudo. The symlink issue must have been due to the wrong mount point of the FAT partition.


Bye

Stefan


¹ <https://guix.gnu.org/devel/devel/manual/en/guix.html#Bootloader>
² <https://guix.gnu.org/devel/devel/manual/en/guix.html#Building-from-Git>



  reply	other threads:[~2021-11-02 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-31 23:09 U-Boot for Raspberry Pi Stefan
2021-11-02 11:00 ` phodina
2021-11-02 13:24   ` Stefan [this message]
2022-02-16 15:55     ` Reza Alizadeh Majd
2022-02-18 23:12       ` Ricardo Wurmus
2022-02-21 11:08         ` Reza Alizadeh Majd
2022-02-21 11:14           ` Ricardo Wurmus
2022-02-22  7:36             ` Reza Alizadeh Majd
2022-02-22  8:30               ` Ricardo Wurmus
2022-02-22  9:05                 ` Vincent Legoll
2022-02-22  9:07                   ` Vincent Legoll
  -- strict thread matches above, loose matches on Subject: below --
2021-10-30 21:39 phodina via
2021-10-30 22:05 ` Vagrant Cascadian
2021-10-31  6:47   ` phodina

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=6B4DB50F-085E-416D-A643-68BAE94B88AD@vodafonemail.de \
    --to=stefan-guix@vodafonemail.de \
    --cc=help-guix@gnu.org \
    --cc=phodina@protonmail.com \
    --cc=vagrant@debian.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).