All Activity

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.

Hi folks, long time lurker here. My helios64 is pretty much brand new, didn’t really needed it at that time, only bought it as I found it really cool. I may power it a couple of times per year for some backups (got 3x 6tb in it, no raid so I can take them out when needed, also back up stuff to external drives), it still starts-up from the initial sd card as I never finished setting it up. I also have a 1 bay separate NAS for downloading movies that if fails, I will just replace; and a drive attached directly to my router for easy file swaps; so don’t need much running 24x7. While I work in IT (on the Windows side, so the Armbian stuff is still a learning path for me), the last years have been so busy that I can’t find myself tinkering anymore at the end of the day. To the ones of you that are running one, does it still make sense, or should I maybe switch to something more mainstream? Thank you!

Thank you, I will test v25.11.1 Noble as soon as the page at the URL has been updated (it has not been updated yet).

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

The mesa 25.3 is imported into Debian, but that version is currently blocked for migration from experimental to unstable by a policy issue. So it will not be available anytime soon in regular versions of Debian (Trixie/stable 25.0.x, Forky/testing 25.2.x, Sid/unstable 25.2.x). To run mesa 25.3 with Debian you'll have to install mesa using source-packages.

Strange. Well, I tested recently released v25.11.1 images https://www.armbian.com/nanopi-m4-v2/ and they boot (Noble Gnome). I won't be testing older images. (image upload still working in this moment - will take an hour or so to appear on /dl pages) @GuestWho

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!

I tested v25.11.1 https://www.armbian.com/orangepi-5/ released yesterday - vendor kernel, Gnome desktop, acceleration works, 4k video playing with Chromium, audio works ... Since I don't have model + right on hand, i didn't test it. But its very similar board and I assume it works. It should even boot with image for normal Opi 5 but all peripherals won't be working correctly.

I'm having the same problem with an official 25.8.2 / 6.1.115. It's a new build, jumping to today's 25.11.1 / 6.12.58 to see if it changes.

I purchased the device after reading your thread and am currently porting it to my hardware with Copilot (Claude Sonnet 4.5). You can refer to my work results in the repository below. So far, the following parts have been confirmed to work: HDMI (no need to reconnect after Linux kernel boot) Ethernet Built-in eMMC Currently working on: Wi-Fi / Bluetooth (in my case, the model uses AIC8800D80) Not yet verified: GPU Install to eMMC As suggested in your thread, I based my work on the Hinlink HT2 and Radxa Rock 2F, using the DTB extracted from my device’s firmware and processing it with Copilot. I’d appreciate it if you could take a look if you’re interested. IMG_1597.HEIC https://github.com/wwwhana/armbian-build

> if that minimal package were part of the stock system, so the armbian-install doesn't break did your system break following the f2fs-tools install or were you able to format with f2fs and install your system in armbian-config?

you can try: sudo systemctl status rpcbind if there are any problems or it's not enabled try: sudo systemctl enable rpcbind sudo systemctl start rpcbind

Tried to get it running on the Rock PI S, which has the same chip, but it somehow doesn't seem to work... I think it has different conflicts maybe? It's kinda hard to debug. Originally I used the following (on 24.*): /dts-v1/; /plugin/; / { compatible = "rockchip,rk3308"; fragment@0 { target = <&spi1>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; spidev@0 { compatible = "rockchip,spidev"; status = "okay"; reg = <0>; spi-max-frequency = <10000000>; }; }; }; }; But it stopped working on upgrade to 25.11. I was able to get it to load again until I adjusted the compatible field to "armbian,spi-dev". But the the connected chip just wouldn't answer. I now tried rk3308-spi1-spidev.dts from this thread, with the codec modification and then even tried to fix the correct conflicts for the Rock PI S' different pinout: /dts-v1/; /plugin/; /{ metadata { title = "Enable spidev on SPI1"; compatible = "radxa,rockpis", "radxa,rock-s0"; category = "misc"; exclusive = "GPIO2_B1", "GPIO2_A4", "GPIO2_A5", "GPIO2_A7"; description = "Enable spidev on SPI1."; }; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; pinctrl-names = "default"; pinctrl-0 = <&spi1_clk &spi1_csn0 &spi1_miso &spi1_mosi>; #address-cells = <1>; #size-cells = <0>; spidev@0 { compatible = "rockchip,spidev", "armbian,spi-dev"; reg = <0>; spi-max-frequency = <10000000>; }; }; }; fragment@1 { target = <&i2c3>; __overlay__ { status = "disabled"; }; }; fragment@2 { target = <&uart3>; __overlay__ { status = "disabled"; }; }; }; But it still doesn't communicate. It's there, but not receiving any data from my chip like it did in the past. I can't find anything in dmesg, so I'm not sure how one can find out what's wrong with it.

Hello people! I have a NAS on my local network. I want to use its NFS share in Armbian Just like I do with the Debian x86 desktop. (I want to say that the NAS is configured correctly). However, I had some problems with armbian. I followed the general NFS instructions for debian. but it didn't work. I followed the instructions for armbian. I created a directory for the mount point. I copied the fstab line from my desktop, where it is known to be correct and working properly. 192.168.xx.x:/d8/d8 /mnt/d8-nas nfs relatime,nfsvers=3 0 0 I've tried issuing commands from the command line. mount -vvvvv -t nfs -o vers=3 192.168.xx.x:/d8/d8 /mnt/d8-nas mount -vvvvv -t nfs -o vers=4 192.168.xx.x:/d8/d8 /mnt/d8-nas The result is nothing. What a mystery "No such device"? I have another rockchip 3228 box with an older armbian 23.11 kernel, and nfs doesn't work there either. And I tried some different builds of 24.5 24.11 25.5. I couldn't get the nfs client to work on any of them. Can you tell me how to solve this quest?

We don't have resources to deal with this question, but I think, in case of this hardware, there is just firmware package (armbian-firmware / linux-firmware) that fits into this. Perhaps some other util. There must be some scripts to scan Debian packages and tell? From my head, I remember iozon3 package (might not be by default on minimal) that is non-free https://packages.debian.org/bookworm/iozone3

Great reply , I'll knock up a connection! much easier than anything else. I work in modern/future vehicles so the spikes and dips are not an issue for me as none of them have engines.

@Hqnicolas thanks for your presentation. I found I made an error : mkdir -p ./build/userpatches/kernel/archive/rockchip64-6.12 should be : mkdir -p ./userpatches/kernel/archive/rockchip64-6.12 as the current directory is build at that point. For wsl installation @NicoD made a great video here :

rk3326 and rk3328 are not the same thing, neither is px30. Definitely no chances to run this on those SoCs; I don't know if there are images for boards using px30/rk3326 in armbian.