06-29-2021, 02:48 PM
(06-29-2021, 02:55 AM)MisterA Wrote: Yeah, I did all that: checked the filesystem, could mount it on another linux box. Flashed several images (debian, armbian focal with or without desktop) several times. There is one constant: as soon as it's 5.x kernel => no boot from usb/eMMC/NVMe
See also the post I referenced, exactly the same issue as I'm experiencing.
https://forum.armbian.com/topic/14724-ro...-v44-does/
I'll repost my previous reply from page 8 for this:
sigmaris Wrote:FWIW, if you're seeing log messages about /scripts/local-premount and so on like in the photo, that's booted up the Linux kernel and got as far as running the scripts on initramfs. So U-Boot may not be the issue here. I would suspect the scripts on initramfs are having trouble finding the root filesystem to mount it and continue booting. Look at your root= argument in the kernel command line, check it's specifying the filesystem you want
I see in Armbian, by default, they pass an argument to the kernel telling it to use /dev/mmcblk0p1 as the root device, on recent 5.x kernels I don't think that corresponds to any storage device. There was a change added to the device tree recently to make the numbering of mmc devices on RK3399 static rather than depending on probe order. On a 5.10 DT it looks like the SD card is /dev/mmcblk1 and the eMMC is /dev/mmcblk2. So if that default variable isn't overridden in /boot/armbianEnv.txt then that could cause the inability to find the root filesystem in the screenshot. If you know the UUID of the filesystem on your eMMC (you can find this by using the blkid command from Linux with the eMMC attached), try setting rootdev=UUID=<replace with the real UUID here> in /boot/armbianEnv.txt - specifying the root by UUID should let the initramfs scripts find it no matter what the device name/number is.
