unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Vagrant Cascadian <vagrant@debian.org>, help-guix@gnu.org
Subject: Re: cannot boot from microSD card on aarch64 machine
Date: Thu, 7 Apr 2022 00:26:55 +0200	[thread overview]
Message-ID: <20220407002655.23ceae11@primarylaptop.localdomain> (raw)
In-Reply-To: <874k4g18x3.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

On Wed, 02 Mar 2022 19:52:18 +0100
Ricardo Wurmus <rekado@elephly.net> wrote:

> Do I need to prepare the microSD card at all?  There’s no
> documentation in the manual, so I have no idea what to do with it
> prior to “guix system init”.  Looking at the code I assumed that the
> disk-image-installer procedures take care of placing whatever blobs
> are needed at the expected locations.

Long time ago I managed to boot Guix on a Lime 1 A20 and it worked. 

I used a command similar to this one (probably the equivalent with guix
image that is now deprecated or removed):
> guix system image --target=arm-linux-gnueabihf -t raw-with-offset \
> system.scm

This takes care of writing the bootloader at the right location on the
image. However I'm not sure what happens if the bootloader gets too big
and get overwritten by the GPT or MBR partition table.

With the command above, you'll have to adjust the target for ARM 64bit.

The issue for me is that at some point the boot broke: I saw u-boot and
the kernel and the init on the serial port, but the init never
completed and I didn't find enough time to correctly investigate the
issue. But at least the bootloader is probably still working fine.

In my TODO list I also wanted to add u-boot for qemu_arm
(qemu_arm_defconfig) and qemu_arm64 (qemu_arm64_defconfig) to be able
to enable people to more easily test ARM support without any special
hardware, but that doesn't advance fast at all due to the lack of time.

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-04-06 22:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02 11:37 cannot boot from microSD card on aarch64 machine Ricardo Wurmus
2022-03-02 17:19 ` Efraim Flashner
2022-03-02 18:45   ` Ricardo Wurmus
2022-03-02 18:19 ` Vagrant Cascadian
2022-03-02 18:52   ` Ricardo Wurmus
2022-04-06 22:26     ` Denis 'GNUtoo' Carikli [this message]
2022-03-29 21:45   ` Ricardo Wurmus
2022-03-16 14:34 ` Maxim Cournoyer
2022-03-29 21:35   ` Ricardo Wurmus
2022-03-30  4:49     ` Maxim Cournoyer
2022-04-02  1:10     ` Vagrant Cascadian
2022-04-02 16:15       ` Ricardo Wurmus
2022-04-02 22:51         ` Vagrant Cascadian
2022-04-03  5:08           ` Ricardo Wurmus
2022-04-05 20:32             ` Vagrant Cascadian
2022-04-06  8:50               ` Ricardo Wurmus

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=20220407002655.23ceae11@primarylaptop.localdomain \
    --to=gnutoo@cyberdimension.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    --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).