Active threads

I would try an "edge" image, but I cannot see any: https://www.armbian.com/orangepi-5/ Only "vendor" and "current" images are listed. Is there a specific page to look for edge-type images? Thanks Fernando

As far as I can tell, Armbian does not support the OrangePi RV2. Where did you get the image from? Or are you really talking about the PC2? RISC or ARM? Big difference.

authelia is not a Debian or Ubuntu package. I'd recommend you complain to whoever you got the package from, I guess. It's the first time the symlink has become an issue as far as I can recall.

Hi, I have a TV box with an RK322x chip. I want to use FFmpeg and process video using FFmpeg hardware decoding. Please tell me: do I need to recompile the system/distro build, or does it work out of the box right now? If not, which distribution is better to choose? Please tell me.

Yes, but packages hasn't been pushed out yet. We need to test and possibly fix last problems on images. In 10-14 days.

Thank you Avenom! I've paused my project. I'm even undecided about continuing to use the Orange Pi Zero 2W. As soon as I find a little more patience, I'll try your suggestion. Thanks again for your post.

Hi, Thanks for sharing details about the Armbian on x88 Pro and your DIY Cooling Solution. Really useful. May I know what is the name of the image that you have used for this setup from https://www.armbian.com/station-m2/. I tried the recent and archived images. Post burning to SD card, the box is not booting with any of the image.

Hello team, I encountered a dependency conflict while trying to upgrade the package armbian-bsp-cli-panther-x2-current to version 25.8.2. The issue seems to be a mismatch in the required version of base-files. Here's a summary of the issue: Attempted upgrade command: apt install armbian-bsp-cli-panther-x2-current Error message: armbian-bsp-cli-panther-x2-current : Depends: base-files (>= 25.8.2) but 25.8.1-12.4+deb12u11-bookworm is to be installed Currently installed version of base-files: base-files: 25.8.1-12.4+deb12u11-bookworm (installed) Available versions for base-files from the repository (apt policy base-files): Installed: 25.8.1-12.4+deb12u11-bookworm Candidate: 25.8.1-12.4+deb12u11-bookworm Version table: 25.8.1-12.4+deb12u11-bookworm 500 25.5.1-12.4+deb12u11-bookworm 500 ... It appears that the repository ( http://apt.armbian.com/pool/bookworm-utils/b/base-files ) does not provide the required version of base-files (25.8.2) for the arm64 architecture. Only the armhf architecture package is available, but armbian-bsp-cli-panther-x2-current depends on the arm64 version. Could you please help investigate the issue or confirm whether the repository will be updated to include version 25.8.2 of base-files? Thank you for your support!

@WINEDS@Hqnicolas Thank you for your help. I will try to see if it can work properly，

Don't use etcher. https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

Armbian 25.8.1 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 25.3 (https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.19-staging-tkg-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.19) + DXVK-sarek-stripped v1.11.0 (https://github.com/pythonlover02/DXVK-Sarek/actions) ~60fps@1080p Cat Quest II

i use a usb to 3.5mm headphone adapter.

Problem is in Balena decompression of xz files. Use USB imager or something else (or 2 years old version of Balena). It will work. We filed bug when it was discovered, but it was not fixed by this day. We can't fix this app for them ... BTW. Its all here: https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

Thanks for the tips. The following overlay works on a c2 /dts-v1/; / { compatible = "amlogic,meson-gxbb"; fragment@0 { target-path = "/aliases"; __overlay__ { i2cA = "/soc/bus@c1100000/i2c@8500"; }; }; fragment@1 { target-path = "/soc/bus@c1100000/i2c@8500"; __overlay__ { #address-cells = <1>; #size-cells = <0>; pcf8563: rtc@51 { compatible = "nxp,pcf8563"; reg = <0x51>; status = "okay"; }; }; }; };

Turns out the secret was getting the address and symbols right in the device tree. I create the following as meson-pcf8563.dts, compiled into meson-pcf8563.dtbo, moved to /boot/dtb/amlogic/overlay, and added pcf8563 to the "overlays" line in armbianEnv.txt. /dts-v1/; / { compatible = "amlogic,meson-gxbb"; fragment@0 { target-path = "/aliases"; __overlay__ { i2cA = "/soc/bus@c1100000/i2c@8500"; }; }; fragment@1 { target-path = "/soc/bus@c1100000/i2c@8500"; __overlay__ { #address-cells = <1>; #size-cells = <0>; pcf8563: rtc@51 { compatible = "nxp,pcf8563"; reg = <0x51>; status = "okay"; }; }; }; };

It is now.

Hi, In 2025, Helios64 is now stable for me and for my brother, who also uses it. The only thing to do is, just after installation or after any upgrade, you must reinstall the special file rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp because I think the specific tuning in this file is not included in the official image. For me, I suggest keeping it, using it, and saving your money for other things. Bye.

should be fixed with https://github.com/armbian/build/pull/8980

Good day all, After compiling a build for my TV box and burn it to the SD boot process stuck to Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems Can someone help please solving the problem?

I switched to the Armbian version of Debian Triexie and now it's OK

I was just about to rebuild the source package, but today's upgrade delivered everything turnkey since my development team was faster and had done everything for me. The previously referenced description does provide a working result, but it does not use the most current available releases. This script runs the NPU with the latest working releases: #!/bin/bash WORKBENCH="." python3.11 -m venv ${WORKBENCH}/python/3.11 source ${WORKBENCH}/python/3.11/bin/activate pip install numpy==1.26.4 pip install pillow==12.0.0 pip install tflite-runtime==2.14.0 TEFLON_DEBUG=verbose ETNA_MESA_DEBUG=ml_dbgs python ${WORKBENCH}/classification.py \ -i ${WORKBENCH}/grace_hopper.bmp \ -m ${WORKBENCH}/mobilenet_v1_1_224_quant.tflite \ -l ${WORKBENCH}/labels_mobilenet_quant_v1_224.txt \ -e /usr/lib64/libteflon.so deactivate classification-3.11.log

I saw that the photos were deleted by mistake, so I added them back. Here is a photo of the two cases: Here is a photo of the motherboards of both cases: Here is a photo of the X96Q-Armbian-H313 V4.0 boot screen: Here is a photo of the X96Q-Armbian-H313 V4.1 boot screen:

RPCbind enabled and running.

Bad News: same issue with 25.11.1 / 6.12.58, and a few others... Worse News: The issue affects all rk3588's (Orange Pi 5/5B/5+, Rock 5A/5B/5C, etc.). Good News: PR is a permanent fix for all images, and also identifies an immediate workaround that only requires a reboot (add "overlays=panthor-gpu" to /boot/armbianEnv.txt). https://github.com/armbian/build/pull/8979

Hello, I'm from China. I bought an H96 Max M9S (8GB+128GB) for 500 RMB. After reading your discussions, I've learned how to use RKDevTool to flash the Android system via USB. However, I've been struggling for several days and still cannot boot the Armbian system. Could you please tell me how to boot Armbian? Is it possible to flash the Armbian system directly to the eMMC of my M9S using RKDevTool? I really need your help. Thank you very much!