Igor

This 100% works - we are even running daily automated tests on Bookworm, Jammy and Noble.
https://github.com/armbian/os/actions/runs/15362508470/job/43232345405
 
Manual test on Rockchip64 (Bananapi M7) with 6.12.28-current, latest kernel from daily repository.

System: https://paste.armbian.com/tiwisuhugi
 
Here is build log:
 

And I have ruled out that this is Armbian OS problem.

https://github.com/armbian/build/pull/8334

Impossible.
 

This might help you: https://github.com/amazingfate/armbian-xiaomi-elish/wiki/Flashing-Guide

Yes, I know about it and I did it right after the update was finished. Maybe it was an isolated case. I did armbin-install again and test 30 reboot again and each one correctly indicated 1Gb RAM 🙂
 

Hi, I would like to share my recent work: a cheap USB Audio Class 1.0 (UAC) input to UAC 2.0 output converter.
 
For folks that may not understand why I have this crazy idea, here is the background:
For some shitty reasons, PS5 does not support outputting audio through certain USB sound card, and that is because PS5 only supports very old USB sound card (UAC 1.0), and usually high end speakers or sound cards would use newer, better UAC 2.0 protocol.
So, this shitty thing happens to me, when I thought my EDIFIER S880 speaker would be a plus for my gaming experience. EDIFIER S880 has a UAC 2.0 in input source, so my PS5 does not support that. So, what I can do is to use another 3.5 jack to connect the speaker to my PS5.
Unfortunately, there is a staticky buzz sound throughout this channel. What's even worse is that EDIFIER S880 has 6 input source selection, but I can only switch to the next source, wait for 2 seconds, and repeat this process 5 times every time I want to switch the audio from my computer to the PS5.
 
After lots of trials and flashing my custom kernel, I finally did it!
The idea is to use a board that has 1 USB otg port to act as a UAC 1.0 sound card, and has another 1 USB host port to connect to the UAC 2.0 speakers, then run programs on that board to redirect sound from USB otg port to USB host port. It is even a plus that the board consumes less power, so we do not need an extra or special power supply for it; this becomes crucial, especially when sharing the same USB connection with the USB otg port (SBC boards are more power-hungry these days!). The standard USB 2.0 protocol only allows 5V 0.5A to the device connected.
I actually built one with an Orange Pi One board, but it turns out that the CPU is not fast enough, and there are sound glitches sometimes.
 
With some research, I found this board that perfectly fits my needs: Radxa zero 3W. Here is the advantage:
- It is cheap, and the one I used is the nearly minimum SKU (1 GB ram with 8 GB onboard eMMC, they also have no onboard eMMC SKU).
- The otg port could handle USB PD protocol, meaning no special hacks are needed, you could get at most 30W of power, if needed (and turns out the normal USB 2.0 port on my PS5 works perfectly, so I guess it consumes less than 5V 1A = 5W)
- It is tiny.
 
However, things don't work right out of the box. At the beginning, I flashed the official, latest Radxa OS, modprobe the g_audio. It is running as a UAC 2.0 device, so it is not the one I want. As a result, I grabbed their kernel source, changed the config to UAC 1.0 gadget, and flashed onto the board, but there seems to be some issues in their kernel fork for UAC 1.0 driver: there was no /dev/snd/controlC0, so the g_audio failed to run.
As a result, I turned to use the Armbian build. This time, the /dev/snd/pcmC0D0c is missing, so g_audio failed to run again.
I then compiled my own kernel, flashed it onto the board. The Armbian build is with kernel 6.1, and the kernel I built is kernel 6.12, then the board failed to boot to the kernel due to U-Boot thought there were some errors.
Luckily, I found that building the whole Armbian image with kernel 6.12 can boot without issues, so I built a custom kernel 6.12 with UAC 1.0 enabled image, modeprobe the g_audio module, and it finally worked!
 
After that, I crafted a simple golang SystemV daemon for bootstrapping and terminating the alsaloop program for redirecting the sound, and used a udev rule to notify that daemon of the attachment/detachment of the USB speaker out event. The converter is finally working!
 
Here is the pre-built image for folks who want a quick test. It is based on the commit b27c86e620dcd9f55daadf52ccc85643dba2a381 from the armbian build repo with the following config modification:
diff --git a/config/kernel/linux-rockchip64-current.config b/config/kernel/linux-rockchip64-current.config index d053d0997..6e360bba7 100644 --- a/config/kernel/linux-rockchip64-current.config +++ b/config/kernel/linux-rockchip64-current.config @@ -3507,3 +3507,8 @@ CONFIG_RATIONAL_KUNIT_TEST=m CONFIG_MEMCPY_KUNIT_TEST=m CONFIG_TEST_MEMCAT_P=m CONFIG_MEMTEST=y + +CONFIG_USB_CONFIGFS_F_UAC1=y +CONFIG_USB_CONFIGFS_F_UAC2=n +CONFIG_USB_F_UAC2=n +CONFIG_GADGET_UAC1=y  
Currently, the "current" build does not detect the Wi-Fi interface, but as it does not affect the audio converting feature, I may not put too much effort into this.

@Stoven @jock
 
We were moving servers around and forgot about https://users.armbian.com
 
Fixed.

Indeed. Comparing sources between kernel 6.12 and 6.15, I could only spot one difference in the drm_atomic_helper_connector_hdmi_check() function so I have tested applying this via a patch and the build compiled successfully. Testing the build I found that reboot now works and shutdown finishes with just a blank display.
 
If it is indeed the same issue then this patch will likely fix the problem. Based on what I found it may impact certain Rockchip Socs also: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/display/drm_hdmi_state_helper.c?h=linux-6.15.y&id=0d337b40ca1e532af42516d9e9024baad466319a
 
drv-drm-atomic-helper-null-pointer-fix.patch
 
Thanks 
 
Ryzer

If nvme is correctly recognized code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install should do.

Recreated hdmi patches under kernels 6.12 and kernels 6.15 in pcduino-boards-fixes branch.  When attempting to build with current kernel 6.12.30, with drm patches for sun4i_hdmi_enc.c to use drm_hdmi_connector_mode_valid and drm_atomic_helper_connector_hdmi_check fails to compile. when just applying drm_atomic_helper_connector_hdmi_check patch build compilation is successful. Just need to verify this build works.
 
For kernel 6.15, with just the hdmi patches, we get a working HDMI display output:
 

@Igor, all
just like to say that I installed
 
Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.imgArmbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img
from the boards page
https://www.armbian.com/orange-pi-zero-3/
 
apt update works 'out of the box', no PUBKEY errors
 
thanks for the the updates
@vtech,
you may like to try the same for orange pi zero 2

What do you mean by that? Images that are currently available are still from 25.2 ... new will be created soon. But you can anyway update them standard way: apt update + apt upgrade.

What do you mean by that? Images that are currently available are still from 25.2 ... new will be created soon. But you can anyway update them standard way: apt update + apt upgrade.

I would suggest you to download clean Debian minimal image and proceed this way:
https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#home-assistant
 
EVCC can be installed this way - official Docker container:
https://docs.armbian.com/User-Guide_Armbian-Software/HomeAutomation/#evcc
 
 
How to deal with EVCC from HA, no idea. This is application level knowledge and I am just an average user of HA. I assume addon will want to connect to the service which runs on some IP address and some port. IMO this part is similar as official HAOS image.
 

Current application images are not yet rebuild with latest stable base, so until then its better going clean Debain + armbian-config way.

Introducing Armbian’s New Cloud Images: Optimized for x86 and aarch64 Cloud Deployments
Armbian is taking a significant step forward in cloud computing support with the introduction of dedicated cloud images tailored for cloud environments. The latest enhancement brings a new ‘cloud’ image set specifically designed to optimize generic x86 and aarch64 deployments, ensuring better performance, security, and compatibility in cloud infrastructures.
Why Dedicated Cloud Images?
As more enterprises and developers deploy lightweight Linux images in cloud environments, the need for a streamlined, cloud-optimized configuration has grown. The new ‘cloud’ images aim to address this by focusing on:
Very Fast Boot Time: Optimized configurations enable boot times as fast as 1-2 seconds, ensuring rapid deployment and responsiveness. No Firmware Package: By eliminating unnecessary firmware packages, the cloud images remain lightweight and focused on essential cloud functionality. Optimized Performance: Stripped of unnecessary hardware drivers, the cloud images are leaner, allowing faster boot times and improved efficiency. Enhanced Compatibility: Fine-tuned configurations ensure that Armbian-based cloud instances run seamlessly across major cloud providers, including AWS and Azure. Security-Focused Design: With a minimal attack surface, the cloud images reduce exposure to vulnerabilities while maintaining essential features. Lightweight Image Size: The uncompressed QCOW2 image is approximately 700MB, ensuring minimal resource usage while maintaining full functionality. Docker Support Enabled by Default: The cloud images come preconfigured with Docker support out of the box, allowing seamless deployment of containerized applications. Lean Debian Bookworm or Ubuntu Noble User Space: Provided images come with a minimal yet powerful user space based on Debian Bookworm or Ubuntu Noble, ensuring stability and efficiency. ZRAM Management: Built-in ZRAM management optimizes memory usage, improving performance in resource-constrained environments. Armbian-Config System Configuration Utility: The powerful armbian-config tool provides an easy way to configure and manage system settings, enhancing user experience and customization. Customize and Brand Your Cloud Image
Armbian makes it incredibly simple to create custom, cloud-optimized images tailored to your needs. Whether you’re an enterprise or an individual developer, you can brand and configure your Armbian cloud images to match your identity and requirements. Have always fresh Armbian OS with your brand!
By leveraging the Armbian build framework, you can easily build your own cloud images with custom configurations, packages, and branding. Get started today by visiting the official Armbian build repository.
Download links
You can find download links at https://www.armbian.com/download/, or use the direct links below.
For the QEMU disk image (QCOW2) format:
https://dl.armbian.com/uefi-x86/Bookworm_cloud_minimal-qcow2
https://dl.armbian.com/uefi-x86/Noble_cloud_minimal-qcow2
https://dl.armbian.com/uefi-arm64/Bookworm_cloud_minimal-qcow2
https://dl.armbian.com/uefi-arm64/Noble_cloud_minimal-qcow2
and Microsoft Azure image format:
https://dl.armbian.com/uefi-x86/Bookworm_cloud_minimal-hyperv
https://dl.armbian.com/uefi-x86/Noble_cloud_minimal-hyperv
https://dl.armbian.com/uefi-arm64/Bookworm_cloud_minimal-hyperv
https://dl.armbian.com/uefi-arm64/Noble_cloud_minimal-hyperv
How This Benefits Cloud Deployments
This update makes it easier for developers and businesses to deploy Armbian-based instances in the cloud without unnecessary bloat. Whether running on AWS, Google Cloud, Azure, or smaller providers and Qemu KVM / Proxmox, users can expect:
Reduced overhead and better resource utilization Improved stability with cloud-centric optimizations A more agile and lightweight system for containerized applications Faster provisioning and deployment due to the ultra-fast boot times Seamless container orchestration with pre-enabled Docker support Optimized memory management with built-in ZRAM support Customizable and user-friendly system configuration via armbian-config The ability to build fully customized, branded cloud images with ease What’s Next?
Armbian continues to evolve, ensuring that users benefit from its embedded Linux roots, embracing a philosophy of minimalism and efficiency that ensures optimal use of system resources. Community feedback is crucial in refining the cloud images, and we encourage users to test them out and contribute.
For more details, visit the official Armbian GitHub repository and join the discussion!
Stay connected and experience the next generation of Armbian cloud support today!
The post Armbian cloud images first appeared on Armbian.
View the full article

We keep (most of) old images here:
https://fi.mirror.armbian.de/archive/
https://fi.mirror.armbian.de/oldarchive/

Upgrade to 25.5.1 successful (straight-forward).

DKMS is 'quite complicated' , in an attempt to understand all that 'cryptic' stuff, I went googling around
https://wiki.archlinux.org/title/Dynamic_Kernel_Module_Support
https://www.linuxjournal.com/article/6896
https://github.com/dell/dkms
https://wiki.gentoo.org/wiki/DKMS
https://www.collabora.com/news-and-blog/blog/2021/05/05/quick-hack-patching-kernel-module-using-dkms/
https://www.baeldung.com/linux/dynamic-kernel-module-support
https://nilrt-docs.ni.com/opkg/dkms_opkg.html
^ surprisingly I found this guide/tutorial from national instruments 'quite intuitive'
and I dug further into how to make a kernel module, well at least a 'hello world'
https://tldp.org/LDP/lkmpg/2.6/html/
https://tldp.org/LDP/lkmpg/2.6/lkmpg.pdf
The Linux Kernel Module Programming Guide
Peter Jay Salzman
Michael Burian
Ori Pomerantz
Copyright © 2001 Peter Jay Salzman
---
ok I actually tried building that 'hello world'  kernel module and *it works*, for practically 'ancient' 2001 instructions.
so it turns out that to compile a kernel module, you do not need to build it in the kernel source tree itself
and that is *without* DKMS, read that last 2 tldp guides: The Linux Kernel Module Programming Guide
you can try building and inserting the 'hello world' module into your kernel, no DKMS, whatever, after you build your module !
in short is it not necessary to build a kernel module within the kernel source tree itself, but that there are some procedures as spelled out
in that 2 tldp docs.
(but fast forward to today, this same instruction may not work if you are using secure boot, then a lot more complicated things like module signing gets involved, review that dkms link from dell)
-------
now back to DKMS , where does that fit in?
so it turns out that DKMS is a utility / tool / system / automation tool, to help you *rebuild the kernel module* - out of linux kernel source tree (i.e. as like the hello world module above), *without building the kernel from source itself* !
but that you need to ***rebuild the kernel module from source***(e.g. using DKMS), then all the other links above are guides that may be relevant
----
now add more complications / complexities, normally what you wanted is a *driver* , not simply a kernel module
the driver often has several parts - the kernel module itself (this is the 'easy' part, you need to build it - from source), and that does not mean having to build the kernel itself from source, but you need to build the *kernel *** module *** *.
after you build the kernel module successfully, say, then there are more blows and pitfall
these days wifi and many network hardware requires *firmware files* , these *firmware files* can consist of 'bin' (firmware binary) and configuration (some of them text files) some of these firmware stuff lives in /lib/firmware.
then that you need your kernel module, you can deem that the 'driver core' that  interface the OS and interface those firmware. those firmware do not necessary run on the (host) cpu (i.e. your pc) but instead in the wifi chip  itself.
this is the part that is *highly opaque*, there are so many wifi chips that are *undocumented*, the firmware is *undocumented* and if you do not have any source for your kernel module which interface the firmware to the os, you are out-of-luck.
-----
 
to summarise - normally, one cannot hope to take a binary kernel module install it in your current kernel and hope it 'just works'.
if that works, a lot of things such as module versions and various constraints imposed by the kernel matches that in the kernel module itself, i.e. that module is compiled specifically for that specific kernel itself !
DKMS do not solve this, DKMS only *helps you rebuild the (kernel) module *** from source *** *, (and install it optionally).
the idea is this, you have the *source* to your out of kernel source *kernel modules*, when you upgrade the kernel, e.g. such as an apt-upgrade etc, DKMS can be triggered to *rebuild the kernel module from source* (and install it) in the new kernel (binary) tree e.g. copy that into /lib/modules/{kernel version}/xxx
---
if the kernel module is part of the kernel source tree itself, it actually do not need DKMS.  But that if the errors occurs  after building that *kernel module* (i.e. driver) , then congrats - you found a 'bug' in the *kernel module (driver)*, and that is true even if it is out of kernel source as a DKMS build. i.e. the driver sources need to be patched to work in the new kernel.

Hi,
wake-on-lan should be working now due to https://github.com/armbian/build/pull/8235.
Groetjes,

Yes. And we will keep fork maintained as long as possible.
https://community.home-assistant.io/t/feedback-requested-deprecating-core-supervised-i386-armhf-armv7/880968/313

/_\  _ _ _ __ | |__(_)__ _ _ _  
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|
                                   
 v25.5.1 for Orange Pi Zero2W running Armbian Linux 6.12.23-current-sunxi64
 Packages:     Ubuntu stable (noble)
 Updates:      Kernel upgrade enabled and 17 packages available for upgrade
 Support:      DIY (community maintained)
 IPv4:         (LAN) 192.168.***.***, 192.168.***.*** (WAN) ***.***.***.***
 IPv6:         ***
 Performance:  
 Load:         11%               Up time:       4 min    Local users:   3                
 Memory usage: 24% of 1.93G      
 CPU temp:     45°C                Usage of /:   10% of 58G        
 Commands:
 Configuration : armbian-config
 Upgrade       : armbian-upgrade
 Monitoring    : htop
orangepi@orangepizero2w:~$
 
It boots into xfce wifi works, eth works and hdmi work.
2gb board with keyboard plugged into expansion board.
 

Yes. And we will keep fork maintained as long as possible.
https://community.home-assistant.io/t/feedback-requested-deprecating-core-supervised-i386-armhf-armv7/880968/313

Yes. And we will keep fork maintained as long as possible.
https://community.home-assistant.io/t/feedback-requested-deprecating-core-supervised-i386-armhf-armv7/880968/313

/_\  _ _ _ __ | |__(_)__ _ _ _  
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|
                                   
 v25.5.1 for Orange Pi Zero3 running Armbian Linux 6.12.23-current-sunxi64
 Packages:     Ubuntu stable (noble)
 Support:      DIY (community maintained)
 IPv4:         (LAN) 192.168.***.*** (WAN) ***.***.***.***
 IPv6:         ***
 Performance:  
 Load:         4%               Up time:       16 min    Local users:   3                
 Memory usage: 45% of 971M       Zram usage:    47% of 485M       
 CPU temp:     46°C                Usage of /:   11% of 58G        
 RX today:     98 MiB            
 Commands:
 Configuration : armbian-config
 Monitoring    : htop
*** System restart required ***
 Some packages require a reboot (gnome-shell)
orangepi@orangepizero3:~$

Yes. And we will keep fork maintained as long as possible.
https://community.home-assistant.io/t/feedback-requested-deprecating-core-supervised-i386-armhf-armv7/880968/313