Active threads

Unfortunately, I have exactly the same problem.

http://blog.armbian.com/content/images/2026/01/githubhighlights-2-1.webpThis week in Armbian development saw a significant round of kernel updates, board support enhancements, and workflow improvements. Notable changes include refactoring of the sunxi patchset, multiple kernel bumps for Rockchip and sunxi platforms, and the introduction of parallel repository management. Several device-specific fixes were implemented, such as improved fan control and USB support for the Station M3, and initial support for the OrangePi 4A. Deprecated and problematic drivers were removed to streamline builds, while eBPF options and bootloader updates further enhance system capabilities. The team also addressed various patching, locale, and build issues, ensuring smoother operations across supported hardware. sunxi: refactor full patchset. by @EvilOlaf in armbian/build#9219Apply rtl8723cs bluetooth only with kernels above 6.1. by @paolosabatino in armbian/build#9184armbian-kernel: more eBPF-oriented options for userspace tooling. by @rpardini in armbian/build#9193atf: once again no-warn-rwx-segment woes. by @rpardini in armbian/build#9162Drop USB wireless driver that doesn't want to compile. by @igorpecovnik in armbian/build#9202Enable OrangePi 4A CSC Initial Support. by @juanesf in armbian/build#9185evict device trees from patches into bare dt. by @EvilOlaf in armbian/build#9215extensions/mtkflash: mtk-flash --no-erase-mmc1 landed upstream as --preserve-boot1. by @rpardini in armbian/build#9198extensions/ufs: don't check sfdisk version also when BUILDING_IMAGE!=yes. by @rpardini in armbian/build#9161feat: implement parallel repository management workflow. by @igorpecovnik in armbian/build#9224Fix broken patch due to upstream changes, drop edge kernel as its not used. by @igorpecovnik in armbian/build#9200Fix locale warnings during chroot operations. by @iav in armbian/build#9160Fix rootfs compilation (dropping deprecated gtk2 engines), drop broken patch on meson64. by @igorpecovnik in armbian/build#9199framework & kernel config - rework the optionality of kernel builtins vs modules. by @tabrisnet in armbian/build#9165framework - extension_hook_opt_out. by @tabrisnet in armbian/build#9178genio/radxa-nio-12l: OPTEE/u-boot/TF-A/FIP bootloader + EXT=mtkflash + fixes. by @rpardini in armbian/build#9159genio: kernel quality-of-life enhancements. by @rpardini in armbian/build#9167grub: remove invalid hack for hvc0. by @rpardini in armbian/build#9189Helios64: update uboot to v26-01. by @iav in armbian/build#9125host-release: allow to build on resolute. by @rpardini in armbian/build#9190mixtile-blade3: board: disable 'edge' kernel, as it's not ready for end-users yet. by @rpardini in armbian/build#9181mvebu64: re-revitalize espressobin - can build (under noble) again. by @rpardini in armbian/build#9182NanoPi R3S LTS: Update to u-boot-v2026.01. by @pyavitz in armbian/build#9207opt-out of driver_rtl8723cs in some legacy kernels so they build again. by @rpardini in armbian/build#9176patching: introduce add-only mode for DT Makefile AutoPatcher. by @rpardini in armbian/build#9204PR actions scripts: fix workflow execution name. by @igorpecovnik in armbian/build#9186rock-3a: unset BOOTFS_TYPE for non-vendor builds. by @EvilOlaf in armbian/build#9068Rockchip bump current to 6.18 and edge to 6.19. by @paolosabatino in armbian/build#9169Rockchip maint: drop upstreamed patch. by @igorpecovnik in armbian/build#9196rockchip/uefi-loong64 6.19: rewrite patches against 6.19-rc4. by @rpardini in armbian/build#9172rockchip64-6.18: Enable audio for HDMI0 on station-m3. by @kasimling in armbian/build#9170rockchip64: bump edge to 6.19; current 6.12 -> 6.18. by @EvilOlaf in armbian/build#9067rockchip64: patch ATF 2.13 to build on gcc-14+ (ref rk3399's m0). by @rpardini in armbian/build#9208rtl8723cs: stop including proprietary driver for kernel 6.19 onwards. by @paolosabatino in armbian/build#9171station-m3: Fix fan speed and enable USB 3.0 Type-A port. by @kasimling in armbian/build#9177sun55iw3.conf bump u-boot to v2026.01 (final). by @juanesf in armbian/build#9197sunxi-6.18: rename patch that does fixups for clarity. by @rpardini in armbian/build#9213sunxi: Add CONFIG_TTY_OVERY_SDIO to edge kernel config. by @EvilOlaf in armbian/build#9226sunxi: bump edge to 6.18.4. by @EvilOlaf in armbian/build#9188sunxi: bump current and edge to latest minor. by @EvilOlaf in armbian/build#9229sunxi: bump current to 6.12.64. by @EvilOlaf in armbian/build#9195sunxi: cleanup old patchsets. by @EvilOlaf in armbian/build#9212sunxi: move overlays from various patches into auto-patcher. by @EvilOlaf in armbian/build#9211thinkpad-x13s: bump arm64-sc8280xp to steev's 6.18.y. by @rpardini in armbian/build#9173tools/repository/extract-repo.sh: simplify extraction by copying directly from pool. by @igorpecovnik in armbian/build#9174u-boot: allow custom LOGLEVEL with UBOOT_LOGLEVEL (default to 6). by @rpardini in armbian/build#9191u-boot: bump u-boot to v2026.01 (final) for boards that had -rcX. by @rpardini in armbian/build#9179kernel-make: clang: Remove -Wno-error=unknown-warning-option from clang KCFLAGS.. by @iav in armbian/build#9183View the full article

Armbian doesn't support TV Boxes, all Community Supported builds are given that description. Yes, per the instructions have you tried all the dtbs that might be relevant? In general, I'm not aware of any dtbs in mainline linux for the s905l3 cpu. I don't know what the closest might be. In general, due to lack of support by Amlogic, the efforts to support newer versions of their CPUs in mainline linux have essentially stopped. For example the project website that tracked progress on mainlining amlogic (https://linux-meson.com/mainlining.html) shows that efforts stopped around two years ago. Realistically only older amlogic cpus (i.e. cpus released at least 4 or more years ago) are going to be supported in mainline linux (and thus Armbian). And unfortunately I think the s905l3 falls into the newer category.

I noticed the same thing. It looks like the server images might have been temporarily removed, possibly during a site update or reorganization. I’d suggest keeping an eye on the official download page or checking the Armbian GitHub mirror, they usually restore missing builds pretty quickly.

Alright, well, such things can happen when attempting to fix a bug and not having hw to test on hand I'll leave it to Cornelius to send a fix since he can directly verify if it works.

Latest nightly I found seems to work, built from source and installed klipper, etc using normal instructions online. Klipperscreen is not working but I believe I will need to build the full graphical version to get this working with my Waveshare 7" hdmi screen. Wifi and general usage of this build seems very stable. Note: I did that the lagtest ngihtly code PR for CB2 was months old, but again, it seems to work.

Been looking at getting my Helios64 back up and running after experiencing a lot of instability a few years ago. Stumbled across this thread and things look somewhat promising, but after reading through I'm unsure what I should actually do to get things running! Lots of different posts with lots of different .dtb files, seemingly PR's in to the armbian repo etc. As of today, what is the best approach to get things up and running? Do the PR's mean I should be able to just use Armbian direct from the site and have a stable NAS?

Hello, sorry for late answer, but I had no time to experiment with my rock64 board. Maybe this issue is already resolved, if so please let me know. I'm still using kernel 6.6.63 and holding kernel packages in order not to break a working home server. So I managed to temporary switch kernel to 6.12.9 again for testing (copied old /boot and corrected symlinks) and enter UART console: Here is output of U-Boot commands you asked: Hit any key to stop autoboot: 0 => setenv b => setenv c => setenv a "a/b" => setexpr b sub "a/" "" a Unknown command 'setexpr' - try 'help' => echo ${b} => setexpr c 1 + 1 Unknown command 'setexpr' - try 'help' => echo ${c} => fdt fdt - flattened device tree utility commands Usage: fdt addr [-c] <addr> [<length>] - Set the [control] fdt location to <addr> fdt move <fdt> <newaddr> <length> - Copy the fdt to <addr> and make it active fdt resize [<extrasize>] - Resize fdt to size + padding to 4k addr + some optional <extrd fdt print <path> [<prop>] - Recursive print starting at <path> fdt list <path> [<prop>] - Print one level starting at <path> fdt get value <var> <path> <prop> - Get <property> and store in <var> fdt get name <var> <path> <index> - Get name of node <index> and store in <var> fdt get addr <var> <path> <prop> - Get start address of <property> and store in <var> fdt get size <var> <path> [<prop>] - Get size of [<property>] or num nodes and store in <var> fdt set <path> <prop> [<val>] - Set <property> [to <val>] fdt mknode <path> <node> - Create a new node after <path> fdt rm <path> [<prop>] - Delete the node or <property> fdt header - Display header info fdt bootcpu <id> - Set boot cpuid fdt memory <addr> <size> - Add/Update memory node fdt rsvmem print - Show current mem reserves fdt rsvmem add <addr> <size> - Add a mem reserve fdt rsvmem delete <index> - Delete a mem reserves fdt chosen [<start> <end>] - Add/update the /chosen branch in the tree <start>/<end> - initrd start/end addr NOTE: Dereference aliases by omitting the leading '/', e.g. fdt print ethernet0. => echo ${fdtfile} rockchip/rk3328-rock64.dtb => echo ${fdt_addr_r} 0x01f00000 => echo ${kernel_addr_r} 0x02000000 => echo ${ramdisk_addr_r} 0x04000000 => ver U-Boot 2017.09-rockchip-ayufan-1065-g95f6152134 (Apr 06 2020 - 08:10:39 +0000) aarch64-linux-gnu-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0 GNU ld (GNU Binutils for Ubuntu) 2.30 => CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.10 | VT102 | Offline | ttyUSB0 I have set up rock64 to boot from SSD connected over USB3-SATA adapter (bought from pine64 store) without SD-card. To make it work I flashed latest U-Boot from ayufan to SPI by this tutorial. Maybe this error because of old U-Boot, and you're right, looks like it doesn't support setexpr command djurny, thank you for looking into this. And one question I don't understand, if I should upgrade U-Boot in SPI or I should erase SPI and wirte U-boot somewhere else? And will I be able to boot directly from USB-SSD without SD-card after that?

I don’t know about Odroid n2 but all the 2025.11 builds with graphical ui get stuck when the initial setup is completed and message appears “now booting to graphical session” and never boots 2024 builds do boot and stay normal I am using mainline uboot via spi boot.

Hi there, I also bought one (V1.5) and tried to use armbian. Unfortunately, I managed to brick it. I booted your image @johlnx from sd, that worked. Then I overwrote the internal EMMC with your image and the box won't boot anymore. Any idea how I can fix it? I made an backup of the original image, but I also read that it may be incomplete because of read protection in uboot of the emmc? I also tried to get into MaskMode by pressing the button and connecting the USB 2.0 to my Windows-PC but no device is discovered. I attached the serial uboot log. Hope somebody has a suggestion how i can boot something again. Thanks boot_with_armbian_sd_insert.log boot_without_sd_insert.log

Hello everyone! I am running Armbian in a BTV11 box (Amlogic S905X3) alongside the "meson-sm1-sei610.dtb". My cabled ethernet connection is working fine but not WIFI. No networks are found. I have already tried alternatives like meson-sm1-sei610-ethfix.dtb, that leads to my ethernet to also stop working. At first the Kernel was looking for `brcmfmac4330-sdio.seirobotics,sei610.bin` firmware, that doesnt exist in Armbian. So I made a symlink pointing to a generic `brcmfmac4330-sdio.bin`. Saw that similar fixes worked for other people. This is what I see from logs: `sudo dmesg`: [ 8.451121] brcmfmac: F1 signature read @0x18000000=0x16044330 [ 8.456690] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4 [ 8.488102] usbcore: registered new interface driver brcmfmac [ 8.495653] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.clm_blob failed with error -2 [ 8.858975] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 8.871034] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104 [ 13.975072] brcmfmac: brcmf_sdio_readframes: read 97 bytes from channel 1 failed: -84 [ 13.979176] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [ 14.014920] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84 [ 14.017205] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [ 16.618796] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [ 16.639467] ieee80211 phy0: brcmf_netdev_open: failed to bring up cfg80211 [ 18.506857] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred [ 18.507694] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 [ 22.171208] brcmfmac: brcmf_sdio_readframes: RXHEADER FAILED: -84 [ 22.171730] brcmfmac: brcmf_sdio_rxfail: abort command, terminate frame, send NAK [ 24.554983] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout [ 24.575580] ieee80211 phy0: brcmf_run_escan: error (-110) More info available from Armbian monitor: https://paste.armbian.com/zuwididupe Does anyone have any insight that might help me figure out whats wrong with my box's WIFI?

Hi everyone. I'm new here. I found and ordered a 4-inch touchscreen with an ili9488 and xpt2046 on AliExpress. I was thinking about connecting it to a Raspberry Pi Zero 2W for my 3D printer's KlipperScreen. Since I had accelerometers connected to spi0, I connected the display and touchscreen to spi1. I thought it would be easy, since I found an article about connecting an ili9341 display to an Orange Pi Zero 3 for the same purpose: https://3dtoday.ru/blogs/3c60a2061c/dnevnik-tronxy-crux-1-displei-klipperscreen-seipery. But I'm new to Linux, so I followed guides to configure Klipper, literally copying and pasting commands. I'm using a ready-made mainsailos 64-bit. I spent almost a week trying to get the display working. I tried various ready-made libraries, but most of them gave me errors. For example, only after a couple of days of trying to use fbcp-9341 did I realize it doesn't support touch input, which isn't what I need, and that the library is only designed for 32-bit systems. I tried using AI based on the article with and without 3dtoday. But the best I could achieve was after some .dtbo file was /dev/fb1 and /dev/event0. When running one Python script, the screen displayed rectangles with gradients from white to black, but after changing the .dtbo file, when I ran the same script, I only got a black screen with multicolored dull horizontal stripes. I couldn't display any color other than black, white, and gray. I followed most of the steps suggested by the AI, since, as I already said, I'm a Linux noob. I'd be glad if someone could help me. My connection pins: Display -> Zero 2W CS - GPIO18(CE0.SPI1) RST - GPIO26 DC - GPIO13 SDI - GPIO20(MOSI.SPI1) SCK - GPIO21(SCK.SPI1) BL(LED) - GPIO6 Touch_CK - GPIO21(SCK.SPI1) Touch_CS - GPIO17(CE1.SPI1) Touch_DI - GPIO20(MOSI.SPI1) Touch_DO - GPIO19(MISO.SPI1) Touch_PEN - GPIO12 Note: I'm from Russia and my English is pretty bad, so all text was translated using a translator. I'm attaching a photo of the latest result I was able to achieve.

Hi @sicxnull, @Nick A thank you very much for your support. Probably last night I was very confused when I wrote my post. Of course the v5.1 updated will be nice to have but looking better I can say to you and to @ventara that the armbian image suggested from Nick to Trauma (https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz) works fine on X96Q vs 5.1 only things the led in front remain always red and that why I was thinking it doesn't boot. Ethernet port works but wifi doesn't work. Never mind ethernet is enough. On the other side when I compare the two release (sicxnull and Nick) I didn't realize that I copy two times the same image on two different sd (I was really too tired) so don't consider the indication that I give you apart the wifi chip. That is right!

Today all works, thank you for all who fixed this problem 🙂 apt update Get:1 http://security.debian.org trixie-security InRelease [43,4 kB] Get:2 http://deb.debian.org/debian trixie InRelease [140 kB] Get:3 http://deb.debian.org/debian trixie-updates InRelease [47,3 kB] Get:5 https://github.armbian.com/configng stable InRelease [5 467 B] Get:4 http://armbian.lv.auroradev.org/beta trixie InRelease [39,4 kB] Get:6 http://deb.debian.org/debian trixie-backports InRelease [54,0 kB] Get:7 http://security.debian.org trixie-security/main armhf Packages [88,8 kB] Get:8 http://deb.debian.org/debian trixie/non-free armhf Packages [69,9 kB] Get:9 http://deb.debian.org/debian trixie/non-free-firmware armhf Packages [6 685 B] Get:10 https://github.armbian.com/configng stable/main armhf Packages [434 B] Get:11 http://deb.debian.org/debian trixie/main armhf Packages [12,7 MB] Get:12 http://deb.debian.org/debian trixie/contrib armhf Packages [50,6 kB] Get:13 http://deb.debian.org/debian trixie-updates/main armhf Packages [5 144 B] Get:14 http://deb.debian.org/debian trixie-backports/main armhf Packages [133 kB] Get:15 http://deb.debian.org/debian trixie-backports/contrib armhf Packages [4 368 B] Get:16 http://deb.debian.org/debian trixie-backports/non-free-firmware armhf Packages [3 856 B] Get:17 http://deb.debian.org/debian trixie-backports/non-free armhf Packages [1 520 B] Fetched 13,4 MB in 12s (1 073 kB/s) 32 packages can be upgraded. Run 'apt list --upgradable' to see them.

Thanks @Werner this is fixed, it works. In my case auto selected mirror is fi.mirror.armbian.de .

Workaround solution: downgrade to 2.3.2 apt install zfs-dkms=2.3.2-2 zfsutils-linux=2.3.2-2 libzpool6linux=2.3.2-2 libzfs6linux=2.3.2-2 libuutil3linux=2.3.2-2 libnvpair3linux=2.3.2-2 # block unwanted upgrade: apt-mark hold zfs-dkms=2.3.2-2 zfsutils-linux=2.3.2-2 libzpool6linux=2.3.2-2 libzfs6linux=2.3.2-2 libuutil3linux=2.3.2-2 libnvpair3linux=2.3.2-2

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 4.1 (https://ryanfortner.github.io/box64-debs/) + wine-10.20-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.20) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.1 (more likely to be crash-proof than other Dxvk versions) ~60fps@720p (Medium/High settings) box64 environment variables: Need for Speed - Underground 2

Hello, the link you shared has expired. Could you please re-analyze it

Hello, im trying to get my rk322x board with SV6051P chip to work, i tried every LED config but wpa_supplicant crashes on boot every time. Here are the dmesgs: dmesg_led8.logdmesg_led7.logdmesg_led6.logdmesg_led5.logdmesg_led4.logdmesg_led3.logdmesg_led2.logdmesg_led1.logdmesg_default_dto.log Anyway to fix this?

@chris178 SmartSolution on discord says his camera works. SmartSolution Hi, i had problem with camera and isp color quality After check and test download radxa-a733 t2 rsdk , image file and upload on mmc and after load system all camera works good

Duplicate

That's advanced as hell for build, but you can use any Rockchip SDK to make it, Some factoryes share the SDK online Some don't you will just compile a copy of the same file that you can find in the android image

And others: https://docs.armbian.com/Mirrors/#current-mirrors

It works with this old drivers in windows. CP2102 doesn't reach high baud rates in linux. Baud rate: 1500000 Data bit: 8 Stop bit: 1 Parity check: none Flow control: none ☑️ CP2104 TTL Tested the original one! ☑️ CP2102 TTL Tested the chinese fake one! with this Driver

I can confirm that booting Odroid M1 from SD card does not work with U-Boot versions newer than 2024.04. Many thanks to IAV for providing a workaround. Perhaps most people are booting from NVMe now, so this issue has flown under the radar? # Install U-Boot 24.5.1 (maps to upstream v2024.04) apt-get install -y linux-u-boot-odroidm1-edge=24.5.1 # Freeze the package at that version "printf 'linux-u-boot-odroidm1-edge hold\n' | sudo dpkg --set-selections" # Flash SPI directly from the package artifacts (or via armbian-install) flashcp -v /usr/lib/linux-u-boot-edge-odroidm1/idbloader.img /dev/mtd0 flashcp -v /usr/lib/linux-u-boot-edge-odroidm1/u-boot.itb /dev/mtd2 # Confirm strings /dev/mtd0 | grep -m1 "U-Boot" # U-Boot SPL 2024.04 (Jan 10 2026 - 10:54:44 +0100) strings /dev/mtd2 | grep -m1 "U-Boot" # FIT image for U-Boot with bl31 (TF-A) Now I can boot from sdcard again w/o RCY button. To use only ZFS on my system I compiled zfs into U-Boot. That worked but the problem was still with U-Boot's handling of the mmc1 somehow. Even though zfsls/zfsload were present in the SPI-flashed U-Boot, that build immediately reinitialized mmc1 in HS200 (1.8 V) mode and hit the “Card did not respond to voltage select! : -110” failure before the boot script could run. So the inability to boot the ZFS v28 pool was due to the SPI U-Boot’s bad MMC tuning, not the ZFS commands themselves. For future reference I’ll leave here on how to built U-Boot with ZFS support from the upstream sources: # Workspace & Dependencies apt install git gcc-aarch64-linux-gnu bison flex device-tree-compiler libssl-dev make python3 ninja-build build-essential mkdir -p ~/work/u-boot && cd ~/work/u-boot # Upstream U-Boot git clone --depth=1 --branch v2024.04 https://source.denx.de/u-boot/u-boot.git # Firmare blobs git clone --depth=1 https://github.com/rockchip-linux/rkbin.git # Prepare .config cd u-boot cp configs/odroid-m1-rk3568_defconfig .config scripts/config --file .config --enable CONFIG_CMD_ZFS yes "" | olddefconfig # Compile make -j$(nproc) \ BL31=../rkbin/bin/rk35/rk3568_bl31_v1.45.elf \ ROCKCHIP_TPL=../rkbin/bin/rk35/rk3568_ddr_1560MHz_v1.23.bin # Flash SPI directly from the package artifacts (or via armbian-install) cp spl/u-boot-spl.bin /usr/lib/linux-u-boot-edge-odroidm1/idbloader.img cp u-boot.itb /usr/lib/linux-u-boot-edge-odroidm1/u-boot.itb flashcp -v /usr/lib/linux-u-boot-edge-odroidm1/idbloader.img /dev/mtd0 flashcp -v /usr/lib/linux-u-boot-edge-odroidm1/u-boot.itb /dev/mtd2