Werner

If your device has UEFI support: https://www.armbian.com/uefi-arm64/ If not, no. Generic support w/o standardization is impossible.

Probably Amlogic. No clue though why they decided to alter the naming for debug console on this soc.

Swapoff wasn't successful, got oom killed. Try disabling zram in /etc/default/armbian-whateverthefilewascalledidontremember and reboot. I assume noble needs more memory be default which is quite common for more recent OS to take more memory than older ones. And with its max at 512M the OPi Zero is pretty limited already. You can try to add a swap space on the sdcard which isn't recommended but might be necessary to get it to compile. Disable afterwards. Also this will most likely affect build time since sd card is quite slow and swapping consumes time. Also set vm.swappiness to 1 in /etc/sysctl.conf if you want to try this. Moved to userspace

mainline support for the rk3588 soc in 6.10 is far from feature-complete. If need most hw features working use vendor 6.1.y kernel. To force rebuild of a kernel instead of downloaded artifact use ARTIFACT_IGNORE_CACHE=yes switch.

You are not using Armbian. You are using a fork of Armbian that uses the name Armbian without permission, confusing users that they would receive some sort of support at official forums (here to say). Also they do not contribute to the core development process. Please ask where you got the software you are using from. Thank you.

Tried 6.11 rc edge?

https://docs.armbian.com/User-Guide_FAQ/#i-have-a-tv-box-or-tablet-from-insert-random-vendor-can-i-use-armbian-on-it

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

From these logs I cannot see any recent packages installed. Everything seems to be 23.02 which cannot be supported.

Check packages on hold and unhold them. Perhaps this helps.

Nobody knows what are even trying to accomplish.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Is the code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-firmware-full package installed? If not please do so via apt, reboot and retry.

supposedly not a powering issue. moved.

https://debug.armbian.de

Those ratings don't necessary have to mean anything. A proper 2A supply can be better than a crappy 4A one. A good PSU keeps the voltage constant up to its rating and then shuts off due to over-current protection. The voltage of a poor PSU will start to break down under load, often long before its max current rating is reached. The result is having weird issues with your board. At customer grade sector its a matter of luck to get something proper. The only way to be certain, if you cannot do measurements by yourself to verify, is picking up something industrial grade. Also most SBCs like being fed with slight overvoltage. About ~5.2 volts at the source. Last but not least to compensate for losses across wiring and connectors. Some PSUs already do that. Even when labeled 5 volts measurements usually show something between 5.1 and 5.4 volts. Depending on quality like described above this breaks down under load or is kept constant.

https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel

Yes this is some generic issue. We're still investigating. Since this is an issue with the build framework please refer to the proper bug report here: https://github.com/armbian/build/issues/7054

clear your code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } cache directory and retry

Not sure why this post should be a PSU issue. Moved.

Think about it

No idea if these are even exposed. Anyway check the datasheet for the board. I guess there is some schematic for it around on the web.

https://github.com/armbian/linux-rockchip/pull/217

Logs excerpts are usually useless. Provide logs as suggested from the build output: Try to build from main instread (I assume you tried 24.05 branch)

Check your /etc/sudoers file to change sudo behavior. ????