Active threads

I do not know how to fix that key / verify signature issue. It might be there because of earlier diskfull. I only know I needed new keyrings, listed in the armbian list files when I dud the in-place upgrade from bookworm to trixie. There is aformal method for that, might be here on forum. I however did copy various things from a new Armbian Trixie image. E.g. new file is now: -rw-rw-r-- 1 root root 2297 Aug 31 22:15 /usr/share/keyrings/armbian-archive-keyring.gpg ~# sha256sum /usr/share/keyrings/armbian-archive-keyring.gpg 9d0ab1676008004f1ee0bfc0f99a6043544d8bb6df3d949f9bd30066246f9095 /usr/share/keyrings/armbian-archive-keyring.gpg For Docker problem: I don't use Docker, I have no clue why that file keeps growing.

From my experience with trunk 130 the gmac is working on both ports. Wifi is not always working, sometimes a reboot may make the wifi to work. There is no USB 3.0 and HDMI is not working either. Running gdisk armbian.img made it bootable. The easiest way to run this command for me was from WSL.

After having this happen again and investigating further, it looks like my container for transmission is writing to a log file that is just ballooning bigger and bigger until the system crashes. root@modron:/var/lib/docker/containers/899f42253bb7772351219b7a65ff21347455f11950f983fb7a8883c6b93cdb17# ls -al total 101656680 drwx--x--- 4 root root 4096 Dec 27 22:28 . drwx--x--- 22 root root 4096 Dec 27 22:28 .. -rw-r----- 1 root root 104095768576 Dec 31 15:08 899f42253bb7772351219b7a65ff21347455f11950f983fb7a8883c6b93cdb17-json.log drwx------ 2 root root 4096 Dec 27 22:28 checkpoints -rw------- 1 root root 5949 Dec 27 22:28 config.v2.json -rw------- 1 root root 1776 Dec 27 22:28 hostconfig.json -rw-r--r-- 1 root root 13 Dec 27 22:28 hostname -rw-r--r-- 1 root root 172 Dec 27 22:28 hosts drwx--x--- 2 root root 4096 Dec 27 22:28 mounts -rw-r--r-- 1 root root 336 Dec 27 22:28 resolv.conf -rw-r--r-- 1 root root 71 Dec 27 22:28 resolv.conf.hash I'm not sure what this file is. Tailing it prints this out, and I'm worried trying to load it into memory with less would cause a crash: {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.854663511Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.854793008Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855042376Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855144456Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855165456Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855213288Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855254412Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855304285Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12-31T20:06:58.855320618Z"} {"log":"[warn] Error from accept() call: No file descriptors available\n","stream":"stderr","time":"2025-12- I've been running the 4.0.5 branch of the linuxserver.io container for transmission, I'm updating to their "latest" branch and seeing if that improves anything.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (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 ~60fps@720p Need For Speed Most Wanted

https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first/#comment-199170

I have the following (maybe stupid) question, what needs to be done to be able to use all the features of the RK3588 by adding the dts file. Example: there used to be /dev/tpm0 which has been missing for several versions. As I said earlier, the latest dts is much shorter. My question is not an attempt to nitpick, but a serious question. And what can I help with. As in my case, there is a peculiarity. I have a FriendlyElec NanoPC-T6 and it is used in "production" in my network. And I do not have the opportunity to reinstall it. I would like to make a dts file that allows using the full functionality of the RK3588. Again, I want to say, I do not want to blame anyone or nitpick, but to find a solution, and whether I can help with anything and if Yes, how and with what. P.S. Since today is the 31st, if you want we can postpone the discussion until January 1st or 2nd

Hello SteeMan, Thank you I am going to look for a usb a to usb a cable Maybe ik can make one myself Happy New Year 🎉🎉🎉

I have an old MXQ Pro 4K (based on the original S905, not S905X or S905D, the original S905) which I tried to install armbian on, but I didn't know extra things were needed to set up uboot and dtb correctly, so I just flashed the image, put the SD card in my box, ran `reboot update` from Android to boot to the SD card, it showed the MXQ Pro logo, rebooted, went back to the MXQ Pro logo, and I can't get it to go past that. My box has a weird firmware issue (started immediately after a firmware restore so I don't think it's hardware damage) where the button in the headphone jack just... doesn't work, even when holding it, it still tries to boot to the eMMC, and now I have no way of getting back into Android, and I can't boot from the SD card due to the button not working, so, is there any hope for my box here? Or have I effectively hard bricked it? I don't have a USB-A to USB-A cable for USB burning tool, and I will not be purchasing one, this was a spare box I've had laying around for eons and I don't think it's worth spending any money on -- I could probably get a much better box for the same money.

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

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 👽

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.