All Activity

According to https://github.com/redrathnure/armbian-mkspi?tab=readme-ov-file#technical-details the mks-skipr is just an mks-pi with an additional mks-robin-nano attached via uart. That should be the reason, why there aren't separate mks-skipr images, only images for mks-pi. Btw, the images for mks-pi and mks-klipad50 both use the same kernel. After replacing the corresponding .dtb file with the one from your original image, these images should behave identical. Your approach of dd'ing the image from a usb-drive directly to the system that is currently running, sounds as dangerous as replacing a car engine while it's running. You said, that you've successfully used rkdeveloptool for a recovery. If that means, that you have flashed a *full* image to the emmc this way, then I would use this approach to directly flash the desired armbian image to that emmc (without using any other usb drive). Or try to intercept u-boot from the original image to boot from an usb-drive (as I wrote here). Then you could 'dd' an image stored on that usb-drive to the emmc - but neither the source or the destination filesystem should be mounted/in use during that process.

I bricked my original H96MAX TV box while tinkering with it, so I bought a new one. The new unit works fine with both wireless and wired networks on Android, but after flashing the firmware Armbian_26.2.0-trunk.302_H96-tvbox-3566_forky_current_6.18.6_minimal.img, the wired network stops working and only the wireless network is functional. Please help me fix this issue, thank you!

Try this. It worked on radxa-e54c with Cinnamon. rm -rf ~/.local/share/cinnamon && sudo reboot

@Nick A Since both the A7a and A7z have the same CPU family, I made a build using the exact same options, but selecting the A7a instead in the compile menu. This build did start to boot, I saw the Radxa logo, then some Linux console boot messages (but it was scrambled on the screen a bit), and lastly I saw the Armbian logo and the spinning circle. Eventually that all went away and the screen was just empty. No response from key presses, etc., but my HDMI screen was still getting signal, it was just blank.

@Bones558 I don't have a a7z to test with right now. I should be getting one soon and I'll look into it. I'm pretty sure a USB to UART serial device works.

I'm having an issue getting my A7z to boot using your Armbian build tree. I created an image using Nobel and kernel 6. Wrote it to the SD card using Armbian imager. The status light on my A7z always stays solid-on. Any ideas? Armbian-unofficial_26.02.0-trunk_Radxa-cubie-a7z_noble_vendor_6.6.98.img.xz

Mhhh..... Image for OrangePi 3b works out of the box (and it's also possible to install to the eMMC), but it doesn't seem to support some features (i.e. there are no devices like "/dev/video*", "/dev/rknpu", etc.). Otherwise the images for BananaPI CM4 doesn't seem even to boot on OrangePI CM4: comparing both images, those are indeed different (i.e. "initrd.img", "vmlinuz", etc. are under "/boot" folder rather than in "/"). Dies anyone knows a simple way to burn BananaPI CM4 images (or another image) to OrangePI CM4 (to SD Card or better to eMMC)? Regards,

Hi, I'm new to the forums and am looking into replacing OEM Klipper firmware on a Sovol SV06 Ace, The main board looks very similar to the MKS Skipr with the following notable differences: rk3308 B emmc soldered on No SD card. Wifi/Bluetooth added - Original boards used realtek and the latest version uses Broadcom. OEM wifi is hit or miss on connecting and hopefull will be improved with Trixie based Armbian. Sovol has mostly complied with the GPL and source/configuration files are on github. IIRC the kernel version was 5.1x I'm a long time Linux user (Slackware 8.1), have contributed OpenWRT builds and have built custom Linux kernels. I think I've mapped out the install: flash the appropriate ambian image to a formated USB2.0 drive - Ideally with wifi ssid/wpa key ssh sovol@ip login sovol/sovol. su, suspect the root passwd will be makerbase. plug in usb, id drive in dmesg and mount dd if /dev/usb* of=/devmmcblk* Unmount drive and hopefully boot and access over wifi ssh. Install/configure Kipper/Mainsail... I have a recovery path that I have tested using rkdeveloptool/upgrade_tool and the original Sovol firmware. I've perused the armbian github pages looking the MKS Skipr build but have not found it yet. I'm willing to build a tailored (stripped if worthwhile) kernel. I'd appreciate any comments about broadcom wifi access and if newer kernels and newer wpa supplicant builds improve access enough to make it worthwhile. Comments on the overall plan. Pointers

If you mean the built-in script as described in the instructions linked to from the download page (https://www.armbian.com/amlogic-s9xx-tv-box) Then yes that should do everything you need.

Hi, is there any way to install Armbian on the built-in emmc memory on an mxq 4k pro with an s905w processor? Should I follow these guides? https://7ji.github.io/embedded/2022/11/08/alarm-install.html https://7ji.github.io/embedded/2022/11/11/ept-with-ampart.html Or is the built-in script in the system sufficient and will do everything without damaging anything? I would be grateful for any tips

@SteeMan - there is no pressure to do it quickly or at all ... if you should look at it and have questions, just ask me here (i'm reading here regularly, but sometimes with a few days delay) or create an issue in my github repo. i'm always happy to see that you are keeping the amlogic boxes stuff alive pretty well in armbian.

I always appreciate the work you do. I'll try to experiment with what you have done. It sounds very interesting, but I probably won't have time until next month though to look at it.

you might try to write (after gunzip) this u-boot boot-amlogic_gxl_a95x-r2-atf-aarch64.dd.gz from https://github.com/hexdump0815/u-boot-misc/releases/tag/250629-01 which i built some time ago via "dd if=boot-amlogic_gxl_a95x-r2-atf-aarch64.dd of=/dev/your-sd-card bs=512 seek=1 skip=1" to the sd-card to which you wrote the armbian image before and see if it boots (never tested it with armbian) - build instructions for that u-boot are here: https://github.com/hexdump0815/u-boot-misc/blob/wip-v2025-04/readme.gxl ... alternatively you might try to boot this (non armbian) image to see if that u-boot works at all on your device: https://github.com/velvet-os/imagebuilder-testimages/releases/download/autumn-release-2025-testimages/aarch64_mbr_uefi-aarch64-trixie-251016.img.gz (please keep in mind that anything around that image is not related to armbian and thus should not be discussed here as i do not want to hijack this armbian thread) @SteeMan - in case you are interested in getting some of this into armbian, maybe have a look at it and i can try to answer potential questions around it - this was just some experiment to boot amlogic via the u-boot uefi implementation and grub which worked out quite well - as a result an amlogic tv box feels a bit like a pc with a normal grub boot on the screen ... should be possible to make that work for many of the supported amlogic socs - i simply do not have the time to look further into this right now ...

Can't you run on sdcard? It is heavily suggested to run on sdcard before installing on emmc. However the overlay is emmc-pins

@Робертс My screen is constantly white. Here's my wiring diagram. Display-Orangepi zero 3 VCC-5v GND-GND CS-PH9(spi1) RST-PC14 D/C-PC7 SDI-PH7(mosi) SCK-PH4 BL-3.3v SDO-PH8(miso) Also, there might be a typo. The specified dc-gpio in your dts is described as PHC7. I don't quite understand, is it PC7 or PH7?

Unfortunately, nothing's working for me yet(. It didn't work with dts, and my Python tests have only resulted in a gray screen and nothing else. I'm still using deepseek, as I don't understand it myself. Maybe I should connect the display's MISO? Although the display only seems to receive data, not transmit it.

Yes. Probably this week.

Is your LCD at least turning white on powerup? Did you connect the "LED" pin in the LCD, to 3.3V? Send a drawing of how you are connecting the LCD to the orange pi zero 3.

You can switch to beta to get faster updates, though they're untested autobuilds, so if something breaks, you have to unbrick yourself.

The Evolution of SBCs: From Hobby Boards to Edge ComputingOver the past two decades, single-board computers (SBCs) have transformed from experimental maker tools into the backbone of modern embedded and edge systems. What started as a handful of affordable hobby boards has grown into a diverse ecosystem powering automation, AI, and connected infrastructure around the world. From Prototypes to PossibilityEarly SBCs were humble experiments — small circuit boards combining processor, memory, and I/O on one platform. For years they lived quietly inside industrial machines and educational kits. The real turning point came in the early 2010s with boards like the Raspberry Pi, BeagleBone, and Cubieboard, which brought Linux to the maker community at a scale and price that anyone could access. These boards opened the floodgates for innovation. Suddenly, home labs, classrooms, and startups could prototype full Linux systems for the cost of a dinner. The appeal wasn’t just price — it was openness, GPIO access, and a thriving community that treated hardware as something to explore, not just consume. The Rise of a Global EcosystemAs demand grew, more vendors entered the field: Orange Pi, FriendlyElec, Radxa, and dozens of others expanded on the idea, each offering faster SoCs, more memory, and better I/O. Modern SBCs can now host NVMe storage, multiple displays, gigabit networking, and dedicated NPUs for AI workloads — features once reserved for full desktops or servers. They power digital signage, smart gateways, home servers, and even small AI clusters. Developers began caring not just about hardware specs, but also kernel stability, upstream drivers, and long-term support — exactly where Armbian excels. What’s NextLooking ahead, the direction is clear: AI acceleration everywhere – NPUs and neural engines are becoming standard on SBCs.Unified software stacks – Containers, orchestration tools, and reproducible builds are reaching the edge.Energy-aware computing – Solar and battery-powered deployments highlight the need for lean, resilient systems.Armbian’s role in this landscape is to provide the stable software foundation that ties it all together — open, optimized, and reliable across dozens of architectures. In SummarySBCs have grown up. They are no longer just learning tools or proof-of-concept boards — they are the quiet engines running modern infrastructure at the edge. Armbian sits at the heart of that transformation, helping these devices boot faster, run cleaner, and stay useful long after their first flash. The evolution of the SBC mirrors the story of open computing itself: innovation born from community effort, refined through shared knowledge, and extended by software that stays light enough to go anywhere. View the full article

Hi there, I'm really happy with Armbian on my Oprange Pi 5 Plus but recently I noticed that I'm not getting kernel updates so often as before. I use rockchip-edge branch and I'm stuck at kernel "6.18.0-rc6-edge-rockchip64". I know there are new versions being tested (https://github.com/armbian/os/pkgs/container/os%2Fkernel-rockchip64-edge), will they be released to armbian? Maybe you are working hard on Armbian version 26.2 and I'm just anxious Thanks in advance!

@robertoj Hello. I was able to get some DuPont wires and test them directly without soldering. The result was zero. I tried using ChatGPT to get it working.He suggests that my display isn't initializing. In some cases, it's either that the reset isn't working, or that the frequency is too high for a Chinese display. I tried using fbtft, but the result was zero. I followed your configuration and pinout. Are there any steps I might have missed?

@robertoj Could you post a step-by-step guide on setting up the Chinese ili9488 screen on a red board and OrangePi Zero 3? I think this forum will receive many thanks for your work.

Thanks, but I cannot run rk322x-config (or can I without being fully booted?). I suppose I can try in overlays=... line in /boot/armbianEnv.txt, but what should I write here?

hello @digital, in some rare cases there are some minor trickeries to try and improve compatibility with eMMC. If you run rk322x-config, there is a panel dedicated to eMMC which allows you to select some compatiblity options, like emmc-pins and DDR/UHS modes. You may try first enabling emmc-pins and rebooting to see if it gets recognized. Anyway photos of the board and the original stock device tree could be useful to identify the compatibility problem.