Those are images from BigTreeTech, not Armbian. Official Armbian images for CB1 are here: https://www.armbian.com/bigtreetech-cb1/ If you want to use vendor images, you should report your issue to BigTreeTech then.

https://www.cnx-software.com/2025/10/25/35-orange-pi-4-pro-an-allwinner-a733-edge-ai-sbc-with-up-to-16gb-lpddr5-wifi-6/ https://www.cnx-software.com/2025/07/07/allwinner-a527-t527-and-a733-datasheets-user-manuals-and-linux-sdk-released/ http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4-Pro.html Another Allwinner board dropped figuring out the wifi chip is always hard, seem to be https://www.taobao.com/list/item/931793873067.htm https://pine64.sfo3.cdn.digitaloceanspaces.com/doc/datasheet/oz64/AIC8800DC Datasheet v1.0.pdf as usual, it is uncertain if drivers and firmware is after all available. Ethernet according to CNX seemed to be YT8531CA Ethernet seemed to be same as that in OrangePi Zero 3 https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/ WiFi is 'more critical' these days, if it is closed sourced and no firmware, then it is good as just a door stop. Then that thare are other stuff the figure out especially the : - DRAM controller, - and various DRAM timing and configuration aspects - many other low level specific stuff to even have u-boot to boot it up to the linux prompt. - then the other devices e.g. uart etc. - then HDMI - then gpu acceleration (or at least display video, not playing media yet) - then media - and finally NPU, don't seemed documented yet - many more known or unknown unknowns, audio etc

Hi all, I’m trying to get KlipperScreen running directly on the framebuffer on a BigTreeTech CB1 that’s using an Allwinner H616B chip. It’s running Armbian Bookworm (kernel 6.6.66-vendor-sunxi64, Dec 2024 build) on a Manta M8P V2.0 board with a TFT35-SPI display that shows up as fb_st7796s. The goal is to have KlipperScreen render directly to /dev/fb0 without needing a desktop or HDMI. The framebuffer itself seems fine as the screen shows the BigTreeTech logo on boot, and I can write to it manually, so the driver appears to be working correctly. KlipperScreen installs fine, the Python environment and dependencies are all in place, but when I launch it, I always get “Gtk couldn’t be initialized.” If I try running it under Xorg, it throws “xf86OpenConsole: Switching VT failed,” which seems to mean the kernel isn’t allowing virtual terminal switching. I’ve tried both framebuffer and Xorg modes, set SDL_VIDEODRIVER=fbcon and FBDEV=/dev/fb0, and even forced it to use SDL directly, but GTK still won’t start. Everything else works normally, it just refuses to render the GUI. Here’s the kicker: this exact setup worked perfectly on Armbian V2.3.4. KlipperScreen ran out of the box with no special tweaks, so something clearly changed in V3.0 and later builds that broke framebuffer support or GTK initialization. It feels like either framebuffer rendering got dropped, VT switching was removed, or GTK was built without fbdev support. So my main questions are: was framebuffer (fbdev) support intentionally removed from newer Armbian builds for the CB1? Is VT switching disabled by design in the H616 kernel? And is there any known way to run GTK or SDL apps directly on /dev/fb0 under the current Bookworm build? If it’s just a matter of rebuilding GTK or enabling a missing kernel flag, I’m happy to do that I just need to know where the problem actually lies.

Here: https://fi.mirror.armbian.de/oldarchive/helios64/archive/ you can find older images.

I’ve sent the URL and details here, hoping they can take a look