Active threads

Thanks @bschnei! It built successfully. -- Success: NTIM Processing has completed successfully! Finish time: 05/05/26 20:14:07 TBB Exiting...! No input file for TIMN is supplied Total number of images to process in file[0] - 3 0 Image at offset 00000000 is TIM_ATF.bin 1 Image at offset 00004000 is wtmi.bin 2 Image at offset 00015000 is boot-image.bin Total number of images 3 Built ebu-bootloader/trusted-firmware-a/build/a3700/release/flash-image.bin successfully

I have been using Proton 11 Arm64 for weeks. It has good compatibilities in general (some games I have tested still broke). However, I prefer Proton 11 (Box64), it gives better performance.

We understand the concern, and we appreciate the effort put into testing and documenting the issue. At the same time, it is important to understand the realities of the embedded Linux ecosystem. Armbian supports a very large combination of SoCs, vendor kernels, boot chains, and downstream modifications across several hundred boards. Security response and validation in this environment is significantly more complex than in standardized desktop/server distributions. Explained here: https://github.com/armbian/build/issues/6937#issuecomment-4366571379 This is not a matter of ignoring the issue, but of limited engineering resources, kernel fragmentation, and the high cost of validating fixes safely across multiple platforms. Project can only finance security from your contributions https://github.com/sponsors/armbian volonteers or sponsors. Until none is taking this seriously, there is little what existing team members can do. We already attempted mitigation work on one of the most widely used kernel branches: https://github.com/armbian/linux-rockchip/pull/475 but even targeted fixes require substantial testing effort and may (i am sure it will) introduce regressions on affected hardware families. Current resources barely sustain even our regular release and maintenance process: https://docs.armbian.com/Process_Release-Model/ For users who need receiving upstream fixes faster and are willing to accept a higher risk of regressions on hardware feature breakage, there is always an option to switch to rolling/daily builds, where fix may already be available: https://docs.armbian.com/User-Guide_Armbian-Config/System/#rolling Tradeoff between stability, validation cost, hardware compatibility, and update speed is unfortunately a sad reality of embedded Linux maintenance.

@jock It looks like a known bug in the rk35xx u-boot code fixed by luckfox-lyra-ultra-yocto

@meco awesome - I see it's merged. how long does it take for a new image to be built?

Sorry I don't understand.

Background - I have a Helios64 NAS with 4 x HDDs running Armbian 25.11.2 with kernel 6.12.58. The HDDs each have a ZFS partition but the partitions aren't imported. The OS is running from an sd card and logging is to ram. Power management and spin-down on the HDDs is disabled. Despite all this *something* is causing the heads to move every second or two. iotop shows no disk activity . lsof +d /mnt/sda etc. shows no open files and fatrace shows files in /usr and /var but nothing on /dev/sda etc. So, whilst it doesn't look as if any files are being accessed the HDDs are still doing something. The question is WHAT and how do I stop it ? Any ideas ?

Another interesting thing is that snd_usb_audio is not loaded as a module and seems to be compiled. I tried in /boot/armbianEnv.tx in extrargs= put snd_usb_audio.index=0 but that didn't work either, unless a different name should be provided instead of snd_usb_audio.

Well, with the new image there was some progress, but I will give up for now. I will look for an SD card and try again using it. I’m confident that I will finally succeed in this operation.

@Maberikku Great! @humanus Nick said you hit a kernel error on 6.6. Can you paste the details here.

Boot on a from scratch helios64 sdcard image, cross fingers and copy / rename / replace original dtb file with ebin-dev file or mount sdcard with scratch helios64 on another computer, do the change, then boot with you ready sdcard on the helios64

Hi SymbiosisSystems, here: But I think you find it 😉

Had to debootstrap trixie because depmod version mismatch. Wifi 2.4 + 5 GHz + BT headphones, keyboards all work. USB is still stuck in plain charge, no micro SD. According to Gemini 3.1 Pro which I have been using, Imagination Technologies (PowerVR) BXM-4-64 MC1 would need 6.12.x kernel or newer which I have not been able to boot yet. This actually feels a bit faster than the Teclast Android even though without accel youtubes playback is quite slow. Battery life probably 5+ hours. aliexpress.com/item/1005009649297050.html keyboard + touchpad I have is a bit shady miss-clicks a bit once in a while. Might have to AI haxor some software filter to get it behave a bit better but that should not be that big of a deal. I have kind of already made up my mind, this ain't going to boot Android anymore, have to see if I grab another one at some point.

A complete breakdown of Mesa’s NIR compiler detailing how it optimizes shader memory access with SSA promotion, deref analysis, copy propagation, and store elimination to reduce memory traffic and improve GPU performance. View the full article

Just a small note here - I recently added Bianbu desktop (can be installed from armbian-config), where acceleration works on K1 based Musebook (legacy kernel). This should be possible to adopt to any other K1 board. Youtube video works fine in Chromium ...

Ubuntu 26.04 with or without KDE Plasma with working drivers for WiFi, GPU, Nic, Bluetooth. Enjoy! https://github.com/mack42/OrangePi5Pro Note: There are Minimal and Graphical images available. It also supports installing to the NVME.

Thank you very much for your responses, it totally make sense. I will try to build it myself, tho I have never done that, and my knowledge is very limited. I'd love to help one day, but this really is beyond what I can offer, for now.

Well if you want to live on the edge, then use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } egde as branch instead of code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } current

I have also encountered this using Orange pi 5 and latest Armbian updated as of today. That the "standing" USB port does not work also means that the USB-C port doesn't work -- they are electrically connected. So Mitu's question is also mine: Is this a limitation of the mainstream kernel (6.18.x) - i.e. does this work only with the vendor kernel (6.1.x)? EDIT: typo

Update: sicXnull/armbian-build (H96q) + "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" and "secure-boot.patch" solved the problem. Now, the ethernet interface is fully functional. Thank you Nick & sicXnull.

Has anyone found a working gpiolib implementation for Armbian on Orange Pi 5? I'm aware of wiringPi and it sort of works. However, being able to use the "real stuff" so to speak would make my life easier.

moved to staging

Collabora brought Bluetooth Auracast broadcasting to MediaTek Genio 700 for Embedded World 2026. Here's the complete, fully Open Source setup featuring Debian, BlueZ, PipeWire, with all the code and configs from our live booth demo. View the full article

I am not using WOL on any of my devices, I have no personal experience with the software on the Helios or any other platform.