We have hundreds of releases and multiple per version per board hard to tell from this which kernel or which exactly i make a wild guess and the kernel you tried is 6.12.y which isn't good for desktop. try 6.1.115 (with mesa-vpu extension, not sure if there are pre-made ones) or 6.18, 6.19 mainline kernel.

Managed to find how to solve the issue! For anyone with the same board revision (IK316Q-EMCP_V4.1) and LPDDR3 memory who is struggling to boot standard images: I tried multiple generic builds (Ophub, etc.) and DTB edits without success. The solution was using this specific pre-configured image version from the sicXnull repository. The working image is: Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz Download Link: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_24.11.0-trunk_X96q_bookworm_current_6.6.44_mate_desktop.img.xz It booted immediately. Hope this helps others with this specific hardware.

Hello!! I am looking for help to boot Armbian on a generic TV Box sold as "MXQ Pro 4K 5G". I have tried multiple images (including official and community builds from sicXnull), but I only get a black screen or signal loss immediately after the boot attempt. Device Specifications: Model on case: MXQ Pro 4K 5G Board ID: IK316Q-EMCP_V4.1 SoC: Allwinner H313 (identified as sun50iw9p1 in Android) RAM: 1GB (Single chip configuration) Storage: 8GB eMMC Current Status: I am able to boot into the stock Android. To attempt the Armbian boot, I've tryed the Power up method, the power up pressing the hidden AV switch, using the reboot update command from a terminal emulator within Android. The issue: Upon executing the reboot command, the Android system shuts down, the display signal cuts off (or stays black), and the device never initializes Armbian (no HDMI output, no LEDs blinking differently). What I have tried:

So I tried running Armbian Minimal/IoT version with kernel 6.1 and the fan is operating normally (tested it with the stress command). I didn't realize i was working with two different kernel versions. Sometimes you just need another set of eyes to look at a problem. Thanks for the help, cheers!

desktop: $ uname -a Linux opi5p-cl1 6.1.115-vendor-rk35xx #1 SMP Fri Nov 21 14:02:48 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux minimal/iot: $ uname -a Linux orangepi5-plus 6.12.58-current-rockchip64 #3 SMP PREEMPT Thu Nov 13 20:34:41 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux Good call, I'm going to download the other Minimal/IoT image that uses kernel 6.1 and give it a try. Will let you know what happens.