evaldas325

I solved the issue, I think it was gcc 13. robertoj answer pushed me towards building inside some virtual env instead of host machine. Basically compile script installs host package gcc-aarch64-linux-gnu and my debian host distro has already aarch64 gcc 13 dependency for this package. But this happens only if you do not have docker binary installed. If compile.sh detects docker binary then pulls ubuntu jammy image automatically with aarch64 gcc 11 and compiles inside docker jammy environment, which is the recommended way to go.

Hey, I've tried to build Armbian kernel for my orangepizero3 1GB board from Armbian main branch sources but always stuck on "Starting kernel ..." message, no leds come up, board seems dead. Tried building minimal bookworm both current and edge versions with unchanged stock config. Also verbosity is set to 7. If I choose not to customize/build kernel during initial compile.sh prompt then the whole custom built root image works perfectly with the stock prebuilt kernel. But as soon as I replace stock kernel deb with my own built kernel deb, or use the whole my custom built root+kernel image, then booting stops. Before digging deeper - is this known issue, is there any patch for orangepizero3 missing in the repo, or hidden in some branch which I missed in the forums? I know this board is not officially supported yet so obviously issues expected.