Active threads

@usual user In essence, I'm not waiting for someone to do the work for me. Realistically, if I knew exactly how to do it, I would have done it and described it here. If I make something that could be useful for someone or the community, I share it. I rarely write because in most cases I use standard things and there's not much to write about, or I use quite non-standard solutions that for most people aren't solutions.

http://blog.armbian.com/content/images/2025/12/githubhighlights-2.pngThis week in Armbian development saw a series of refinements and maintenance updates across the build and configuration repositories. Contributors focused on workflow standardization, cosmetic improvements such as board name adjustments, and documentation enhancements. Several technical fixes addressed typos, property mispellings, and package issues, while platform support was expanded with kernel and boot improvements for devices like the Mekotronics R58-4x4 and MusePi Pro. Notable changes also included vendor reorganization and the addition of fallback logic for Ubuntu LTS releases. Overall, the activity reflects ongoing efforts to streamline processes and bolster hardware compatibility. Adjusting board names - cosmetic issue. by @igorpecovnik in armbian/build#9116chore: cleanup mirror_to_codeberg.yml workflow. by @igorpecovnik in armbian/build#9133chore: standardize workflow names. by @igorpecovnik in armbian/build#9130chore: update copyright years to 2026. by @igorpecovnik in armbian/build#9129Create mirror_to_codeberg.yml. by @EvilOlaf in armbian/build#9131docs: improve README and add Armbian Imager promotion. by @igorpecovnik in armbian/build#9128dts: orangepi-4-lts: fix mispelled disable properites. by @EvilOlaf in armbian/build#9123Fix dialog typo. by @SergeantSerk in armbian/configng#716fix(apt-utils): add fallback for Ubuntu LTS releases without -updates suffix in JSON. by @adeepn in armbian/build#9117fix(rootfs): unset GIT_FIXED_WORKDIR after debootstrap/mmdebstrap clone. by @QwaSeeK in armbian/build#9132Genio: Change INSTALL_ARMBIAN_FIRMWARE to 'yes'. by @HeyMeco in armbian/build#9134gha: check-pr-pictures: allow declare -g BOARD_VENDOR=. by @rpardini in armbian/build#9142mekotronics-r58-4x4: enable edge branch with mainline kernel & u-boot. by @rpardini in armbian/build#9127Missing upstream package mousetweaks. by @igorpecovnik in armbian/build#9143Move boards with vendor intel_amd under generic vendor. by @igorpecovnik in armbian/build#9122SpacemiT: Fixup eMMC boot on the MusePi Pro "SPINOR". by @pyavitz in armbian/build#9141sunxi: backport A523/T527 related patches from 6.19-rc1 and #8831. by @EvilOlaf in armbian/build#9106View the full article

From what I hear, that could a long time coming for trixie and the a5e.

Greetings, H96 Max V56 developers, I got 1Gb Ethernet, basic WiFi6, and the full Bluetooth5.4 suite of capabilities from the new H96 hardware, running my 6.12.44 kernel, Home Assistant OS port. Thanks especially @WINEDS for the stellar foundation, and to @GmP for the final piece of the Bluetooth puzzle. GBEM 👽

A lot of things can go wrong, so depending on what goes wrong in a copy from SD to emmc, what steps would be needed to recover could differ. But flashing back to the original android firmware will generally always get you back to the starting point.

NanoPi R76S is supposed to have PHC hardware timestamp support with both ethernet interfaces. Unfortunately ethtool -T returns no hardware support. Would be great if PHC could be enabled in this nice box.

Hello - Very new to this all and trying to learn my way around. I have an OPi4a which I was previously using for octoprint, etc. Was able to get it going using OrangePi's provided Ubuntu22.04 Jammy image, but am needing to reconfigure and was interested in armbian as the official images from OrangePi can be hard to access at times (site seems to intermittently go down / time out?), and from what I've seen there's very limited support from the manufacturer. Anyways - for the uninitiated, what is the status of the image for the 4a? Seeing the most recent post - does the backport being merged mean that it is possible to build from armbian main? Which target board should be selected? I am not seeing an option for the 4a, or any with the T527 chip. Alternatively, the most recent image I'm seeing is from @JuanEsf - to get this to work do I just need to use something like balena and flash from URL? Very new to all this, any help is appreciated.

The x96q-v5-1 image support aic8800 wifi chip without modify anything from dtb. Follow this https://github.com/LYU4662/aic8800-sdio-linux-1.0, the AIC8800 and alternate based on AIC8800 will work!

Well, at this point, hard to say what's going on: I'm not sure what happened during my chroot sessions but it looks like / in now non crypted and the boot options were completely overridden by who know's what verbosity=1 bootlogo=false console=both extraargs=cma=256M overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-rock-5-itx.dtb rootdev=UUID=92f542d4-5a03-424e-b953-e711111186dc rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u And I can boot without having to luks decrypt. It is probably a side effect of what I mounted in the chroot (/run /sys, etc) but I did not know this was even possible and I would be interested in theories or possible explanations. Thanks to all of you, especially @IBV

Will you please give the detail step?I flash "Armbian 25.11.2 trixie" ,but I can't find any useful dtbo file.

How can you active spi support?I burn " 25.11.2" image,but I can't find any overlay of spi ,uart or i2c. This is my system status: cat /etc/os-release PRETTY_NAME="Armbian 25.11.2 trixie" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.2 ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 25.11.2 trixie" uname -a Linux Pi-s 6.12.58-current-rockchip64 #3 SMP PREEMPT Thu Nov 13 20:34:41 UTC 2025 aarch64 GNU/Linux ls /boot/dtb/rockchip/overlay/rk3308* /boot/dtb/rockchip/overlay/rk3308-b@1.3ghz.dtbo /boot/dtb/rockchip/overlay/rk3308-otg-host.dtbo /boot/dtb/rockchip/overlay/rk3308-bs@1.3ghz.dtbo /boot/dtb/rockchip/overlay/rk3308-s0-ext-antenna.dtbo /boot/dtb/rockchip/overlay/rk3308-bs.dtbo

moved to tvboxes

Post the UART log.

@Werner OK, since I have a few Duos (v1.0 and v1.1) I tried same Jammy with 6.1.63 kernel SD in each and let idle. The 1.1 with copper heatsink runs about 40C, the 1.1 with same aluminum heat sink runs around 45C. The v1.0 runs around 50C. So weird. I'll try latest build, but stress-ng causing thermal shutdowns worries me. I used to run decent loads on these little boards. Good thing is thermal shutdown works or it would burn up the board.

How can I force it to boot from SD though?

As a followup: hardware crypto is damn slow on the Ky / SpacemIt platform, at least for default LUKS block encryption with AES. This probably also affects the Banana Pi F3 image. With default sector-size of 512 byte, HW-AES is 5 times slower than SW-AES, while cryptsetup benchmark reports 5 times faster. Main reason: block size. With sector-size of 4096 LUKS is reasonable fast. Also there is leftover debug (cannot be switched off) and a small bugs in the driver that triggers SW crypto fallback after HW crypto succeeds. Patches: https://github.com/sven-ola/armbian-build/tree/orangepi-rv2/patch/kernel/ky-current Best // Sven-Ola

I do not use chatgpt Most of them are rubbish anwers

Here is ukrainian forum with Android for this box: https://legione.name/upload/?dir=Smart-TV-Box/Q1/ Any chance to find linux for the same box? Android tv box q1 v3.0 Allwinner H313 If someone will find working version, please share

Hello! It seems that there is some issue with the user files FTP server. The multitool image should be acessessible from: https://users.armbian.com/jock/web/rk322x/multitool/ But it is present in: https://users.armbian.com/users.armbian.com/jock/web/rk322x/multitool/

I now actually see after some more reading and checking other SoC's that the CPU's in the A733 must start the kernel at EL2. See also ARM reference doc: 102412_0103_01_en So also 5.x kernel should work if EL2 I think If the A733 has not implemented EL2 and EL3 as could be the case as suggested in ARM reference doc, no KVM. See chapter6: As it is Allwinner, I won't be surprised, but wait and see what Radxa will come up with.

Good afternoon. I'm trying to stream video to my orange pi zero 2w. I am using Gstreamer and while testing I saw that v4l2slh264dec fails. When using autosink, only a transparent window is shown and when using a specific sink, no window is opened. My intention is to take advantage of the VPU with Gstreamer but that failure has caused me headaches. I tried using MVP and it works fine but it's not what I need. Maybe I will choose other options for what I want to do but first I would like to ask here about the topic- Thank you very much to whoever takes the trouble to read this and thanks in advance to whoever responds ❤️ By.: Google Translate

Developing solutions and sharing by sending PR and/or using customize image script might be the way address those.

Hi, I'm new to this forum but I've been researching this topic for quite some time. I have a Mecool KM1 Deluxe with 4GB of RAM and 64GB of storage, and an Amlogic S905X3 chip. I wanted to install Armbian to use it as a Linux device, but I've tried several versions and it hasn't worked. Someone mentioned on this forum that installing CoreELEC would prevent Armbian from booting. I installed emuelec and it worked perfectly, but I haven't been able to run Armbian. Could this be the reason? Thanks.

I've been using my Helios64 nonstop since i got it in 2020 (and the Helios 4 since 2018). It's been great the whole time; does exactly what I want it to do, and now I've made it my sole Plex server to save power. My only problem is that the internal eMMC is now 100% full (thanks to Plex), and I can't work out how to move the install back to the SDCard (Linux noob...), which is my I'm here. I'm sad these guys had to shut down. This could have been a magnificent project

Hello, Here is a config file that works with linux-6.6.119 config-6.6.119 And a tarball here : https://drive.google.com/file/d/14EHPMT01-geYNflC2lqXNue4ZH25z-lA/view?usp=drive_link with a fresh built kernel. Two small patches are needed : one to activate the wifi/bluetooth card (in dtb file), another to add a delay in mwifiex_sdio.c What works : wifi, eth0 and eth1 cards I can't activate the bluetooth card with btmrvl_sdio (need to be investigate) If someone else can test this (@rolli_44 , @umiddelb ? ). Next : propose a patch to integrate this board in armbian ?