From: Vagrant Cascadian <vagrant@debian.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: cannot boot from microSD card on aarch64 machine
Date: Tue, 05 Apr 2022 13:32:53 -0700 [thread overview]
Message-ID: <87ee2b5kzu.fsf@contorta> (raw)
In-Reply-To: <871qye4u6k.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
On 2022-04-03, Ricardo Wurmus wrote:
>> On 2022-04-02, Ricardo Wurmus wrote:
>>> Vagrant Cascadian <vagrant@debian.org> writes:
>> Device 0: (1:0) Vendor: ATA Prod.: Faspeed F510-120 Rev: O080
>> Type: Hard Disk
>> Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
>> ... is now current device
>> Scanning scsi 0:2...
>> Found /boot/extlinux/extlinux.conf
>> Retrieving file: /boot/extlinux/extlinux.conf
>> Ignoring unknown command: UI
>> 1: GNU with Linux-Libre 5.17
...
> Hmm, unfortunately, this is not working for me :(
>
> I applied the patch, built u-boot-rockpro64-rk3399 with
>
> ./pre-inst-env guix build u-boot-rockpro64-rk3399
Most perplexing. Since it at least worked for me, I went ahead and
pushed to master with the u-boot 2022.04 update.
> Maybe I made a mistake that would seem really obvious to others?
Nothing obvious so far, unfortunately...
My best guess is some difference in actual board model, card model, etc.
$ lspci
00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port
01:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
Is your board a v2.1 ? The version is clearly printed on the board next
to the CPU. I'm not sure what the differences are with the v2 model, or
if there are newer variants.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-04-05 20:35 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
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 [this message]
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=87ee2b5kzu.fsf@contorta \
--to=vagrant@debian.org \
--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).