all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sat, 02 Apr 2022 15:51:57 -0700	[thread overview]
Message-ID: <877d875caa.fsf@contorta> (raw)
In-Reply-To: <87ilrr4g16.fsf@elephly.net>

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

On 2022-04-02, Ricardo Wurmus wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>> I was able to get it to work! With your updated patch to disable openssl
>> (and rebasing against newer u-boot), and the phase modifying the config
>> and the the rockchip include file to add support for SCSI devices.
>>
>> The netbsd patches weren't needed with 2022.04-rc5.
>
> Oh, that’s great!

It really is, thanks for getting it as far as you did!

Although very mildly disappointed that this might deprioritize making
split /boot in guix a reality. :)


> Do you have patches for the u-boot upgrade that I could test?

https://www.aikidev.net/~vagrant/guix/u-boot-2022.04-rc5-with-rockpro64-scsi.patch

Pretty similar to what you had already, with some added native-inputs
for the newer u-boot version, minor adjustments to the patch to disable
openssl, and I only tweaked the upstream files in the
u-boot-rockpro64-rk3399 package, not for all u-boot packages. There is
also an unrelated extraneous patch, but I left it out of the above patch
for brevity.

I think it *might* be possible to get the patches a little
smaller... and of course should get submitted upstream!

I'd consider pushing the updates now, but u-boot 2022.04 is planned to
be released monday, so may as well wait till then.


> Are you using a PCIe card with your rockpro64?

Yup. Pretty sure it's whatever PCIe dual-port sata card I bought right
along with the rockpro64.

U-boot is still on microSD, but it loads the kernel+initrd+dtb from
SCSI. The scsi target ends up pretty low in the boot order, so you have
to either manually set the boot_targets or make sure your mmc/nvme
devices aren't bootable (e.g. change partition type, rename boot
extlinux.conf, etc.):

  Hit any key to stop autoboot:  0
  => printenv boot_targets
  boot_targets=mmc1 mmc0 nvme0 scsi0 usb0 pxe dhcp sf0
  => setenv boot_targets scsi0
  => boot
  scanning bus for devices...
  SATA link 0 timeout.
  Target spinup took 0 ms.
  AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
  flags: 64bit ncq stag led clo pmp pio slum part ccc sxs
    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)
  
  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
  Retrieving file: /gnu/store/fxrc92smbx16k29fw8yz1s0mi7nslnan-raw-initrd/initrd.cpio.gz
  Retrieving file: /gnu/store/z5kqlcqf4r0hpyj6cdkcylh3gmcp4x9x-linux-libre-5.17/Image
  append: root=/dev/sda2 gnu.system=/gnu/store/fz4g427hcdjp70wh7rjh88vrvwi8r5yp-system gnu.load=/gnu/store/fz4g427hcdjp70wh7rjh88vrvwi8r5yp-system/boot modprobe.blacklist=usbmouse,usbkbd quiet
  Retrieving file: /gnu/store/z5kqlcqf4r0hpyj6cdkcylh3gmcp4x9x-linux-libre-5.17/lib/dtbs/rockchip/rk3399-rockpro64.dtb


Happy guixing on your shiny rockpro64!


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2022-04-02 22:52 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 [this message]
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

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

  git send-email \
    --in-reply-to=877d875caa.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.
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.