All Activity

This week's work centers on board support expansion, kernel and U-Boot maintenance, and desktop and CI tooling refinements. On the platform side, the Radxa Cubie A5E received Wi-Fi enablement and a kernel refresh as part of a broader update, while the youyeetoo YY3588 was promoted from CSC to standard support and the YY3568 gained PCIe NVMe functionality. The NanoPi R76S and Rock 5 ITX were both migrated to mainline U-Boot v2026.04, dropping vendor-branch gates, and the Vanxoak HD-RK3506-EVB was added with vendor and board imagery. Kernel hygiene dominated the maintenance work: duplicate OPP labels on the Xiaoxin Pad Pro (sm8250) were corrected, broken UHS-I, xo-clock, SD, and DSI patches were removed from sm8550 trees for both 6.18 and 7.0, and a now-upstream r-spi backport was dropped from sunxi-6.18. The odroidxu4-current branch advanced to 6.6.141 across two successive bumps. Desktop and infrastructure tooling saw layered improvements through configng: alsa-ucm-conf and libcamera/v4l userspace were added to the minimal tier, PackageKit and AppStream landed at the mid tier, and DE postinst scripts now execute in the build chroot to resolve missing wallpaper. UEFI x86 and arm64 desktop spins were switched to GNOME on the edge kernel, and build infrastructure gained inline ShellCheck PR feedback, scoped token permissions, fork-aware artifact gating, and event-driven runner cleanup via systemd hooks. #Armbian #EmbeddedLinux #Rockchip #UBoot #KernelDevelopment ChangesAdd vendor and board image of Vanxoak HD-RK3506-EVB. by @SeeleVolleri in armbian/armbian.github.io#316Add wifi to Radxa Cubie A5E (kernel7.0). by @juanesf in armbian/build#9879ci: post ShellCheck findings and auto-fix suggestions inline on PRs. by @iav in armbian/build#9868ci: scope GITHUB_TOKEN writes to job-level in maintenance-lint-scripts-post. by @iav in armbian/build#9887ci: skip build-artifacts gating job on forks. by @iav in armbian/build#9865desktops: install alsa-ucm-conf at minimal tier. by @igorpecovnik in armbian/configng#923desktops: install libcamera/v4l userspace at minimal tier. by @igorpecovnik in armbian/configng#924desktops: run DE postinst scripts in build chroot (fix missing wallpaper). by @igorpecovnik in armbian/configng#927enh: substring filter for the board picker. by @iav in armbian/build#9843expose: switch uefi-x86 / uefi-arm64 to GNOME desktop on edge kernel. by @igorpecovnik in armbian/armbian.github.io#315feat(ccache-remote): parse password from DNS-SD TXT for redis backend. by @iav in armbian/build#9864feat(tools/shellfmt): accept positional file args for scoped format. by @iav in armbian/build#9863fix(runners): handle missing HOME in systemd hooks for runner-clean-pages. by @igorpecovnik in armbian/configng#928fix(sm8250): drop duplicate cpu7_opp21 label on Xiaoxin Pad Pro overclock OPP. by @igorpecovnik in armbian/build#9882fix(sm8550-6.18): drop broken sm8x50 UHS-I/xo-clock mbox patch. by @igorpecovnik in armbian/build#9884fix(sm8550-7.0): drop merged & broken SD/DSI patches. by @igorpecovnik in armbian/build#9885fix(sunxi-6.18): drop r-spi backport now merged in linux-6.18.y stable. by @igorpecovnik in armbian/build#9883gha: don't double-quote board/maintainer filter values. by @iav in armbian/os#462gnome: add packagekit + plugins + appstream at mid tier. by @igorpecovnik in armbian/configng#922module_cockpit: drop qemu-kvm (no riscv64 build; qemu-system covers it). by @igorpecovnik in armbian/configng#926nanopi-r76s: bump mainline u-boot to v2026.04 and drop vendor-branch gates. by @SuperKali in armbian/build#9869release-targets: flip UEFI desktop spins from current to edge. by @igorpecovnik in armbian/armbian.github.io#314rock-5-itx: link upstream kernel commit in pcie3 refclk u-boot patch. by @SuperKali in armbian/build#9861rock-5-itx: switch to mainline u-boot v2026.04. by @SuperKali in armbian/build#9848Rockchip: youyeetoo yy3568: enable pci-e NVMe ssd. by @hqnicolas in armbian/build#9877runner-cleanup: event-driven _diag/pages wipe via systemd hooks. by @igorpecovnik in armbian/configng#925Update for Radxa Cubie A5E. by @juanesf in armbian/build#9626Update odroidxu4-current to 6.6.140. by @belegdol in armbian/build#9867Update odroidxu4-current to 6.6.141. by @belegdol in armbian/build#9881Update radxa-cubie-a5e.csc with current kernel for build. by @juanesf in armbian/build#9874youyeetoo-yy3588: promote from CSC to standard support. by @SuperKali in armbian/build#9873View the full article

@Rodrigo Campos In my case the U-Boot side is not just a generic version choice. That baseline carries the board-specific path I tested: the zero2w-based defconfig, mmc0 broken-CD handling, H616 EMAC1/RMII support, I2C3 enablement, the LAN preinit step, and the extra EMAC-related clock/register writes. Since the kernel LAN attach depends on the board already being prepared by U-Boot, I preferred to keep the bootloader side conservative. So the short answer is: it is pinned because it is the validated baseline, not because I know of a hard conflict with every newer release.

https://github.com/armbian/configng/releases

@rosic download it using the torrent i attachment (included checksum as well). To flash use the instruction provided on github. Armbian-Unofficial-LinknLink-iSG-Box-SE-v0.1.torrent SHA256SUMS.txt

I have the same problem running a board with v26.2.1 for Rock 5B Plus running Armbian Linux 6.1.115-vendor-rk35xx Packages: Debian stable (trixie) that there is no install candidate named 'armbian-config'. I have two different systems running Armbian, one with "Debian (stable) Trixie" (which has the problem) and one with "Ubuntu stable (noble)" (same Kernel 6.1.115-vendor-rk35xx, same v26.2.1 dist) which has NO problem getting Armbian-Config package updated. After copying the apt-source from one to the other (Ubuntu -> Debian), it works fine. Was that intended? Here the code of the copied file '/etc/apt/sources.list.d/armbian.sources': Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg Looks like it works fine now ... Could you please confirm if I am doing okay with this? Thx in advance

https://github.com/armbian/build/pull/9901

I think that the comment by @werner was mostly intended to set your expectations. Based on what you have said, you have a board that Armbian doesn't support at all. Second, you have found a similar board (Bpi M2 Ultra) that exists within Armbian. But that board is a csc board (Community Support). Which means it also isnt' supported by Armbian. But some developer in the community has as some point in the past contributed some work on it. Likely that developer no longer is around and that board doesn't get any meaningful maintenance. So you are doing the proper thing in using these forums to post your observation and question. But unless either you or some other volunteer in the community wants to work on this, it is unlikely to ever get much if any attention. That is the reality of a SBC world where the manufacturers don't support the software on their boards and the volunteers at Armbian can only work to support a few boards directly while providing the tools and framework for other community volunteers to add in partial support for some other boards.

Thank you

https://github.com/armbian/build/tree/main/config/boards BOARD equals filename (without file extension) from above

Hello Thanks for you answer, I understand the point that if even though M2B & M2U are very close, it does not mean it will work. I really thought it was a simple thing to change "just" to turn off/on the board, as all the rest is perfect. I had a look to https://docs.armbian.com/Developer-Guide_Build-Preparation/ but honestly I am not skilled enough to to this, I did not understand how building it on my PC will make it work on the BananaPi, and the config ./compile.sh build \ BOARD=uefi-x86 \ #bananapim2b does not seem to exist BRANCH=current \ BUILD_DESKTOP=no \ BUILD_MINIMAL=yes \ KERNEL_CONFIGURE=no \ RELEASE=trixie does not help on which string using for my board. Regards

I know this is an old post, but I am desperate and saw you are using v 1.3.2. I have an Orange Pi 5 v 1.3.2 as well and I can't get it to boot. I have been trying a bunch of different OS's, Ubuntu and Ambian versions and it keeps failing. ChatGPT and Gemini both say it is a bad DBT file and then point me to the same version of Ambian to use. None of it seems to work, have you had any luck getting it to work? I haven't tried compiling the OS yet for it, I was hoping there was a stable version out there I could use.

New upstream BlueZ documentation helps simplify Bluetooth qualification for Linux-based products by mapping supported profiles, test requirements, software versions, and manual steps in one place. View the full article

In the world of cheap ARM sbcs you cannot simply use image for board X and assume it works for board Y. It may up to a certain point, even boot, but you have to live with regressions. https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image If there is no pre-made image for a specific board, then you can DIY if it is even supported by the framework. keep in mind, boards in eos or csc status may or may not work. We don't know, we don't pay attention, we don't support.

Hello, Thanks for armbian on Banana PI, it is really wonderful compared to official releases. I installed the image "Armbian_community_26.2.0-trunk.904_Bananapim2ultra_trixie_current_6.18.29_minimal.img.xz" on my Banana PI M2 Berry (there is no image for this type), and all is working wonderfully well ... except rebooting or shutting down the Banana PI. When typing reboot, all services stop but the screen blocks on systemd-shutdown[1]: Rebooting. and it never reboots. It does the same for shutdown, stuck on same kind of message. Could you help me please ? Regards

Perhaps send fix here: https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.18/board-nanopi-m5-add-wifi-bt-ufs-and-misc.patch

**Board:** NanoPi M5 (RK3576) **Kernel:** 6.18.33-current-rockchip64 (#1 SMP PREEMPT Sat May 23 11:07:21 UTC 2026) **Armbian build:** v26.8.0-trunk.53 ## Problem Gigabit RX is completely non-functional on `end0` (GMAC0, `ethernet@2a220000`). The interface comes up at 1000Mb/s, TX works, but no packets are ever received. DHCP never gets an OFFER, `ethtool -S end0` shows RX counters stuck at zero. Forcing 100Mb/s via `ethtool -s end0 speed 100 duplex full autoneg off` works around the issue — RX starts working immediately. ## Root cause The DTB sets `phy-mode = "rgmii-id"` together with `rx_delay = <0x3f>`. The RTL8211F PHY in `-id` mode already applies its own internal RX delay, and the driver applies an additional hardware delay on top of it. The double delay breaks gigabit RX entirely. ``` # /boot/dtb/rockchip/rk3576-nanopi-m5.dtb — broken phy-mode = "rgmii-id"; tx_delay = <0x21>; rx_delay = <0x3f>; # <-- causes double RX delay ``` ## Fix Change `phy-mode` to `rgmii-rxid` (PHY applies RX delay internally) and remove `rx_delay`. This applies to both GMAC0 (`ethernet@2a220000`) and GMAC1 (`ethernet@2a230000`). ``` # Fixed phy-mode = "rgmii-rxid"; tx_delay = <0x21>; # rx_delay removed ``` After applying this fix gigabit works correctly at 1000Mb/s with full RX functionality. ## Workaround ```bash ethtool -s end0 speed 100 duplex full autoneg off ``` Or patch the DTB manually: ```bash dtc -I dtb -O dts -o /tmp/nanopi.dts /boot/dtb/rockchip/rk3576-nanopi-m5.dtb sed -i 's/phy-mode = "rgmii-id"/phy-mode = "rgmii-rxid"/g' /tmp/nanopi.dts sed -i '/rx_delay/d' /tmp/nanopi.dts dtc -I dts -O dtb -o /boot/dtb/rockchip/rk3576-nanopi-m5.dtb /tmp/nanopi.dts reboot ```

Android DTB itself is broken in many ways, mainly because wifi gpios from DTB do not show up in the gpioinfo output. It is more important to put the brcm4335-sdio firmware in /lib/firmware/brcm, which is missing in the armbian repository. iw phy0 info shows support of the 5GHz channels, but i don't have such access points nearby. I will check tomorrow with my dual-band AP.

It happened a few days ago that I rebuilt my complete firmware package to try something with another device. An HC4 firmware binary also automatically falls out in this process. If you like, you can put it on a microSD card (dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/${entire-device-to-be-used}), place the prepared microSD card in your HC4 and start it with the boot button pressed. Check whether it meets your expectations, and if all tests are successful, you can transfer it to the SPI flash.

Board: Orangepione Testing results for the three available images. Should there be more images available? Armbian_26.5.1_Orangepione_resolute_current_6.18.33_minimal.img Tested working: Boot from SD card with uboot and then to a USB SSD. Reboot Connect via ssh iperf3 after installing iperf3 gpio after installing gpiod HDMI video HDMI audio after installing mpg123 Used usb keyboard/mouse to test HDMI. Note that resolute now uses gpiod for gpio instead of sys. Gpiod had to be installed whereas trixie minimal comes with gpiod installed. Armbian_2Armbian_26.5.1_Orangepione_trixie_current_6.18.33_minimal.img Tested working: Boot from SD card with uboot and then to a USB SSD. Reboot Connect via ssh iperf3 after installing iperf3 gpio HDMI video HDMI audio after installing mpg123 Used usb keyboard/mouse to test HDMI. Armbian_26.5.1_Orangepione_resolute_current_6.18.33_xfce_desktop.img Tested working: Boot from SD card with uboot and then to a USB SSD. Reboot On HDMI connecter screen with usb keyboard/mouse Using terminal emulatori tested perf3 and gpio HDMI audio with vlc media player. Not working: Ran chromium to get to Armbian download page but took over a minute for each page to load and then the system crashed. With only 512MB RAM this system is under powered for general purpose desktop use. ubuntu_resolute_minimal.txt debian_trixie_minimal.txt ubuntu_resolute_xfce.txt

The longer answer is that for standard releases, updates only occur with each release cycle (i.e. every three months in Feb, May, Aug, and Nov each year. So you will get new kernel release on that schedule. Armbian also has rolling release repositories and these put out new versions on a frequent basis. And you should be able to switch between stable releases and rolling release apt repositories using armbian-config. Note that rolling releases don't get any testing (other than automated builds) and therefore may not be suitable for many users needs. But those are your two options.

We're in the middle of the May release, so new packages should eventually hit repo in a few days/weeks.

Hi, I have been running armbian with the minmal debian trixie image on a odroid M1 for a few month now and I noticed that since I installed the image there has not been a single kernel upgrade. the kernel is still at 6.18.10 despite current debian install image for this board being shipped with 6.18.28 so I am assuming I am doing something wrong. The apt update and apt dist-upgrade logs show clearly all current package information are being downloaded from both debian and the armbian mirrors, and both armbian-config updates and upstream debian packages have been upgraded whenever I run the apt dist-upgrade commands, but the kernel is still the same old version from several month ago. Any clue what I should look at to find the issue? Thanks

Board: MKS-Klipad50 Images: * Armbian_26.5.1_Mksklipad50_resolute_current_6.18.33_minimal.img.xz * Armbian_26.5.1_Mksklipad50_trixie_current_6.18.33_minimal.img.xz Passed tests: * gpg and sha checksum files * boot from emmc, leds, display, touch, usb, internal wifi * initial setup, uboot-console, reboot Result: All expected images do exist, verify and work properly. Sidenote: The Klipper ecosystem does not yet run on Ubuntu-Resolute (Python-3.14 incompatibility), but that shouldn't be a stopper for the release.

You can send your DTB, that has wi-fi?

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.