debian installer on rock64

[Diego Roversi]

Hello,

today I've tested bookworm debian-installer from https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ on a rock64 but it didn't boot.

I got this error:

[ 1.806958] List of all partitions:
[ 1.807299] No filesystem could mount root, tried:
[ 1.807304]
[ 1.807892] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.808637] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0-1-arm64 #1 Debian 6.1.4-1
[ 1.809357] Hardware name: Pine64 Rock64 (DT)

It looks like the kernel don't see the mmc (or the initrd.gz from ram). Just fyi, bullseye d-i seems it works fine. Except no hdmi output and no error on Xorg.log, but this is another story :)

Thanks in advance,
Diego

[Vagrant Cascadian]

Post by Diego Roversi
today I've tested bookworm debian-installer from https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/ on a rock64 but it didn't boot.

Did you use the GTK images or the "regular" images?

Post by Diego Roversi
[ 1.807304]
[ 1.807892] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.808637] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0-1-arm64 #1 Debian 6.1.4-1
[ 1.809357] Hardware name: Pine64 Rock64 (DT)
It looks like the kernel don't see the mmc (or the initrd.gz from
ram).

Yeah, from the log it looks like the initrd was never loaded. Wild guess
would be the partition is too small to hold the initrd, presuming you
used the GTK installer... the regular installer appears to load an
initrd ok for me. (although I kind of cheated, installing u-boot
independently and dumping the partition onto a device)


live well,
vagrant

[Vagrant Cascadian]

Post by Vagrant Cascadian

Post by Diego Roversi
[ 1.807304]
[ 1.807892] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.808637] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.1.0-1-arm64 #1 Debian 6.1.4-1
[ 1.809357] Hardware name: Pine64 Rock64 (DT)
It looks like the kernel don't see the mmc (or the initrd.gz from
ram).

Yeah, from the log it looks like the initrd was never loaded. Wild guess
would be the partition is too small to hold the initrd, presuming you
used the GTK installer...

I did test images from
https://d-i.debian.org/daily-images/arm64/20230113-02:28/netboot/SD-card-images/
seem to work fine for me.

zcat firmware.rock64-rk3328.img.gz partition.img.gz | dd of=/dev/SOMEDEVICE bs=4096k

live well,
vagrant

[Diego Roversi]

On Fri, 13 Jan 2023 12:56:32 -0800

Post by Vagrant Cascadian
I did test images from
https://d-i.debian.org/daily-images/arm64/20230113-02:28/netboot/SD-card-images/
seem to work fine for me.
zcat firmware.rock64-rk3328.img.gz partition.img.gz | dd of=/dev/SOMEDEVICE bs=4096k

I found out that the problem was the u-boot on the SPI, not the d-i image. I've tried to upgrade u-boot from https://github.com/ayufan-rock64/linux-mainline-u-boot/releases/tag/2022.10-ayufan-2029-gdc3d30c8, but it was even worse, failing to read from micro sd.

Finally I've erased the SPI, and now it works fine.

Thanks again,
Diego.