11-15-2020, 03:51 AM
(This post was last modified: 11-15-2020, 03:54 AM by n4tter4ngell.)
(11-14-2020, 03:47 AM)kuleszdl Wrote: @n4tter4ngell Thank you for this update! Sounds quite interesting, but I would be interested in why the kernel did not boot for you using my approach. Is this a bug in the newer unstable kernels? And could you describe the error message, please?This is the problem I experienced (someone else reported it): https://bugs.debian.org/cgi-bin/bugrepor...bug=973323
Imho, uboot should not have issues with FAT vs. ext4? And did you install directly to SSD or did you use only the microSD card like I did?
Well, technically I can't be sure the problem is really due to u-boot. U-boot starts as expected from the SD-card, but the kernel doesn't boot, it hangs at "Booting using the fdt blob at 0x01f00000". The FAT environment referenced as I understand it is it set in rockpro64-rk3399_defconfig, it doesn't seem to refer to the file system on the SD-card.
When you wrote your guide, what kernel version was the Debian unstable using at the time? Mine was at 5.9.0-1. It occurred to me I could have tried the kernel in buster-backports, but I haven't done that yet. I believe it's still at 5.8.10-1.
I installed root directly on the SSD. The debian-unstable installer image creates a FAT-partition for the installer on the SD-card, after leaving space for u-boot with the correct offset. I simply created /boot as the second partiton on the same SD-card.
And this is the bug report for dropbear-initramfs as mentioned, with a workaround: https://bugs.debian.org/cgi-bin/bugrepor...bug=968519