Active threads

All are interested. However, H3, H5 and H6 boards will receive additional fixing to DVFS during this week. After that, I will rebuild them, but those are all CSC, so there are additional tasks: We only generate and test boards with at least "standard support", where a known maintainer is around. If you (or someone else) step up as a maintainer: https://docs.armbian.com/User-Guide_Board-Support-Rules/ following by PR as such https://github.com/armbian/build/pull/8981 boards will automatically be added to automatically generated build lists https://github.armbian.com/release-targets/targets-release-standard-support.yaml and images can be (auto) generated: https://docs.armbian.com/Process_CI/#automation-for-developers-and-maintainers If you wanna cover those steps, report status at release periods, step up. In most cases, boards work but during those tests we usually always found something to fix. And boot loader compilation is checked this way - end user upgrades don't upgrade that by default so you could be running a board for years while freshly build images would have borked uboot ... Perfect - new use case: Armbian QA

Great! It's working now, sorry, I made it too complex previously.

Can you see this post? Please write at least a letter.

Collabora continues to be a key contributor to the Linux kernel, with 125 patches from 21 developers! Highlights include Arm Mali GPU improvements, expanded MediaTek and Rockchip SoC support, Rust integration progress, and new Rockchip video capture functionality. View the full article

@maxsub no, its hacked. At least from my side. For us, that GPU stuff is closed, patented, tighly licensed and so on. LG // Sven-Ola

@Nick A Yes, I used the MT7601U for a few days, but I wasn’t really satisfied with it. So, with the help of AI, I decided to port the SV6256P anyway—and to my surprise, it actually worked.

I've made some improvements of .dts for H96 MAX M9S, tested on Linux version 6.19.0-edge-rockchip64 (build@armbian) What's new: GPU working USB 3.0 mode working Currently working: both USB ports, incl. USB 3.0 mode GPU (using Panfrost driver) HDMI (audio+video) Ethernet port Wifi (using aic8800 DKMS drivers provided by https://github.com/radxa-pkg/aic8800/releases) Leds Not working: NPU Bluetooth S/PDIF rk3576-evb1-v10-main-h96-v5.dts dmesg-19.0.txt

armbian-config submenu STO001

Hello friends, in general, a friend gave me an x96q TV set-top box, I want to install armbian on it and then install klipper and use it on my 3d printer, I'm not good at this, maybe someone can help

Yeah, don't do that.. At least read "<application> --help" before doing sensitive stuff like that if you are unfamiliar. If that happened to you, and that is the reason you typed that.. For future reference: If you have a root account, you can change to root user with "su root" and enter passwd. You are then root and can add your user back to the groups needed. Or you can use the debian "child safe" way, "adduser <user> <group>" (only works on already existing users and groups) instead of usermod to begin with. But best is you learn usermod, since that will let you utilize that knowledge on pretty much any unix system.

@marcosdsdba

Lately, I've been playing around a bit with computer vision detection. I managed to patch together a PoC script with which I conducted some tests. The results are quite promising. The frame rate is just based on the round trip time of my test script, so it only roughly reflects the inference time. The throughput includes all additional overhead but is sufficiently informative for a relative comparison. Inference on a single CPU core delivers an image throughput of about 4 images: Inference on a single NPU core delivers an image throughput of about 17 images: Inference on eight CPU cores delivers an image throughput of about 21 images. But all eight cores run over 80% during this, and after a short time the fan kicks in. The headroom is also quite limited, for e.g., to perform other tasks concurrently. Running several similar inference tasks concurrently immediately results in a proportional drop in frame rate per task. When six similar inference tasks are executed simultaneously with NPU delegates, they are distributed across the three available NPU cores, and the SoC utilization is moderate enough that the fan doesn't even turn on. The throughput does not degrade and the CPU cores remain available for other tasks as well: For my tests, I used a random video clip. For the inference, I used a model pre-trained with the COCO dataset. With its 4.1MB memory size and its 80 object classes, it delivers surprisingly good results. Using the NPU hardware not only reduces the load on the CPU cores but also provides additional acceleration of processing. But the best part is that only current mainline code is required for use. No dependencies on proprietary implementations or outdated software stacks. It just works out-of-the-box, you just need to know how to use it.

This morning, the difference is not as big as yesterday, but it is still there. Why isn't it synchronized via NTP? sudo date -s “2026-02-10 04:13:00” Tue, Feb 10, 04:13:00 CET 2026 root@cubietruck ~ > date Tue, Feb 10, 06:11:41 CET 2026

I installed Filebrowser via armbian-config but it didn't work. The container was restarting and there was: Using database: /database/filebrowser.db Error: open /database/filebrowser.db: permission denied in the .log file. The developers of Filebrowser explained they introduced some breaking changes and documented the changes that have to be made to avoid that error: - User: File Browser no longer runs as root, but as user with PID 1000 and GID 1000. You can still change this by using Docker's --user flag [https://www.docker.com/blog/understanding-the-docker-user-instruction/]. - Volumes: the volumes with the database and configuration are now aligned with the s6-overlay images. Instead of mounting the files themselves, which leads to frequent issues, you now mount the surrounding directory. Unfortunately, these are breaking changes and will require updates on your side. Assuming you have a database.db, a .filebrowser.json and the data in /data, do the following: 1. Change the path of database in .filebrowser.json to /database/filebrowser.db 2. Rename database.db to filebrowser.db 3. Rename .filebrowser.json to settings.json 4. Put them in the same directory locally, let's say /app/filebrowser/ 5. Change the permissions of both directories: sudo chown -R 1000:1000 /app/filebrowser /data 6. Mount with the flags -v /app/filebrowser:/database -v /app/filebrowser:/config - you can also choose to put them in separate directories, but it is not needed. If you are still getting errors, please make sure that the paths/volumes you are mounting have read-write permission for user 1000:1000. For more up to date information regarding how you should use the Docker image, check filebrowser.org/installation.html#docker [https://filebrowser.org/installation.html#docker] But how exactly to apply those changes after the container already has been created and started via armbian-config?

http://blog.armbian.com/content/images/2026/02/githubhighlights-2-1.webpThis week in Armbian development saw significant advancements across kernel, firmware, and build targets. The release of 6.18.y kernel UEFI images marks a major update, alongside expanded desktop build options including Cinnamon and KDE Neon for UEFI systems. Notable board support enhancements include the addition of custom build targets for Amlogic TV Boxes, the Raspberry Pi Zero 2W as a virtual board, and improved support for Orange Pi 3 LTS and Odroid M2 devices. Automation improvements streamline inventory rebuilds and board data management, while new features such as Armbian board auto-detection and browser enablement for Riscv64 boards enhance usability. Several bug fixes and configuration updates address issues across Hyper-V images, kernel configs, and u-boot versions. The changelog also highlights upgrades to wireless firmware, dependency management, and support for BTRFS on NanoPi R3S-LTS, reflecting ongoing efforts to broaden compatibility and stability. 6.18.y kernel UEFI images are out. by @igorpecovnik in armbian/armbian.github.io#221abl: feat: add extraargs from armbianEnv for mkbootimg. by @CodeChenL in armbian/build#9341Add -hyperv suffix to REDI_VARIANT for Hyper-V images. by @igorpecovnik in armbian/armbian.github.io#216Add Cinnamon and KDE Neon desktop builds for UEFI. by @igorpecovnik in armbian/armbian.github.io#209Add cloud image extensions to UEFI minimal targets. by @igorpecovnik in armbian/armbian.github.io#211Add custom build targets for Amlogic TV Boxes. by @SteeManMI in armbian/armbian.github.io#224Add ENABLE_EXTENSIONS to UEFI desktop targets. by @igorpecovnik in armbian/armbian.github.io#210Add KDE Neon and RISC-V XFCE desktop targets. by @igorpecovnik in armbian/armbian.github.io#214Add Raspberry Pi Zero 2W board as virtual board. by @igorpecovnik in armbian/armbian.github.io#223Add remote execution method for inventory rebuild. by @igorpecovnik in armbian/armbian.github.io#222Add REMOVE_EXTENSIONS blacklist support to generate_targets.py. by @igorpecovnik in armbian/armbian.github.io#217ath12k: Upgrade to WLAN.HMT.1.1.c5-00302-QCAHMTSWPL_V1.0_V2.0_SILICON…. by @kasimling in armbian/firmware#118Automation: when board data changes on push, execute inventory rebuild at armbian.github.io. by @igorpecovnik in armbian/build#9354BPI-M4-Zero / KickPi K2B: Update u-boot to v2026.01, ATF to lts-v2.12.9 and fixup the KickPi K2B linux DTS. by @pyavitz in armbian/build#9340Enable Browsers on two Riscv64 boards. by @igorpecovnik in armbian/armbian.github.io#219Extension: Bump Nvidia propriatery driver. by @igorpecovnik in armbian/build#9338feat: add Armbian board auto-detection and toast notification system. by @SuperKali in armbian/imager#91feat: add Dependabot configuration for dependency management. by @SuperKali in armbian/imager#70File was removed while it remained in series control file. . by @igorpecovnik in armbian/build#9339Fix errors in .editorconfig. by @iav in armbian/build#9363Fix file_extension extraction for Hyper-V cloud images. by @igorpecovnik in armbian/armbian.github.io#215Fix K3 issues - APT Caching, PB2, Missing KConfig. by @Grippy98 in armbian/build#9349KDE Neon: drop conflicting packages in order to assemble KDE desktop. by @igorpecovnik in armbian/build#9337kernel configs: disable unprivileged BPF. by @neheb in armbian/build#9082khadas-edge2: remove legacy uboot. by @efectn in armbian/build#9367Limit exposed.map to maximum 2 entries per board. by @igorpecovnik in armbian/armbian.github.io#220meson64: ressurect 6.12 as BRANCH=oldlts. by @rpardini in armbian/build#9350Odroid M2: Move main build target to CURRENT kernel branch. by @igorpecovnik in armbian/build#9357Odroid-M2: update uboot to v2025.10. by @mlegenovic in armbian/build#9359Orange Pi 3B: Update config. by @dust-7 in armbian/build#9370OrangePi 3 LTS: Add DTS and DEFCONFIG to u-boot v2026.01. by @pyavitz in armbian/build#9352OrangePi 3 LTS: Add ethernet support to u-boot defconfig. by @pyavitz in armbian/build#9365OrangePi 3 LTS: Fixup u-boot LED nodes. by @pyavitz in armbian/build#9358OrangePi 3 LTS: Update crust and u-boot defconfig. by @pyavitz in armbian/build#9372OrangePi 3 LTS: Use extlinux, remove aw859a-wifi.service, update current defconfig, etc.... by @pyavitz in armbian/build#9362Promoting Opi 3LTS and Odroid M2, demoting cubox-i and Jetson Nano. by @igorpecovnik in armbian/build#9353Radxa E52C: add mainline U-Boot support and kernel target configuration. by @okrc in armbian/build#9366radxa-e54c: board config: remove wayland-sessions-mask extension. by @schwar3kat in armbian/build#9351Refactor mesa-vpu extension: add architecture-specific browser selection. by @igorpecovnik in armbian/build#9347Remove Rockchip gpio patch, already applied upstream. by @tparys in armbian/build#9368Restore qemu performance fix for Ubuntu Noble. by @tparys in armbian/build#9371Restructured qcom/sm8550/ayn directory. by @Squishy123 in armbian/firmware#117Rock 5B Plus: Add GPIO names to edge dts. by @JohnTheCoolingFan in armbian/build#9348Support BTRFS on NanoPi R3S-LTS. by @clarkmcc in armbian/build#9343View the full article

See here:

The raised U-Boot version here is the culprit: https://github.com/armbian/build/commit/b8844c9 Maybe done by accident, since the commit/PR message does not mention the ZeroPi at all, or that it has been successfully tested on that board. Removing those two lines BOOTBRANCH="tag:v2025.04" BOOTPATCHDIR="v2025-sunxi" , reverting to U-Boot v2024.01 and respective patch dir, solves it for us. Of course, if someone finds time, it would be interesting to find out which missing patches or changes in upstream U-Boot are causing the issue. What I see in our logs is that the last starting and never finishing service is one which calls "udevadm settle", hence waits for udev rules to be processed, endlessly. The NanoPi NEO image boots on the board, but using the NanoPi NEO device tree on the ZeroPi image does not boot, which left only the bootloader as culprit. Maybe it puts some device into a bad state which causes the kernel/udev hang. Duplicate topic:

My recent RK3588 kernel adventure: - dual-core H.265 (HEVC) encoding working live at full 4K@60 on armbian-build edge kernel (6.19-rc8) for Rock 5B[+] and Orange Pi 5 Ultra. - fix for setting HDMIRX EDID (this didn't work in mainline on any of my tested hardware) This is out-of-tree (practical focus over upstream goals), but it's stable and producing clean bitstreams. Repo: https://github.com/rcawston/rockchip-rk3588-mainline-patches Feedback welcome.

@Almir Oliveira why are you looking for a build that is over three years old and includes a Linux kernal that is no longer supported? Why not download the latest build from the Armbian downloads page?

I don't see it specifically listed, but does Armbian run on the Beaglebone black?

Community support is fine for me, thanks for your job! Are there system packages I shouldn't upgrade with apt to not break OS in my case? Maybe kernel or hardware-specific tools...).

After digging into more details, I think Armbian has moved to use new U-Boot generated FIT image u-boot-rockchip-spi.bin for SPI boot, however, it doesn't work to boot NVMe rootfs and sometimes breaks the board and I have to erase SPI to get SD card booting. Couldn't find more information how Armbian does MTD boot now. Note that older vendor SPI bootloader can boot kernel 6.18.8 but I ran into other issue like freezing system for a couple of minutes so that I'd say to avoid use old MTD image with 26.2 6.18 kernel.

Have you tried the install instructions and build from here: https://www.armbian.com/amlogic-s9xx-tv-box/

On my Gentoo setup, I never had any USB issues before 6.6, even without the usbcore.autosuspend=-1 option. With 6.6, though, USB doesn’t work for me even with that option enabled. The fix from all2 worked for me, so thanks to that I put together what I think is a slightly more robust solution: