all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: help-guix@gnu.org
Subject: Re: cannot boot from microSD card on aarch64 machine
Date: Wed, 06 Apr 2022 10:50:44 +0200	[thread overview]
Message-ID: <87wng21teu.fsf@elephly.net> (raw)
In-Reply-To: <87ee2b5kzu.fsf@contorta>


Vagrant Cascadian <vagrant@debian.org> writes:

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

My SATA controller differs:

  01:00.0 SATA controller: JMicron Technology Corp. Device 0585

It’s good to know that it works for a different PCIe card.  Maybe I can
find some more information about the differences.

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

Yes, my board is V2.1 from 2018.

-- 
Ricardo


      reply	other threads:[~2022-04-06  8:58 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
2022-04-06  8:50               ` Ricardo Wurmus [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wng21teu.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.