Werner

Feel free to pr any missing overlay here: https://github.com/armbian/linux-rockchip

moved to csc https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image tl;dr: You are using the wrong image. Get/build one for your board

current isn't ideal for any rk3588 hw anyway due to lack of hw features mainlined for now. edge or vendor working best.

Yes. This is an example of a rk3588 based board of mine: overlay_prefix=rockchip-rk3588 overlays=panthor-gpu opp-oc-24ghz The overlay names come from /boot/dtb/*/ find an overlay matching your soc and needs and enable by putting its name to overlays=. Then reboot. Having a serial console to read uboot logs can show if it has been loaded properly or in case it did not why.

Overlays can be added manually as well. Check /boot/armbianEnv.txt

Expected. current had a bare minimum of hdmi support before it became recent LTS kernel. Therefore no fixes will hit there until rollover to next LTS. Needs to be enabled. Either enable panthor overlay (the mainline panthor driver was backported to vendor kernel but is disabled by default) and install more recent mesa packages (depends on userspace). Or install proprietary mali blobs. Having or building an image with mesa-vpu extension enabled handles that for you. There is no automatic method of installing afterwards yet. https://github.com/armbian/apa/issues/20

moved

tag adjusted

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

Radxa Zero has a different soc: https://radxa.com/products/zeros/zero/ Double-check what hw you actually have

The easiest route is to simply flash it to a microsd card and boot from it. Once booted issue "armbian-install" to move the OS and boot loader to eMMC. eMMC should be accessible directly if tools like rkdeveltool or whatever that is called is used. Never used that personally, seems tricky to use. Prefer first path.

Not having correct uboot on spi can often lead to such issues. Also sometimes vendor kernel does not like mainline uboot and vice versa. This is why vendor kernel based images usually are shipped with vendor uboot which is version 2017.09 I think. Anyway glad you figured it out

I'll fix that soon Edit:done

moved since neither a review nor a tutorial. I made a writeup just a few days ago how to get an idea about how Armbian puts its kernel and uboot sources together with an example for a different board:

Armbian does not accept new boards for official support unless there is funding involved. However anyone from the community can step up and add it as community-supported.