All Activity

You can try, worse case it won't boot. What's the problem with that ? Only general. Switch to nightly repository and then switch to edge kernel: https://docs.armbian.com/User-Guide_Armbian-Config/System/#rolling https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels but if it won't work, you are on your own to find out why it doesn't work. Also some features won't work. We never supported EDGE kernels due to extreme costs associated with such operation.

Thanks @djurny! So the only think I should need to do after/when upgrading is to run nand-sata-install? The rest of it should be handled by the packages in the update? Mine is running off an SD card so in the options that appear I would select "Boot from SD" correct?

Hi @wolf7250, When you upgrade, one of the packages will update the bootscript (/boot/boot.scr), that will prevent a load address conflict - this should be armbian-bsp-cli iirc. The new bootscript will either calculate the load addresses or use new defaults to avoid the image overlap/"corruption" issue. The U-Boot for the helios4 has been updated as well to enable load address calculation, instead of using hardcoded values. To update U-Boot, run nand-sata-install and select to "install/update the bootloader on SD/MMC" (see here). Groetjes,

This is part of https://github.com/armbian/build/pull/8777/files And there are no changes at our end. So I assume the issue was introduced in mainline?

moved to staging

I am attempting to update my Helios4 running OpenMediaVault and am experiencing the same error that many have posted about above Boot script loaded from mmc 207 bytes read in 156 ms (1000 Bytes/s) 28834 bytes read in 620 ms (44.9 KiB/s) 13378509 bytes read in 2448 ms (5.2 MiB/s) 8678912 bytes read in 1753 ms (4.7 MiB/s) Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... I can see that some patches have been developed and @Igor has merged these in, is there something in particular that I need to do in order to do a successful update/upgrade? Is this what I should be following?

@djoness I also have V4.0 Box, have same X96Q-Armbian-H313 V4.0 boot screen, so, I burn "Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz" which you said to SD Card, My Box not work.Than i press and hold the Av button,The LED.Show Red,and. Screen Black. nothing. i don't press ,it will be inside to Android. what are you do, can make inside to Armbian.Tell me. Thanks a lot.

I've been using this setup for a few good weeks without issues, same powered hub and everything, however after accidentally unplugging the server and being unable to boot I decided to reimage the SD Card and now the box refuses to detect my external 1TB 2.5" HDD (powered hub). Currently running latest server Debian (Armbian_community_26.2.0-trunk.22_Aml-s9xx-box_trixie_current_6.12.59) on X96 Mini (Amlogic S905W). I've tried to recreate my setup as close as possible to what I had before, however, now I cannot seem to be able to detect the HDD. The OS is installed on the SD Card. lsblk looks like this: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 57.6G 0 disk ├─mmcblk0p1 179:1 0 512M 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / mmcblk1 179:32 0 14.7G 0 disk mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk zram0 252:0 0 960.7M 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk I can hear a clicking sound coming from the hdd, however it does not want to spin up. The HDD has around 8-9% free space left, and is formatted as EXFAT. Connecting to a windows laptop the HDD spins up and gets detected instantly, even with no external power. I'm completely at a loss regarding this, especially since I did my best recreating my working setup from a few hours ago.

Good to know. I'm interested in getting the red LCD's to work as they are cheaper and more available, I purchased the waveshare only to test my SPI, SBC, and DTS formatting were functional. Now that I confirmed how to translate DTS to work with my SBC, I can work on the red ili9486/8 without worrying about it being a formatting issue.

The v2 uses a diff wifi chip: SKW wifi module VS6621S I have a patch for it, which came from KICKPI in the deb builder, but... I don't have a V2 to work any magic on it. chuanzz at one point contacted KICKPI and they sent him an archive that had a bunch of Armbian adds in it, including the patches and board.confs. But the HDD I had the archive on got erased by mistake, so yeah... I don't have the info anymore. I don't see the K2B REV2 getting official support here or by me, as its using a wifi chip that is just to obscure. Here is a u-boot-v2025.07 binary for the K2B REV2 u-boot-sunxi-with-spl.bin

Hello, These boards (Radxa Rock 2F and Rock 2A) have standard support so there should probably be a forum section for them. In its absence, I created this topic in the section for the most "similar" board. Currently, we only have the `vendor` kernel available for both. It seems that both of them have been mainlined in 6.18, as seen here for example: https://www.cnx-software.com/2025/12/01/linux-6-18-release-main-changes-arm-risc-v-and-mips-architectures/ The config file for the board currently looks like this: # Rockchip RK3528 quad core 1-4GB SoC WIFI/BT 0-32GB eMMC BOARD_NAME="ROCK 2F" BOARDFAMILY="rk35xx" BOOTCONFIG="rock-2-rk3528_defconfig" BOARD_MAINTAINER="CodeChenL" KERNEL_TARGET="vendor" KERNEL_TEST_TARGET="vendor" FULL_DESKTOP="yes" BOOT_LOGO="desktop" BOOT_FDT_FILE="rockchip/rk3528-rock-2f.dtb" BOOT_SCENARIO="spl-blobs" IMAGE_PARTITION_TABLE="gpt" enable_extension "radxa-aic8800" AIC8800_TYPE="usb" I tried just adding "edge" in the KERNEL_TARGET line and building an image but this won't be enough to make it boot, will it? Any tutorials on how to get them to work on mainline?

@Maurizio Finesso@John Taylor@SteeMan I've had success using USB stick instead of SD Card (see my post on 1st page), however now the BOOT Fat32 partition was hidden for some reason, I used DiskGenius to unhide it. I didn't test this on the tv box yet. This also goes against what is being said in this thread (that there are no more Fat32 paritions visible in Windows) from this thread:

I did a bisect. 3381d25b77fbf1ebaaa151a9f2be66fbf1ca3a1e is the first bad commit commit 3381d25b77fbf1ebaaa151a9f2be66fbf1ca3a1e Author: Ricardo Pardini <ricardo@pardini.net> Date: Sun Oct 12 19:57:32 2025 +0200 I try to build 6.18 kernel with config file linux-meson64-edge.config taken from "good" 6.17 kernel. but result was a "slow" kernel. Before I hope to find "bad" change in kernel config, now it's clear problem not there. I have no more ideas 😢

I downloaded 'Armbian_25.11.2_Odroidc2_trixie_current_6.12.58_minimal.img.xz', flashed it to sdcard, and it booted fine. As a sidenote unrelated to the issue at hand, my first try was with the sdcard on a device with emmc, and in this case the boot process stopped after block-local (?), and dropped to initramfs shell prompt.

Can you check one from here: https://fi.mirror.armbian.de/incoming/igorpecovnik/odroidc2/archive/ Sizes seems alright.

Brillant, eselarm! I followed your suggestion to avoid USB-adapter issues and took my quite old laptop with a MCC/SD slot. Run fsck -fn /dev/mmcblk0p1 - no errors! As you suspected, the USB-adapter is at fault! I grabbed all SD-USB adapters I collected over the years and tried them. Different results, fsck without errors using few of them. My lesson lerned is: NEVER TRUST A USB-SD ADAPTER! The strange thing however is, that using this faulty adapter (14cd:1212 Super Top microSD card reader (SY-T18)) some images like Armbian_25.8.1_Rockpi-e_noble_current_6.12.41.img fsck'ed OK. I think all my adapters can cope w/o problems with simple, more or less sequntiell, reads/writes. It's what they do most of the time. I guess, when it comes to more complex I/O operations requested by fsck, some of them give out. What eselarm also suggested. Just for reference, the bad ones: 2 x 14cd:1212 Super Top microSD card reader (SY-T18) 5136:4678 Generic USB2.0 Device aaaa:8816 MXT microSD CardReader The OK ones: two with this inside: 090c:6200 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) microSD card reader and 14cd:127b Super Top SDXC Reader (very old, labeled hama) Thanks and regards, Chris

Hi @John Taylor, @SteeMan, unfortunatly it takes me time because I was not at home. I found that I can use the minimal or server version and only using Rufus. If I use Balena Etcher it doesn't create the fat32 partition named Boot. now I'm struggling because I would like to use the system on SD card but after that I do any changing for example IP from dynamic to static using armbian-config a lot of messages comes saying that EXT4FS is in read-only mode and I can use the system but not to install programs. I'm a little afraid to install on eemc because I have no android image. It is an old MXQ pro mini from leelbox.

Aha. We only test one randomly picked image per board - not all of them. And nobody noticed small size of the file ... I see now. Probably runner starved for memory or some other problem. Logs were already deleted so I can't check, but have started new build. Indeed All clear now.

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v2.6.2 >=60fps@1080p Yu-Gi-Oh LOTD Evolution

@Maxim Shell Does it have a SD card slot? If not then it won't be easy to install Armbian.

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v2.6.2 >=60fps@1080p Dead Cells

Armbian 25.8.2 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + DXVK-stripped v2.6.2 60fps@1080p Celeste

Yes, you're right, I did a little Googling and clarified the specifications.

moving to Amlogic TV Boxes as I believe (via a quick google search) that this is amlogic cpu based.

moved to tvboxes