07-17-2021, 02:05 PM
Tried on the SD card before yanking the mmc. This on my host computer:
I had the same problem, hung at the manjaro splash screen.
So I pulled the emmc and plugged it into my USB stick. And the partition table does NOT look like ayufan buster:
That looks like the Manjaro partition scheme.
So WTF was I dd'ing to when I first tried to flash the emmc with ayufan?!? Was it all just cached because I never ran `sync` ? That seems really unlikely... But I checked the source device ID for the root partition, and dd'ed to the other device.
Is it possible that I booted off of some bizarre mix of mounts? How does uboot decide which partition becomes / ?
Code:
# start with a manjaro image. (which works for uboot but hangs on splash)
sudo dd if=Manjaro-ARM-kde-plasma-pbpro-20.12.img of=/dev/mmcblk0 bs=512 status=progress
# copy the root partition from ayufan buster-containers.
sudo dd if=buster-containers-rock64-0.11.0-1185-arm64.img of=/dev/mmcblk0p2 bs=512 skip=524288 status=progress
I had the same problem, hung at the manjaro splash screen.
So I pulled the emmc and plugged it into my USB stick. And the partition table does NOT look like ayufan buster:
Code:
Disk /dev/sda: 58,24 GiB, 62537072640 bytes, 122142720 sectors
Disk model: STORAGE DEVICE
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E96A8F3C-0431-4043-8BFE-2D57A1A4CE67
Device Start End Sectors Size Type
/dev/sda1 62500 500000 437501 213,6M Linux filesystem
/dev/sda4 524288 122142686 121618399 58G Linux filesystem
So WTF was I dd'ing to when I first tried to flash the emmc with ayufan?!? Was it all just cached because I never ran `sync` ? That seems really unlikely... But I checked the source device ID for the root partition, and dd'ed to the other device.
Is it possible that I booted off of some bizarre mix of mounts? How does uboot decide which partition becomes / ?