[5.10.69-4] Error: kernel_comp_addr_r or kernel_comp_size is not provided!

[MichaIng]

With the latest kernel package, U-Boot fails to load boot.scr, throwing the following error:

## Executing script at 01600000
initrdsize = 0xc49323
kernel_comp_addr_r or kernel_comp_size is not provided!
SCRIPT FAILED: continuing...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
...

It seems to fallback to extlinux, but fails to load the device tree then:

Retrieving file: /dtbs/5.10.69-4-amlogic-g37ae4051315a/amlogic/amlogic/meson-g12a-radxa-zero.dtb
Failed to load '/dtbs/5.10.69-4-amlogic-g37ae4051315a/amlogic/amlogic/meson-g12a-radxa-zero.dtb'
kernel_comp_addr_r or kernel_comp_size is not provided!

Reason is the doubled amlogic path element, which seems to be due to:

• devicetreedir /dtbs/5.10.69-4-amlogic-g37ae4051315a/amlogic in /boot/extlinux/extlinux.conf
• fdtfile=amlogic/meson-g12a-radxa-zero.dtb in /boot/uEnv.txt
• and I suspect that both are concatenated. Removing that path element either in extlinux.conf or in uEnv.txt resolves the issue, but removing it in uEnv.txt breaks boot.scr, of course.

[MichaIng]

As a workaround, both variables can be defined in uEnv.txt:

kernel_comp_addr_r=0x19000000
kernel_comp_size=0x04000000

This sets the RAM address for the uncompressed kernel to 400 MiB and with a maximum 100 MiB. There shouldn't be any collision since the largest RAM address otherwise is the initramfs, being loaded to ~300 MiB. With the above, the system boots via boot.scr and not via extlinux, as intended.

[StephenInVamrs]

Can you provide me the steps to reproduce this issue?

[MichaIng]

1. Boot this image: https://github.com/radxa/radxa-zero-images-released/releases/download/radxa-zero-v20211010/zero_debian_buster_xfce4_arm64_20211010_0810-mbr.img.gz
2. apt install linux-image-5.10.69-4-amlogic-g37ae4051315a
3. Reboot with serial console attached to see the above logs. It falls back to extlinux but enters a boot loop due to: #6