unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 45517@debbugs.gnu.org
Subject: bug#45517: Failed boot on arm32 with u-boot due to missing requirements with the distro boot protocol
Date: Wed, 30 Dec 2020 15:35:48 +0100	[thread overview]
Message-ID: <87sg7n5pkr.fsf@gnu.org> (raw)
In-Reply-To: <20201229033439.60b2a9ff@primarylaptop.localdomain> (Denis Carikli's message of "Tue, 29 Dec 2020 03:34:39 +0100")


Hello Denis,

> I then built it with:
>> cp `guix system disk-image --target=arm-linux-gnueabihf lime2.scm` \
>>     guix.img
>
> However when booting the image, u-boot doesn't find
> /boot/extlinux/extlinux.conf.
>
> However running the following command in u-boot makes the board boot:
>> sysboot mmc 0:2 any $scriptaddr /boot/extlinux/extlinux.conf
>
> When we look at the resulting image with fdisk -l we have:
>> Device     Boot Start     End Sectors  Size Id Type
>> guix.img1        2048   83967   81920   40M ef EFI (FAT-12/16/32)
>> guix.img2       83968 3301783 3217816  1.5G 83 Linux

The default image type creates an EFI partition which is not desirable
here. You should try again running this instead:

--8<---------------cut here---------------start------------->8---
guix system disk-image -t arm32-raw lime2.scm
--8<---------------cut here---------------end--------------->8---

Thanks,

Mathieu




  reply	other threads:[~2020-12-30 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29  2:34 bug#45517: Failed boot on arm32 with u-boot due to missing requirements with the distro boot protocol Denis 'GNUtoo' Carikli
2020-12-30 14:35 ` Mathieu Othacehe [this message]
2021-01-02  2:54   ` Denis 'GNUtoo' Carikli
2021-01-02 10:23     ` Mathieu Othacehe
2021-01-03 22:15       ` Danny Milosavljevic

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=87sg7n5pkr.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=45517@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).