Werner

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. ????

opi5pro is wip, therefore moved to staging. website falsely claims it is supported.

Would make more sense if the wiringop maintainers change to /etc/armbian-release since orangepi images are based on Armbian. They forked the framework years ago, did "sed s/armbian/orangepi/g" across the whole code and added hacks to make their boards somehow work.

Pre-made images for download are compressed while building an image by yourself is not by default. use xz to compress it and you should get to your desired ~250M

have you removed 10-dhcp-all-interfaces.yaml:?

I don't know. Not my department. Just passing information. If you want to dive into how things work (and can do improvements) everything is there: https://github.com/armbian

Repo rebuild is running

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Doesn't look like a kernel that came from Armbian.

https://docs.armbian.com/User-Guide_FAQ/#can-i-upgrade-my-userspace-flavor-like-bullseye-to-bookworm-or-jammy-to-noble

https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script

https://debug.armbian.de

I suggest to ask where you got this image from. We cannot help with 3rd party OS.

Not sure if they can be brought back to sync since I see a similar behavior on my board. However you can try to disable/re-enable the heartbeat or disable for certain colors if possible. Refer to https://docs.armbian.com/User-Guide_FAQ/#can-this-behaviour-adjusteddisabled

hdmi worked on edge until something like rc4 or so an then broke. We'll see if 6.11-rc fixes this again. End users are still recommended to use vendor 6.1 branch.

Feel free to make adjustments, test and send a PR to fix this

Doesn't sound like a genuine Armbian image.