@bickns @Nick_Sl Happy to build a CLI/headless image — there's clearly demand now. A few things: 1) If there are packages you'd want baked in by default (network tools, docker, python, monitoring, whatever suits your use case), drop me a list in the thread and I'll include the sensible ones. Easier to get it right up front than have everyone apt install the same stuff afterwards. 2) Heads-up on one known issue: I'm still finishing off the analog audio (the 3.5mm jack) — work in progress (HDMI audio works fine). So it comes down to what you need: If nobody needs the analog jack → I can get the CLI image to you pretty much straight away, and finish the audio later. If you do need it → I'd rather wait and ship it once the audio fix is done, so you're not left with a half-working board. So just let me know: does your use case need the 3.5mm audio jack or not? 3) And a little cheeky one 😄 — if any of my work has been useful, a quick comment on my Ko-fi would honestly make my day (it's looking pretty lonely over there, zero comments so far! 🙈). A donation isn't necessary at all — a friendly note is more than enough — but if you do feel like buying me a coffee, it's hugely appreciated and helps me keep going (and buy test hardware). ☕ ko-fi.com/aurealnix I'll ping you here when it's ready to test. Cheers!

hi. can you make only cli image? i will test it

Thanks @AurealNix - that's good intel. Only 20 of those patches of the 109 failed - I had a quick look through them and I can see you are looking to prioritise the GPU (all those GOOGLE_ flags to make youtube stream better etc) amongst other things. For my project I only needed to run headless so I could install your image and uninstall KDE if it didn't work out with my current prototype for this outdoor noise cancelling thing (I was attracted to the opi 4a because it had a bit more all round grunt) I figured I'd stick with armbian as it would have a better chance of the PR for changes to dtb etc being accepted into "stable".. I think I might go with your .dts and manually apply the changes to the other files and then build from there - used to have the stomach for this back in the day when I used to hack stuff before the internet, but I really need to get onto the noise cancelling project as my wife complains about the noise of the road when we have a BBQ outdoors and I reckon i could go some way to disturb that with some software. Your retro gaming image sounds top notch! I'm still to Master Halo 4 on the X-Box one given all these other distractions. The board is now in the bottom drawer for now as the DJI Mic Mini 2 just turned up today and the other board recognises it ok and its on to stage 2 of this prototype. Enjoy the football .. Cheers

you fancy a fun distraction rather than a frustrating one: I'm also putting together a retro-gaming image for this SoC (HDMI to the TV + a gamepad = a neat little emulation box, and it's the same chip as some of the new handhelds). Early days, but it's in the works — one more reason to keep the board out of the eBay pile. 🙂

Hi @bickns, thanks a lot for giving it a go! 🙏 The reason dropping them into userpatches/kernel/archive/sunxi-6.18 fails is that these aren't Armbian-style patches — they're a git format-patch series on top of plain vanilla 6.18.38 (base commit 1db74811b), meant to be applied to a clean tree in order. Armbian applies its own sunxi patch set first, so they conflict against that. I didn't use the Armbian build system at all — I built mainline from scratch: Clone/checkout vanilla 6.18.38, then git am /path/to/patches/0*.patch (all 106, in order). Copy opi4a_blindboot_defconfig into arch/arm64/configs/ and make opi4a_blindboot_defconfig. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc) Image dtbs modules Wrap it for the BSP U-Boot (this is the important bit — it only boots a legacy uImage): mkimage -A arm -O linux -T kernel -C none -a 0x41000000 -e 0x41000000 -d arch/arm64/boot/Image uImage Two things to know: A handful of the patches are BSP-U-Boot workarounds (static /memory, display FDT stubs, etc.) — only needed to boot under the proprietary BSP U-Boot. If you're on mainline U-Boot / a normal Armbian boot flow, you'd skip those. The README groups the patches by destination so you can see which is which. If you want to integrate into Armbian proper, the cleaner path is probably the board DTS + defconfig + the generic sunxi fixes as individual patches, rather than the whole display series in one go (that one's a big port of the minimyth2/Suess work and would need adapting to Armbian's tree). Happy to help however's useful — glad it's of interest!