All Activity

for NPU if you can't run it on armbian using the rockchip vendor kernel, you can use the Joshua: https://github.com/hqnicolas/ubuntu-rockchip-joshua/tree/h96-max-v56-board-add

Hi, I would like to report an issue I encountered while testing the new NanoPi M5 UFS boot support in Armbian 26.5.1. Board: NanoPi M5 Boot media for installation: SD card Target storage: onboard UFS BOOT switch after installation: UFS/SD Tested images: * `Armbian_26.5.1_Nanopi-m5_trixie_vendor_6.1.115_minimal.img.xz` * `Armbian_26.5.1_Nanopi-m5_trixie_current_6.18.33_minimal.img.xz` My current NVMe setup uses a custom layout: * `ext4` `/boot` * `btrfs` `/` I had to use this layout because, in my previous NVMe tests, installing the system directly to NVMe with btrfs using `armbian-install` did not boot when `/boot` was also located on btrfs. With a separate ext4 `/boot` partition and a btrfs root filesystem, the NVMe setup works correctly. When testing the new UFS installation path, I noticed that the UFS option in `armbian-install` seems to only install the whole system to `/dev/sda1` on the UFS General LUN. Unlike the NVMe installation path, I could not find a way to select an existing target partition or use a manually prepared partition layout. I tried the following UFS layout manually: * `/dev/sda1` as `ext4` for `/boot` * `/dev/sda2` as `btrfs` for `/` However, after splitting the UFS General LUN this way, the system did not boot at all. I also tested the default UFS installation path without manually changing the partition layout. I booted from SD card, ran `armbian-install`, selected the UFS install option, and selected btrfs as the filesystem. With both tested images listed above, the installation process completed, but after removing the SD card and booting from UFS with the BOOT switch set to UFS/SD, the system did not boot. So the behavior I observed is: * UFS installation creates and uses only `/dev/sda1` as the system partition. * UFS installation with btrfs selected completes, but the installed system does not boot afterward. * A manual layout with separate `ext4 /boot` and `btrfs /` on UFS also does not boot. * The UFS install path does not seem to provide the same manual partition selection behavior as the NVMe install path. My questions are: 1. Is btrfs on UFS expected to be bootable at this stage? 2. Or should ext4 currently be considered the only supported/recommended filesystem for UFS boot on NanoPi M5?

Thank you @Revellion I just did ``` sudo apt-mark unhold armbian-firmware sudo rm -rf /lib/firmware/qcom/sm8550/ayn/ sudo apt update && sudo apt upgrade ``` and it worked fine

Welcome to the latest Armbian Newsletter: your source for the latest developments, community highlights, and behind-the-scenes updates from the world of open-source ARM and RISC-V computing. Armbian v26.5.1 delivers another strong round of improvements across the project, focusing on expanded hardware support, desktop and userland refinements, build framework modernization, and infrastructure enhancements. This release introduces new board images and platform updates, improves Ubuntu 26.04 "Resolute" integration, refines Bianbu desktop support, adds firmware and driver updates including AX210 wireless support, and continues ongoing work to strengthen the build system, CI pipelines, and developer tooling. Numerous kernel, bootloader, and device tree updates further improve stability, compatibility, and performance across a wide range of ARM and x86 platforms, reinforcing Armbian's commitment to providing a reliable and flexible Linux distribution for single-board computers, embedded devices, and edge computing deployments. SPONSORED Join us in making open source better! Every donation helps Armbian improve security, performance, and reliability — so everyone can enjoy a solid foundation for their devices. Release Armbian Quarterly digest · armbian/buildThis quarter’s work centers on three priorities: kernel modernization across SoC families, a redesigned desktop subsystem driven by armbian-config, and substantial expansion of board and platform c…GitHubarmbianNative UFS boot lands on the NanoPi M5Armbian’s next release boots the FriendlyElec NanoPi M5 end-to-end from UFS on a mainline U-Boot, with no proprietary recovery image in the loop. It is the first RK3576 board in the catalogue to reach this state, and the integration pattern paves the way for the others. UFS, the storage classArmbian blogDaniele BriguglioWe rewrote how Armbian installs desktops. Here’s what changedA friendlier, faster, snap-free desktop install in armbian-config If you’ve installed a desktop environment with armbian-config over the last few months, you may have noticed things feel different: there’s a tier you can pick, the browser actually works on every arch, uninstall doesn’t take half your system with it, andArmbian blogIgor PecovnikView the full article

Welcome to the latest Armbian Newsletter: your source for the latest developments, community highlights, and behind-the-scenes updates from the world of open-source ARM and RISC-V computing. Armbian v26.5.1 delivers another strong round of improvements across the project, focusing on expanded hardware support, desktop and userland refinements, build framework modernization, and infrastructure enhancements. This release introduces new board images and platform updates, improves Ubuntu 26.04 "Resolute" integration, refines Bianbu desktop support, adds firmware and driver updates including AX210 wireless support, and continues ongoing work to strengthen the build system, CI pipelines, and developer tooling. Numerous kernel, bootloader, and device tree updates further improve stability, compatibility, and performance across a wide range of ARM and x86 platforms, reinforcing Armbian's commitment to providing a reliable and flexible Linux distribution for single-board computers, embedded devices, and edge computing deployments. SPONSORED Join us in making open source better! Every donation helps Armbian improve security, performance, and reliability — so everyone can enjoy a solid foundation for their devices. Release Armbian Quarterly digest · armbian/buildThis quarter’s work centers on three priorities: kernel modernization across SoC families, a redesigned desktop subsystem driven by armbian-config, and substantial expansion of board and platform c…GitHubarmbianNative UFS boot lands on the NanoPi M5Armbian’s next release boots the FriendlyElec NanoPi M5 end-to-end from UFS on a mainline U-Boot, with no proprietary recovery image in the loop. It is the first RK3576 board in the catalogue to reach this state, and the integration pattern paves the way for the others. UFS, the storage classArmbian blogDaniele BriguglioWe rewrote how Armbian installs desktops. Here’s what changedA friendlier, faster, snap-free desktop install in armbian-config If you’ve installed a desktop environment with armbian-config over the last few months, you may have noticed things feel different: there’s a tier you can pick, the browser actually works on every arch, uninstall doesn’t take half your system with it, andArmbian blogIgor PecovnikView the full article

Finally this board works. But it doesn't boot from eMMC onboard when flashing it. I used both dd on the Armbian image (Trixie), or the armbian-config and official download and flash image into eMMC. The error is: U-Boot SPL 2024.10_armbian-2024.10-Sf919-P0490-Hc6a9-V4f26-Bd0d2-R448a (May 11 2026 - 06:14:06 +0000) DRAM: 4096 MiB Trying to boot from MMC2 MMC Device 1 not found spl: could not find mmc device 1. error: -19 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### It seems into the SPL bin file there's no eMMC activation code.

@Marvin-03 You're probably right—it may be worth checking the FPC connection. A timeout usually only occurs when the PCIe/NVMe board is not being detected. I'm currently using an early MCUZone NVMe 2230 HAT. I recently ordered a new Waveshare AIO HAT as well, so once it arrives I'll be able to do some additional testing.

its not 905 its 805x android 7 i am working on same board contact me i can help

@alexc What pcie hat do you use? I use one from Yahboom made for the RPI 5, but my nvme wont show up and since logs show "sunxi:pcie-rc-6000000.pcie:[ERR]: Speed change timeout" it seems like the hat doesnt work. On the Cubie A5E I only get this timeout if the SSD isnt plugged in.

My ROCK5B was ordered as a 'blue one' on Aliexpress a year ago; I got a 'green one' and as with included case the price was > 150 euro, it got stuck at customs for quite some time. It was with blank/empty SPI flash and endless boot-loop. That was already known by me, so I had fixed 12V soldered to a male USB-C connector. Same story for ROCK3A, although that one booted most of the time but then while running al sorts of strange errors and or crashes. So I think you have to assume USB-C PD negotiation is not working with the Armbian images you tested. Only the U-Boot starting at sector 64 does matter, rest (Linux) is don't care. If a stable U-Boot or UEFIv1.1 form SPI-flash or SD-card, you have already a very extensive commandline interface or text menu's in the EDK2. But lock up might simply happen because the PSU does not do 65W, instead max 15 W (only up to 3A) and the 5V might drop way too low, just very short dip that is not measurable without good oscilloscope or so. The Radxa image might have a bootloader variant that does do USB-C PD, although I haven't seen proof anywhere that it correctly handles and does operate the FUSB302, but that might simply be because my ROCK3A and ROCK5B came out of the box with empty SPI and for ROCK5B I have ignored Radxa images anyway after the big troubles with ROCK3A, so do not really know what happens with those. So I have no other advice then use fixed higher voltage, formally it is >= 9V according to Radxa wiki/docs AFAIR, but I remember the powertree design actually better than those quick facts and my conclusion was : forget about 5V, use 12V and it was easy decision for me as I use 12V UPS and 3.5inch HDD that also needs 12V anyway.

Armbian 26.2.1 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - 26.2.0~git2605212123.7b286abe336 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.3 42ae8b818 (https://ryanfortner.github.io/box64-debs/) + wine-proton-11.0-beta1-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-11.0-beta1/wine-proton-11.0-beta1-amd64-wow64.tar.xz) + DXVK-stripped v2.7.1 ~40fps@720p Grand Theft Auto IV - The Complete Edition

Armbian 26.2.1 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - 26.2.0~git2605212123.7b286abe336 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.3 42ae8b818 (https://ryanfortner.github.io/box64-debs/) + wine-proton-11.0-beta1-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-11.0-beta1/wine-proton-11.0-beta1-amd64-wow64.tar.xz) + DXVK-stripped v1.7.3 30~60fps@1536x864 Batman: Arkham City GOTY Edition

Yes, the next step should be u-boot normally. @meco any clue?

Armbian 26.2.1 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - 26.2.0~git2605212123.7b286abe336 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.3 42ae8b818 (https://ryanfortner.github.io/box64-debs/) + wine-proton-11.0-beta1-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-11.0-beta1/wine-proton-11.0-beta1-amd64-wow64.tar.xz) + DXVK-stripped v2.7.1 40~60fps@1536x864 Far Cry 2 GamerProfile.xml

Armbian 26.2.1 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - 26.2.0~git2605212123.7b286abe336 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.3 42ae8b818 (https://ryanfortner.github.io/box64-debs/) + wine-proton-11.0-beta1-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-11.0-beta1/wine-proton-11.0-beta1-amd64-wow64.tar.xz) + DXVK-stripped v1.7.3 40~60fps@1536x864 Resident Evil 4 Ultimate HD

@sr4armbian Try X98H.

Hi, I can't find an image for my TV box and I was wondering if anyone has one that I could use on the device. Thanks for your help

So I cloned the repo, did a git revert on the commit you mentioned then ran `./compile.sh BOARD=rock-5b RELEASE=noble BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no`, flashed the image in the output folder and I'm getting but I'm still getting the same output ``` INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x1 INFO: code: 0x88 INFO: ext 32k is not valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 ``` I wonder if we are getting to the next step (U-boot, right?) and just not getting any logs

Ok I will try that. The `Armbian_26.2.1_Rock-5b_noble_vendor_6.1.115_gnome_desktop.img` image is from February so this commit shouldn't be there but I will try without this commit anyway. I also try the Ubuntu rolling release from May 24 that should include this commit but the behavior is the same

Hm. Pure guess: https://github.com/armbian/build/commit/1bac6d977217039cae7193a1d6c19ae5b50c2c5f Try to build and boot an image with this reverted

It just stops after that. No Linux UART logs, nothing via HDMI. I'm flashing this image: Armbian_26.2.1_Rock-5b_noble_vendor_6.1.115_gnome_desktop.img

Does it simply stop after that line or is the output incomplete?

Hi. I did a wipe of the SPI flahs using the method found in this guide https://docs.radxa.com/en/rock5/rock5b/low-level-dev/install-os/rkdevtool_spi#erase-spi-flash While I can see that the TF-A version is newer I still hand int the same fashion: ``` DDR b8ce94f14b cym 25/09/26-15:48.05,fwver: v1.20 ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 ch0 ttot18 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS=1 Die BW=16 Size=2048MB ch1 ttot18 channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS=1 Die BW=16 Size=2048MB ch2 ttot16 channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS=1 Die BW=16 Size=2048MB ch3 ttot18 channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS=1 Die BW=16 Size=2048MB Manufacturer ID:0xff DQS rds:l0,h1 CH0 RX Vref:27.5%, TX Vref:21.8%,0.0% DQ rds:l0 h1 h1 h1 h4 h1 h3 h1, h1 h6 h4 h3 h4 h4 h7 h2 DQS rds:l0,h3 CH1 RX Vref:27.5%, TX Vref:20.8%,0.0% DQ rds:h1 h6 h1 h3 h3 h4 h3 h4, h5 h1 h4 h6 h5 h7 h1 h2 DQS rds:h1,h1 CH2 RX Vref:28.5%, TX Vref:20.8%,0.0% DQ rds:l0 h4 h2 l0 h6 h5 h4 h2, h3 h3 h2 h4 h5 h5 h7 h6 DQS rds:h1,h1 CH3 RX Vref:28.9%, TX Vref:21.8%,0.0% DQ rds:h2 h7 h7 h2 h6 h2 h7 h1, h5 l0 h5 l0 h1 h5 h1 h1 stride=0x2, ddr_config=0x0 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x0 change to F1: 528MHz ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 change to F2: 1068MHz ch0 ttot14 ch1 ttot12 ch2 ttot12 ch3 ttot14 change to F3: 1560MHz ch0 ttot16 ch1 ttot16 ch2 ttot14 ch3 ttot16 change to F0: 2112MHz ch0 ttot18 ch1 ttot18 ch2 ttot18 ch3 ttot18 out INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-942-g98eaeb2f3:derrick.huang, fwver: v1.53 NOTICE: BL31: Built : 12:10:56, Aug 25 2025 INFO: spec: 0x1 INFO: code: 0x88 INFO: customer demand: 0x0 INFO: ext 32k is not valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 ```

@Marvin-03 It is past the bootloader. I only tested the build on XFCE, which boots fine. GNOME failing to boot properly might be due to the PowerVR or KMScon install script. If you need GNOME. Try removing the function post_family_tweaks__install_powervr_desktop(). https://github.com/NickAlilovic/build/blob/Radxa-mainline-WIP-test/config/sources/families/sun60iw2.conf#L467-L1045 Update: I removed both post_family_tweaks__install_powervr_desktop() and kmscon install funtions. Gnome works. But you need to use a serial device to fill in the first login information.

@Marvin-03 Just to confirm: for both boards, with and without eMMC, are you using the same microSD card as the boot device? From the current boot log, it looks like there may be an issue with the microSD card. Both the previous boot log (using the BSP MMC driver) and the current boot log (using the mainline MMC driver) show problems detecting mmc0 (the microSD card). Could you try a different microSD card, preferably from another brand, and see if the issue persists?