by adam900710 » Mon Oct 21, 2019 1:15 pm
$this->bbcode_second_pass_quote('', '
')Do not load the initramfs? Exactly what version of uboot are you using, and what commands did you use to compile it?
Obviously it doesn't load the initramfs properly.
I guess most guys don't really try to manually boot using interactive U-boot command as long as the scr can boot.
See this:
$this->bbcode_second_pass_code('', '
U-Boot 2019.10 (Oct 08 2019 - 18:05:25 +0800)
Model: Radxa ROCK Pi 4
DRAM: 3.9 GiB
Cannot find regulator pwm init_voltage
MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment
In: serial@ff1a0000
Out: serial@ff1a0000
Err: serial@ff1a0000
Model: Radxa ROCK Pi 4
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net: eth0: ethernet@fe300000
Hit any key to stop autoboot: 0
=>
=> load mmc 1:1 ${kernel_addr_r} /boot/Image
27380224 bytes read in 1730 ms (15.1 MiB/s)
=> load mmc 1:1 ${fdt_addr_r} /boot/dtbs/rockchip/rk3399-rock-pi-4.dtb
71831 bytes read in 19 ms (3.6 MiB/s)
=> fdt addr ${fdt_addr_r}
=> load mmc 1:1 ${ramdisk_addr_r} /boot/initramfs-linux.img
7378692 bytes read in 475 ms (14.8 MiB/s)
=> booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
')
See it? Just as what I found in U-boot.
Maybe in script mode, it skips the check and discard the initramfs.
And just as you expected, if loaded the uboot wrapped initramfs, everything is fine.
$this->bbcode_second_pass_code('', '
=> load mmc 1:1 ${ramdisk_addr_r} /boot/initramfs-linux.img.uboot
7378794 bytes read in 475 ms (14.8 MiB/s)
=> booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}
## Loading init Ramdisk from Legacy Image at 04000000 ...
Image Name: U-boot ramdisk
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 7378730 Bytes = 7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f5820000, end f5f2972a ... OK
Loading Device Tree to 00000000f580b000, end 00000000f581f896 ... OK
Starting kernel ...
')
And I really don't believe it matters for how I compiled the U-boot.
But you can check it in my PKGBUILD, it's just board defconfig:
https://github.com/adam900710/PKGBUILDs ... 4/PKGBUILDMaybe it's newer U-boot doing extra check in interactive mode, but even using that modern boot.txt, after boot, kernel doesn't load the initramfs properly anyway.