From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: cannot boot from microSD card on aarch64 machine
Date: Wed, 30 Mar 2022 00:49:27 -0400 [thread overview]
Message-ID: <87fsn0ujs8.fsf@gmail.com> (raw)
In-Reply-To: <87wngc77qz.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 29 Mar 2022 23:35:52 +0200")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi,
>
>>> I mounted the target disk (an SSD) at /mnt, made sure that the microSD
>>> card was inserted, unmounted, and available at /dev/mmcblk1, and then
>>> ran
>>>
>>> guix system init config.scm /mnt
>>>
>>> This was successful.
>>>
>>> Unfortunately, rebooting failed. There is seemingly no activity at all
>>> when I power on the board, so something’s not right with how u-boot was
>>> installed on the microSD card.
>>>
>>> Does it perhaps install the u-boot files at the wrong offsets? How
>>> would I begin to debug this?
>>>
>>> I’d appreciate any hints.
>>
>> Sorry, I don't have any clue to offer, but were you able to solve or
>> workaround your problem?
>
> Not quite, but I’ve learned more and understand the problem better.
>
> I manually copied the two u-boot files to the expected offsets on the
> microsd card, and that let me boot Guix System from USB. But I have so
> far been unsuccessful in my attempts to do this automatically as part of
> “guix system init” (I haven’t tried this much) or to successfully patch
> u-boot to boot from the SSD on the PCIe card (I have tried this a
> lot).
Heh, sounds tricky.
> My next step is to attempt to install the whole system onto the microsd
> card, just to end up with a usable system. If that works then nothing
> is wrong with Guix (except for a lack of documentation), but it would be
> a disappointing workaround.
>
> I think it should be possible to patch u-boot to initialize the PCIe
> card and boot from the attached disk (with the patched u-boot residing
> on the microsd card). I tried the relevant subset of the netbsd
> patches, but the CPU keeps resetting after (successfully) enumerating
> the PCI devices.
If I recall from my limited experience with an embedded ARM, you'd have
to register the newly supported hardware in the device tree of
U-Boot/the kernel; do the patches applied take care of that?
> I hope I can make some more time for this soon and overcome that last
> hurdle — and then write a cookbook entry for all this :)
I wish you luck!
Cheers,
Maxim
next prev parent reply other threads:[~2022-03-30 4:49 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
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 [this message]
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=87fsn0ujs8.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).