Active threads

Probably dead, yes. It looks like it is in read-only mode, so you cannot even erase it. Unfortunately for you, the way I designed the armbian boot requires either an empty flash or an installed u-boot that boots from sdcard first. You have three options: 1) hack the armbian boot using the multitool bootloader, but I don't suggest doing so because updates may overwrite the changes 2) remove the eMMC phisically, desoldering it 3) short the eMMC clock pins permanently, similar to what you would do when you want maskrom mode. The board will then always boot from sdcard. See the unbrick paragraph in the first post for some instructions.

THANK YOU so much for this effort. I no longer regret buying an OrangePi RV2!

There was a successful test with Debian Forky in RK3566 I saw some progress and success in the last 2 days. Someone made compiled ffmpeg 8.0+v4l2request and made it work in Debian Forky... which also carries ffmpeg 8.0 https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427 Does this mean that I need to use Debian Forky too? (I was staying with Debian Bookworm because H264 hwaccel only worked there) References: https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3 https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 https://tracker.debian.org/pkg/ffmpeg

How do you power the bananapi m1? It has 2 microUSB connectors.

Rpi support for whatever of their devices is mainly on the level of RaspberryPi OS. We use their kernels sources as base, add some additional things and release timing is different - not much difference. If they added new device, it should just work. If anyone wants to improve support or fix WiFi -> https://github.com/armbian/build/pulls

@Bones558 I guess you are using a USB-C to HDMI adapter? I bought one and it doesn't work on kernel 6.6. I think it's because the DRM heap driver hasn't been updated yet. I got a Micro HDMI to HDMI cable, and that works.

http://blog.armbian.com/content/images/2026/01/coverleter.pngWelcome 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. http://blog.armbian.com/content/images/2026/01/image-2.pngJoin Armbian at embedded world 2026. Meet us in Hall 3, Booth 3-556 (Seeed Studio), where we’ll be showcasing the Armbian build framework and how it powers reliable, production-ready Linux for ARM devices. FriendlyElec’s NanoPC T6 Plus: The flagship edge computing powerhouse and media stationThe NanoPC T6 Plus, powered by the performance-optimized Armbian OS, is your ticket to a truly professional, high-speed edge computing experience. This industrial-grade device is built around the flagship Octa-core Rockchip RK3588 SoC and now features a massive upgrade to LPDDR5 RAM (up to 32GB), giving it the muscle tohttp://blog.armbian.com/content/images/icon/favicon-40.icoArmbian blogMecid Urgancihttp://blog.armbian.com/content/images/thumbnail/T6-Plus-01.pngSponsored Github HighlightsThis 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 andhttp://blog.armbian.com/content/images/icon/favicon-36.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/githubhighlights-2-2.webpForget third-party utilities: meet Armbian ImagerArmbian Imager eliminates the guesswork from flashing SBC images. Real-time board detection, persistent caching, and built-in safety make installation fast, simple, and risk-freehttp://blog.armbian.com/content/images/icon/favicon-37.icoArmbian blogDaniele Brigugliohttp://blog.armbian.com/content/images/thumbnail/introducing-armbian-imager.pngArmbian 2025: by the numbersOpen hardware is growing faster than ever and breaking in new ways. 2025 has been a productive year for the Armbian project. As the Single Board Computer ecosystem continues to fragment and expand, Armbian has consolidated its position as the universal glue holding the open-source hardware world together. Our missionhttp://blog.armbian.com/content/images/icon/favicon-39.icoArmbian blogMichael Robinsonhttp://blog.armbian.com/content/images/thumbnail/New_review1.pngView the full article

Thanks Igor. Just for reference, I also tried Armbian_community_26.2.0-trunk.332_Odroidhc4_forky_current_6.18.7_minimal.img apt update apt upgrade apt install linux-headers-current-meson64 apt install zfsutils-linux zfs-initramfs zfs-dkms zfs-zed Everything went fine and seams to working OK. Chris

@Harleyyyu Your project could be interesting , I would suggest to open a dedicated 3ad on It own so people can contribute. As you have already realized by yourself quite all hardware and drivers aspects of this rk322x soc have bene investigated by @jockand/or @ilmich But if you achieve any progress on GENERAL drivers and performance that isn't already been discussed or achieved you can came back here to share Thanks

Hi! This is my first message here, congrats to the community for building this I would also like to corroborate that the current Balena Etcher, in Windows at least, is not writing the image correctly to the SD card. The Armbian imager did it well for me. I just booted an unused A95X (S905X) "Mini Kitty" with Armbian, but I don't think I will spend too much time with it, I already got a lot of mini PCs for servers and it's too slow for a terminal 😅 What do you recommend me to do with this little box? Thanks!

It is a AP-mode problem of the Realtek 8822CE chipset. Replaced the M2 card with Intel AX200 card and since then solid as a rock

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 72807b6b9 (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.7.1 50~60fps@1080p (no AA) box64 environment variables: FlatOut 2 Enhanced

@Nick A I flashed your latest build in Dec.2025 which is named to use for Transpeed, and in addition, manually added brcmfmac4334 firmware. Wifi is working now but bluetooth. Other malfunction in previous rom version April.2025 also disappear. Thank for your time to advise me

I downloaded image today using Armbian Imager, and it asked me to run something like armbian-update. I installed the system afterward, but it didn’t work.

Ordered 2 more X96Qs off aliexpress. will see what versions i get. Will build images for them if they're different.

There is no way. You need a dedicated image for your hardware. https://docs.armbian.com/User-Guide_FAQ/

@Torte continued to help on his github site. The boot.img of the OEM firmware appears to set up a serial framebuffer screen and some shenanigans with the camera. I'm pausing the thread for now - need to figure out a path to reverse engineer the boot.img. Otherwise, alternative boards will need to be adapted.

Coming late to the party, but I have observed a similar thing with moderm kernels on PCduino 3 nano. To know what is happeneing, have you tried connecting to UART? That gives you more info about what is going on. Now I have trouble with the OTG port. I am unable to configure it for mass storage.

OK so how can I help to fix this issue?

Userspace has nothing to do with hardware features. I don't know what is the case for A20, but for many others, OTG functionality is driven with overlays. If there are no overlays, you need to edit device tree and change its role. If that doesn't help, it is more complex problem. More complex, perhaps days / weeks to debug and fix. Most of (Armbian) kernel developers are long gone from this 10+ years old platform and users can't help. Also look into previous builds. Finding out when this broke is half of the solution https://fi.mirror.armbian.de/oldarchive/ or by finding a kernel that works https://docs.armbian.com/User-Guide_Armbian-Config/System/#alternative-kernels With any userspace (trixie/noble/jammy ...) Probably all A10 and A20 boards share this problem.

@shexplorer Control +c should have worked after: U-Boot SPL board init U-Boot SPL 2017.09_armbian-2017.09-S93fe-Pe5fd-Hbdb5-Va5b2-Bbf55-R448a (Nov 06 2025 - 16:35:49) SPL Hotkey: ctrl+c Make sure that USB TX is well connected to RX and try to spam it. Or use another terminal emulator, like putty instead of screen on a bash terminal. Maybe control is being intercepted.

I think it depends on what you want. If you want to have some fun, then building this one is interesting actually, and there is more extensibility, and since radxa zero GPIO pin is compatible with Raspberry pi's, you can also get a DAC Mini Hat raspberry pi module, so there is more you can play or customize. But, if you just want to solve the problem and don't want to have these hassle, buying an existing product is a better option, so you have the warranty, customer support, and everything should work out of the box. I don't have Fosi Audio DS1 or Fiio Ka13, so every information I get is from the google search and cannot guarantee the correctness. From what I saw, Fiio Ka13 seems to be unable to work with PS5, and Fosi Audio DS1 can. This project only handles digital audio data, so I do not need to pay attention to the audio electronic properties when outputting (because that's the job of that USB speaker), and I do not know the sound quality of Fosi Audio DS1. One last word, if your original plan is to use this converter to connect to Hiby R3II, then to your headphone, that should work, but that is kind of redundant; there is more latency introduced, and the robustness could be wore because you have a longer output chain (from the engineering perspective). It would be easier to just get a high quality UAC 1.0 Amp.

Tried this?

What exact image are you running? Or better yet providing full logs with armbianmonitor -u

I installed Waydroid on an Amlogic Meson GXM (S912) TV box. The SOC has a Mali-T820 GPU, and the box has 2 GB of RAM and 16 GB of eMMC. This was easy to do and Waydroid worked, but it was very slow, even before it heated the SOC to 80°C, which is probably its throttling limit. I removed Waydroid because it was too slow. I wasn't trying anything demanding. Even navigating Android Settings was ridiculously slow. This is a bit surprising because the hardware was designed for running Android. I was not running much else, just Wayfire and one or two Alacritty consoles. I don't think I was running out of memory. Is it possible to get decent Waydroid performance on other arm64 hardware?