What happened?
After writing the image to the TF card, the system fails to boot properly. The built image does not place fixup*.dat and start*.elf in the RPICFG partition, and the image does not include the raspi-firmware package.
As an ordinary user, I lack in-depth knowledge of the boot process. After unpacking the image, I found that these files are actually present under /usr/lib/armbian-firmware-raspi. When I manually copied fixup*.dat and start*.elf from that directory into the RPICFG partition, the system was able to boot successfully.
How to reproduce?
./compile.sh \
BOARD=rpi4b \
BRANCH=current \
BTRFS_COMPRESSION=zstd \
BUILD_MINIMAL=yes \
COMPRESS_OUTPUTIMAGE=xz \
DISABLE_IPV6=false \
IMAGE_XZ_COMPRESSION_RATIO=9 \
KERNEL_CONFIGURE=no \
KERNEL_GIT=shallow \
NETWORKING_STACK=systemd-networkd \
RELEASE=trixie \
ROOTFS_TYPE=btrfs \
SEVENZIP=yes \
SKIP_ARMBIAN_REPO=yes
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Debian 13 Trixie
Are you building on Windows WSL2?
Relevant log URL
https://paste.armbian.com/imuxuzizat
Code of Conduct
What happened?
After writing the image to the TF card, the system fails to boot properly. The built image does not place
fixup*.datandstart*.elfin theRPICFGpartition, and the image does not include the raspi-firmware package.As an ordinary user, I lack in-depth knowledge of the boot process. After unpacking the image, I found that these files are actually present under
/usr/lib/armbian-firmware-raspi. When I manually copiedfixup*.datandstart*.elffrom that directory into the RPICFG partition, the system was able to boot successfully.How to reproduce?
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Debian 13 Trixie
Are you building on Windows WSL2?
Relevant log URL
https://paste.armbian.com/imuxuzizat
Code of Conduct