#armbian

okay so i know changelog posts aren't exactly the most exciting thing to read on here but bear with me because this one actually has some genuinely interesting stuff in it

the kernel situation

linux 7.0 is now stable on armbian for rockchip64, sunxi, meson64, raspberry pi 4, spacemit, and uefi edge targets. that's most of the popular hardware covered. and if you want to live dangerously there's now a bleeding-edge branch tracking linux 7.1 rc's on rockchip64 and meson64. go wild.

they fixed the desktop installer and i am so relieved

okay this is the one i'm actually most excited about. if you've ever used armbian-config to install a desktop environment you probably know the pain. uninstall xfce and watch it take half your system with it. browsers that just silently don't work on certain architectures. it was a mess.

26.5 replaces all of that with a clean yaml-based system. every desktop environment — xfce, gnome, kde plasma, mate, cinnamon, i3, xmonad, enlightenment, and more — is now a single declarative file. uninstalls only remove what was actually installed. browsers work everywhere. kde plasma and mate are new additions. xfce, mate, i3 and others now work on armhf and risc-v 64-bit too which is cool.

honestly this fix alone makes the upgrade worth it if you've been burned before

the nanopi m5 thing is actually really cool

so the friendlyelec nanopi m5 is now the first rk3576 board that can boot entirely from ufs storage using a mainline u-boot with zero proprietary blobs in the chain.

ufs is the storage tech that replaced emmc in smartphones — faster random i/o, better write endurance, lower latency under load. for anyone running the m5 in something like a kiosk or an industrial setup this is genuinely useful. getting it to work apparently required wiring up phy initialization, regulator rails, device tree overlays and a proper flashing path. the armbian team made it look easy. it was not easy.

other stuff worth knowing

u-boot 2026.04 lands for a bunch of rockchip boards (rock 5, nanopc-t6, odroid-n2, helios4/64 and more)

ubuntu 26.04 lts "resolute raccoon" is now the default image base

intel ax210 wireless support is finally in out of the box

over a dozen new boards added

panthor gpu firmware expanded to cover more mali variants

the build pipeline got smarter with shellcheck feedback, board-config validation, and multi-arch unit tests

should you upgrade

yeah probably. especially if you use the desktop installer or you've been waiting on linux 7.0 for your board. images are on armbian.com and the full changelog is on github if you want to go deep on the details. https://techrefreshing.com/how-armbian-26-5-improves-upon-previous-releases/

okay that's it. go flash some boards 🚀

La computación basada en ARM continúa su imparable ascenso, impulsando desde sistemas embebidos hasta centros de datos. En este escenario dinámico, Armbian se ha consolidado como una piedra angular para desarrolladores y entusiastas, proporcionando una base sólida, optimizada y versátil para una amplia gama de dispositivos. Hoy, el equipo de Armbian marca un hito significativo con el lanzamiento…

For an amateur radio operator, having a real-time dashboard is essential for monitoring band conditions and identifying DX opportunities. While several solutions exist, I recently completed a project centered on OpenHamClock, an open-source, web-based successor to Elwood Downey’s (WB0OEW) original HamClock. My goal was to move beyond simply opening a browser tab and instead create a dedicated, always-on kiosk for my workshop/shack. This setup allows me to monitor live DX cluster spots, PSKReporter reception, and satellite X-ray flux in real-time, helping me decide exactly when to jump into a radio session.

The heart of this project is a two-component system: a centralized server and a remote kiosk unit. For the server, I utilized a PC equipped with an AMD Ryzen 7 series CPU and 32GB of RAM. While this machine hosts multiple other services, it serves as the perfect, reliable host for the OpenHamClock backend.

The installation process is straightforward, following the official repository guidelines to get the software running on Node.js. To tailor the dashboard to my specific needs, I configured a .env file in the root directory with my preferred settings. Once I verified the deployment was accessible via the default port 3000, I transitioned the application into a formal system service to ensure it runs continuously and resumes automatically after system restarts.

When creating the custom openhamclock.service script, it is vital to update the Environment, WorkingDirectory, and ExecStart paths to match your specific installation. If you use a Node.js version manager other than NVM (such as fnm or brew), ensure you modify the service file accordingly. Additionally, update the User and Group variables to reflect your Linux credentials. After a quick daemon-reload and enabling the service via systemctl, the backend was up and running without any issues.

With the server established, I turned my attention to the kiosk hardware. I chose the Banana Pi M4 Zero, based on the Allwinner H618 with 2GB of DDR4 RAM - paired with a 10.1-inch display. This SBC provides ample power for a dedicated web interface while maintaining a tiny footprint. Because the kiosk is intended for long-term operation, thermal management and power stability were my primary hardware priorities.

I am running this unit in a workshop environment where ambient temperatures typically stay between 29°C and 31°C. To prevent overheating during extended uptime, I installed a commonly available Banana Pi M4 Zero heatsink kit. After 24 hours of continuous operation, the board temperature stabilized at approximately 38°C, which is a very safe range for this chipset. Powering the unit requires a reliable source to avoid mid-session crashes; I used a 5V 3A power supply unit to drive the board.

The software side of the kiosk required a "set it and forget it" approach. I used Armbian to craft a minimal OS image built on the X Window System using the Openbox window manager and Chromium. This image requires no keyboard or mouse and boots directly into the dashboard. To protect against SD card wear and file system corruption, the OS is designed to launch with a read-only rootfs. While the initial launch takes a moment, subsequent boots are impressively fast, typically reaching the dashboard within 30 to 35 seconds.

Integrating the Banana Pi into the display unit involved some custom fabrication. I designed a mounting unit using a 2mm acrylic sheet to securely attach the SBC to the back of the 10.1-inch display. Using a laser cutter, I precision-cut the sheet and all necessary mounting holes. This mounting panel drawing available in the download pack.

The final touch was optimizing the UI for the hardware. Given the display’s 1024×600 resolution, I configured OpenHamClock to run in "tablet mode", which scales the information perfectly for this screen size. The unit has been running continuously in my workshop for a few weeks now, allowing me to monitor the ionosphere, HF band traffic, and track SOTA/POTA activators in real-time.