Active threads

Old automated builds are not kept. Only last three releases https://github.com/armbian/community/releases Its 300Gb / week

Hi, can anyone help me with my board, I tried all 4 images from the github releases for the x96q, flashing them into sd card on windows using belenaetcher, then pluging into the box and booting it, it gets stuck at red light, the moment I eject the sd card it boots into android. am I doing something wrong or I need a specific image?

It boots but does not recognize USB keyboard input. Not possible to login.

hallo @WanJiXianSheng, responding to this image, for the SUB position where the SD card is installed, there are 3 cables, what is their function? Please share here the guide for flashing to Armbian thx..

Success! Thank you so much @Harleyyyu! It now boots perfectly off the eMCP. If anyone wants it I can write a small guide on how to do this, just to make this easier and faster for folks in the future.

Hello @Malay, et.al, after submitting my PullRQ to the Armbian repo, I think it's best to cope first with the annotations I received from that. It complains about missing board photos, and some LLM generated blurb partly valid suggestions, partly not. The current status of Armbian's Spacemit support does not make the RV2 board a good video player: GPU support is missing and I'm pretty unsure if it's possible to include the HW video encoding / decoding feature that is in the chip. Which is 4k@30 with diverse codecs according to the chip description PDF. I am glad, that X11 framebuffer video runs and I am unsure if I can proceed here b/c I am not a video / GPU / EGL / vulkan specialist. Anyhow, thank you for the pointer to the Spacemit FAQ I did not recognize until now. While the PowerVR page from mesa3d states: "no IMG BXE-2-32" (https://docs.mesa3d.org/drivers/powervr.html), the respective Gitee repo contains closed-source BSD licensed Risc64 compiled shard objects (*.so), probably similar to the Nvida binary user space closed drivers that does the GPU support for the big videos cards. This may be worth a look, but as I wrote above, prio task is to bring the support into the Armbian tree. Best // Sven-Ola

http://blog.armbian.com/content/images/2026/01/githubhighlights-2-2.webpThis week’s Armbian development saw a wide range of updates focused on automation, hardware support, and workflow improvements. Key highlights include the introduction of automatic YAML target generation, expanded support for Hetzner ARM64 runners, and enhancements to the redirector update workflow with cache mirror support. Several board-specific fixes and feature additions were made, including improved power cycle handling for meson-sm1 devices and new binary files for RK35 series components. The team also advanced kernel support, notably enabling RDNA2 GPU compatibility and initial kernel 6.18 support for Ayn odin2. Continuous integration and build reliability received attention through Docker-based unit tests and improved artifact management. Overall, these changes reflect ongoing efforts to streamline development processes and broaden hardware compatibility across the Armbian ecosystem. Add automatic target YAML generation from image-info.json. by @igorpecovnik in armbian/armbian.github.io#184Add board-level extension to mask Wayland desktop sessions. by @schwar3kat in armbian/build#9268Add cache mirror support to redirector update workflow. by @igorpecovnik in armbian/armbian.github.io#189Add edge branch support to community targets. by @igorpecovnik in armbian/armbian.github.io#195Add exposed.map download step to download index workflow. by @igorpecovnik in armbian/armbian.github.io#190Add Hetzner server creation with cloud-init, swap, and configurable runners. by @igorpecovnik in armbian/actions#13Add new binary files for various RK35 series components. by @ghhccghk in armbian/rkbin#42Add regulator-boot-on to meson-sm1-odroid and -hc4 to fix power cycle during boot. by @ean365 in armbian/build#9217Add scripts/generate_targets.py to workflow push trigger. by @igorpecovnik in armbian/armbian.github.io#185Add workflow for enabling 16 Hetzner ARM64 runners. by @igorpecovnik in armbian/armbian.github.io#196arm64: enable AMD DC display controller for RDNA2 GPU support. by @igorpecovnik in armbian/build#9273atf: rk3399: fix PL330 DMA controller initialization. by @iav in armbian/build#9285Bump sm8250. by @CodeChenL in armbian/build#9180Change actions folder to actions-report. by @igorpecovnik in armbian/armbian.github.io#188Change exposed.map minimal patterns from bookworm to trixie, add forky as fallback. by @igorpecovnik in armbian/armbian.github.io#194chore: use release-signing policy for Windows artifacts. by @SuperKali in armbian/imager#87ci: add PR build artifacts with public download links. by @SuperKali in armbian/imager#81ci: use Docker containers for unit tests. by @igorpecovnik in armbian/configng#720cli: kernel-dtb: check dtc for version 1.7.2 before producing normalized dts. by @rpardini in armbian/build#9270config: arch: amd64: fix building kernel amd64 target with on arm64 host. by @rpardini in armbian/build#9271deps: update dependencies and document glib vulnerability. by @SuperKali in armbian/imager#88Enable debug. by @igorpecovnik in armbian/actions#14Enable Firefox download from PPA, drop Jammy and Oracular. by @igorpecovnik in armbian/os#424Exclude non-community trunk builds from promotion. by @igorpecovnik in armbian/armbian.github.io#193extension: grub: deploy qemu binary when doing cross build. by @amazingfate in armbian/build#9282feat: add image status warning for nightly builds and community boards. by @SuperKali in armbian/imager#83fix api change since v6.17. by @Spider84 in armbian/bcmdhd-dkms#5fix api change since v6.19. by @amazingfate in armbian/bcmdhd-dkms#6Fix uptime-kuma Docker image detection regex. by @igorpecovnik in armbian/configng#722fix: reduce board image scale and improve CI cache strategy. by @SuperKali in armbian/imager#86fix: regenerate Tauri updater signatures after SignPath code signing. by @SuperKali in armbian/imager#89fix: use any_changed output for reliable changed files detection. by @igorpecovnik in armbian/configng#725fix: use published_at for release sorting. by @igorpecovnik in armbian/community#46Framework: Add "Repeat Build Options" string at the end in case of er…. by @iav in armbian/build#9276framework: add custom_kernel_make_params extension hook. by @iav in armbian/build#9284Generate separate exposed.map patterns for stable and community boards. by @igorpecovnik in armbian/armbian.github.io#192Include community boards in exposed.map generation. by @igorpecovnik in armbian/armbian.github.io#191Initial support for kernel 6.18 on Ayn odin2. by @kasimling in armbian/build#9286mainline: bump to 6.19-rc6. by @EvilOlaf in armbian/build#9278memoize: add user feedback and configurable timeout for flock. by @iav in armbian/build#9262NanoPi R5C: Update to v2026.01; enable BTRFS support. by @okrc in armbian/build#9291orangepi5-plus: u-boot: restore vendor uboot with blobs. by @rpardini in armbian/build#9287orangepi5-plus: u-boot: use mainline ATF; bump to v2026.01; drop funky CE config options. by @rpardini in armbian/build#9261Override new yaml files - drop the code here if it works.. by @igorpecovnik in armbian/os#423radxa-e54c: board config: replace 'hacky' Wayland fix with wayland-sessions-mask extension. by @schwar3kat in armbian/build#9281radxa-zero2/khadas-vim3l: u-boot: disable LWIP. by @rpardini in armbian/build#9272refactor: conditionally hide custom image button when manufacturer is selected. by @SuperKali in armbian/imager#85refactor: standardize redis module and improve workflow reliability. by @igorpecovnik in armbian/configng#723Reload redirector after we check all mirrors. by @igorpecovnik in armbian/armbian.github.io#178Remove browsers from RISC-V desktop app groups. by @igorpecovnik in armbian/armbian.github.io#186Rockchip 6.18.y: drop upstreamed patches. by @igorpecovnik in armbian/build#9288Rockchip EDGE: drop up-streamed patches. by @igorpecovnik in armbian/build#9290rockchip64: station-m3: Enable USB type-C port. by @kasimling in armbian/build#9246rootfs: enable loong64 in qemu binfmt registration. by @igorpecovnik in armbian/build#9279scripts: use git commit date for 'edited' timestamp instead of filesystem mtime. by @igorpecovnik in armbian/armbian.github.io#177Switch Docker module to distribution maintained packages. by @igorpecovnik in armbian/configng#719Update CI documentation to reflect automated target generation. by @igorpecovnik in armbian/documentation#867Use armbian-apps config for app-specific images. by @igorpecovnik in armbian/armbian.github.io#187work-around Ubuntu Rust coreutils bug in dirname affecting linux-headers board-side compile of scripts/mod. by @iav in armbian/build#9264View the full article

so whats the status on this issue is it resolved by running the rolling forky release and using network manager ?

Endless loop booting Image. I download Image form source: https://dl.armbian.com/odroidxu4/Bookworm_current_minimal-omv Flash Image with Rufus-4.11 --> no problem insert sd-card in odroid hc1 --> blue LED is flashing I ping to odroid with windows 'ping odroid -t -w 100' --> replied 10 seconds, then there was no response for 40 seconds, and it repeated, I wait 30 minutes. I use Image from archive without OpenMedaivault --> Booting Ok I install OMV 7.0 manually described following link: https://docs.openmediavault.org/en/7.x/installation/on_debian.html in first view everything seem fine BUT: after restart and save settings to SD-card --> odroid restarts after 20 seconds, if you do anything with huge load, it restarts, even 'apt update' or 'apt upgrade" I did several tests, buy a new SD-card try 3 different cards, remove hard drive remove PCB and renew thermal interface material, nothing helps. I installed it 5 to 10 times and I did the installation in different ways. Also nothing helps. I use my old working sd-card and I did some test, it works properly. (old means: installation is 2-3 years old) I try 'armbianmonitor -m' --> output: 23:30:52 600/2000 MHz 0.66 19% 6% 11% 0% 0% 1% 37.0 °C 0/3 The frequency changes depending on the load, I used stress -c 8 --> frequencey 1400/2000MHz -> works perfect I try Debian 12 (Bookworm) with OpenMediaVault from armbian download page. (Build Date: Jan 19, 2026) I try 'armbianmonitor -m' --> output: 22:10:52 200/200 MHz 0.66 19% 6% 11% 0% 0% 1% 24.0 °C 0/3 The frequency was always at 200/200MHz. I think I found the error in '/etc/default/cpufrequtils Both values are "0". MAX_SPEED="0" MIN_SPEED="0" I compare it with my old working sd-card. The values there: MAX_SPEED="2000000" MIN_SPEED="600000" I Update the Image: I 'unxz' the image that I had downloaded from armbian page, 'losetup' it, 'mount' the partition and change the value in 'cpufrequtils' to MAX_SPEED="2000000" MIN_SPEED="600000". I 'xz' the image, flash it to my sd-card and now the images works on my Odroid XU4/HC1 perfect. Is this a bug?

I think this is the First version of this board, please use the official release for this https://github.com/armbian/community/releases/ if it doesn't work https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/#findComment-183131 ask @Evgenii Egorenko

@shexplorer here are the first 10MB of the internal emmc. Extracted with dd if=/dev/mmcblk1 count=10 bs=1M | gzip > x88pro13_first_10MB_of_mmcblk.gz. please unzip first. see also the solutuion of this page: x88pro13_first_10MB_of_mmcblk1.gz

Hello. Where can I download multitul for rk3528?

@user03 Given that you now have a working uboot installed on the emmc, I'm 95% confident that following the standard instructions will let you move your SD card install to emmc. But there are no guarantees.

You can set conditions on which branch uses which uboot. Like this: https://github.com/armbian/build/blob/9aa6e1e29ec2d397bbe223bebaa93bd13ef79818/config/boards/orangepi5-max.csc#L21 If the BRANCH is edge, then use mainline uboot, specifically this tag.

Good afternoon. I have a Rockchip 3566 tablet.oscal pad 70 wifi Is it possible to install Armbian on it? I don't have a device tree (I couldn't find anything at all for the WiFi module except the test report), no drivers, nothing. I've found a related one (the letters at the end are slightly different), but there's a little information. The original Pineta B2 costs 159, plus shipping and taxes...that's 300. But the aforementioned one costs 100 and doesn't require taxes! That's what got me thinking. Prices are in dollars. The bootloader can apparently be unlocked with a simple command (according to Google Assistant!) I need the tablet for learning Linux and watching videos in the browser...will it handle it? Is this even possible for a beginner? Best regards and gratitude... I'm writing using Google Translate, so there may be some inaccuracies... I apologize for that! motherboard R863T-RK3566-DK-V1.0 wifi module wxt42j1001s I don't know what kind of touchscreen and display it has. Will I need to unlock the bootloader? I understand it's probably very difficult...isn't the processor too old for our times? Or is installing Armbian probably not an option, and shouldn't I waste my time on it and buy something else? Thanks from the bottom of my heart to everyone who responded.

It looks like mksclient is python code can be patched. Sovol3D forum Enable LED light toggle in Mainsail I followed the steps and was able to get an LED toggle in Mainsail on my SV06 Ace I did loose the touchscreen control of the LED but that's acceptable. I only need the LED when using the Camera to check for Failed prints and previously left the LED on during printing. Now I can save a little electricity😀. To me this also has pertinent implications to the thread. mksclient must be a python blob that can runs on boot. If were willing to tolerate the "black box" close source nature of mksclient, a touch screen supporting build, targeting the OEM electronics, should be possible.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 3ec5de03c (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) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v1.6.1 15~60fps@720p box64 environment variables: FF13 Lightning Returns

Thank you

Hello, thk work fine on my X88 pro13 Here is : Armbian_community_26.2.0-trunk.332_Hinlink-ht2_noble_vendor_6.1.115_gnome_desktop.img Armbian_community_26.2.0-trunk.332_Hinlink-ht2_noble_vendor_6.1.115_gnome_desktop.img

By any chance, could someone post a link to a working image for Cubox I? I'm trying to find any working Armbian build and there is nothing that works. Thanks!

What happens if your start armbian-resize-filesystem.service manually? IE "sudo systemctl start armbian-resize-filesystem.service" and then check the log for the service?

You can create an extension including something like unset armbian_kernel_config__force_pa_va_48_bits_on_arm64

Nevermind, got the answer from here.

Interested myself in the 3W in general, and if I can find them anywhere. They have the proper chip for a zero form factor board to use with the Radxa 5C and 5A, and several other boards. So I've looked, but they seem to have been outdated by the better zero form factor boards... which also seem to have a specific chip type, and aren't really compatable with the other chips if you're trying to give yourself some headroom to run clusters or offload some processes. I don't know too much about too many things yet, but I know that I need to stick with 1 chip, like a GPU arcitecture, and I can't find the 3W anywhere for any type of reasonable price. I think I found a few for like $300, but the dream of using this stuff at the top end of what it can be used for is looking grim as I am having troubles finding some of these parts for this more developed chip style. I'm sure in due time, it will all be replaced by the new Radxa zero form factor, along with the Pi form factor which will probably gravitate to this new more powerful model. The Zero board has twice the specs aprox. as the old 3W, which means likley the next Radxa board is comming out swinging to start with 32GB of RAM, and then it'll be updated with 64GB. As they seem to do that... Start half mast, then bring out a new twice as powerful model. Hoping to get my first arm project going, and I wish I knew more about ARM in general before I started focusing on 1 chip style. Radxa is cool, and they are buff as can be, but as ARM evolves, the specificity of board type to the different things you have to do is a big big pain in the ass that makes this whole adventure more painful then it should be... Eventually I'm sure it'll all come together into a standard.... But by then, you can't be a pioneer in the tiny computer parts projects. Hope this thread evolves some. I know just seeing a title on 3W caught my eye, and it's on the top of the list. I'll be getting more involved with all of this in the days to come. If you can message me, feel free. I am pretty Armtarted, and would love any information I can get.