Igor

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

We have vendor (v6.1.115) based kernel support here, where hw features usually works fine. I didn't do much of testings, only added board to the test farm. I never tried mainline here, perhaps someone else did.
 
Logs: https://paste.armbian.com/uhofaquguz

We have vendor (v6.1.115) based kernel support here, where hw features usually works fine. I didn't do much of testings, only added board to the test farm. I never tried mainline here, perhaps someone else did.
 
Logs: https://paste.armbian.com/uhofaquguz

Hello, we have tried wifi and it is working fine https://www.armbian.com/armsom-sige5/

After years of thinking, wishing and tinkering - Armbian automated WiFi performance benchmark system:
https://docs.armbian.com/WifiPerformance/
From latest WiFi 7 down to (in)famous xradio XR819.

The software used by the Orange Pi "team" is, to a very large extent (estimates go as high as 99.9%), based on the work of developers from the Armbian project (and beyond). Their contribution mainly includes adding basic support for new boards, but unfortunately, without further maintenance or long-term support – which practically means that the entire burden of maintenance and support falls on the community.
 
It should be noted that systems such as Orange OS Ubuntu and Debian on ARM architecture are the result of years of work by more than 500 people gathered around the Armbian project. Orange Pi only makes minor adjustments. In the past ten years, we have not seen a single contribution from any member of the Orange Pi team to the development of these key components. Absolutely nothing, while they keep signing under our work (even changed to some degree) ... on top of stealing software support. Which they don't provide in any way.
 
The work of the Orange Pi team (which appears to be just one individual), on top of some old Armbian, can be tracked here:
https://github.com/orangepi-xunlong/orangepi-build/commits/next (they removed other board configs)

Everything is good, thanks for the help and sorry for confusion, I only should to change PiRogue default interface after installation, this is PiRogue interface detection problem...

From logs I can only conclude that problems are at your side - wrong configuration. Anyone can help you - problem is almost certainly not Armbian specific.
 
May 10 21:05:09 pirogue systemd-helper[8502]: dnsmasq: unknown interface end0 May 10 21:05:09 pirogue dnsmasq[8502]: unknown interface end0  
I am not an expert of application you try to install, in fact I never heard about until now. 

@Igor
Fans working great with fancontrol. I have 92 MM Noctua Fan attached and it is working perfectly. I can adjust the configuration as described here https://wiki.kobol.io/helios4/pwm/
@all
I also edited the default 2.5 inch drives case provided from helios4  (replaced fan mounts from default 70 mm fan to 92 mm fan) and added holes to mount ssds horizontally as well using 3.5 to 2.5 metal adapter from aliexpress .. It looks like this.. Very quiet and the drives stay cool.

Many thanks for fixing this!

I also tested on my side, works now. We can eventually put this board back to supported list. (board config .csc -> .conf)

There are few other things that would be nice to get working - I notice WOL service erroring out, fan support is unknown. I only have PCB without anything attached to it, for testing.
 
Merging both patches shortly.

@Igor
 
> There are few other things that would be nice to get working - I notice WOL service erroring out, fan support is unknown.
 
Regarding "fan support":
Fan was working correctly after installing fancontrol, see
https://forum.armbian.com/topic/44379-fancontrol-bookworm-solved/#findComment-209055
 
(Thread is in Standard support->Other families->Helios 4)
 
 

Hi there,
Now two pull requests are awaiting review:
- https://github.com/armbian/build/pull/8166#issuecomment-2867147049
   Update the boot.scr script to calculate load addresses in case `setexpr` is available on the U-Boot monitor.
- https://github.com/armbian/build/pull/8170#issuecomment-2867915659
   Enable the `setexpr` command on the U-Boot monitor, to unlock load address calculation in combination with the boot.scr update.
 
Both are now tested OK using a built armbian 'minimal' image based on Bookworm.
 
Groetjes,

I am still here  but as we all know our time is precious and I am currently using all my time for other projects. So I am not currently maintaining this board.
On the whole I think armbian is moving too fast, for me, with new features in the build system and kernel which has somewhat discouraged me from further investing my time. ARM is IMHO not a stable platform, unfortunately.
 
@djurny solution looks good - I might test this later and try to integrate it. But everyone else, if you can, please make it a PR on github
 
It should only be necessary to adjust this file https://github.com/armbian/build/blob/main/config/bootscripts/boot-mvebu.cmd

Welcome on board.
 
 
This will be a huge difference, so be open for learning, have a lot of patience.
 
https://docs.armbian.com/User-Guide_Board-Support-Rules/
One of the key challenges we face is that maintaining older hardware is both time-consuming and costly. With limited financial and community support, the resources we have are already stretched thin across the entire project.
 
Our team is very small—currently, we have only one dedicated maintainer for the Allwinner software stack that is focused into latest 64bit Allwinner family (H6/H6xxx). Other projects often face similar constraints, often relying on a single contributor who can do anything. For example, in our collaboration with LibreELEC (LE), we benefit from some shared efforts, but both sides are still primarily driven by individual volunteers working on a best-effort basis. If priorities shift, progress can be delayed significantly—and unfortunately, Armbian doesn't have the capacity to pick up.
 
I’m sharing this openly in the hope that it raises awareness. Personally, I would love to see continued support for legacy devices. But to make that happen, we need to ask: who is willing and able to invest weeks or months each year required to maintain these older platforms?

What you can do? Try to understand how this works, connect with people that share your problem (all similar board owners with interest that it is maintained) - invest time to learn.
 
 
Probably USB ports are just not enabled - check this: https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-overlays

@Werner thanks for your time.
 
I found the solution in this post:
I'll never be able to say it, but this community is the best I've ever seen.
I want to thank you because once again, I couldn't have solved the problem without it.
Thanks @djurny@Igor and the all the people of this post.
 

This is everyone's problem.
 
Buy boards that are supported and maintained. We have not received any support from Orange Pi, contrary, their business model is very damaging to us and donations only pays coffee and beer. We do not maintain or officially support hardware you have, and AFAIK it is not maintained by anyone else - but if it is, it will get to Armbian too. However, given the similarities across these boards and the nature of open source, it’s difficult to prevent Orangepi and their customers (you) from abusing open source development.
 
 
This is everyone's problem. Stop buying hardware that we don't and won't support as making a pressure to open source developers is worse thing you can do. Hardware dealer abuse is already big enough.
 
 
Just a polite reminder that you are not a customer, so adjust your over-expectations.

Not anymore  ZFS, versions that we are adding is now again properly autotested:

and this won't be happening in the future. If dependency check fails, packages are not pushed into the repo ...

In case you get "Unsupported system warning", replace 
PRETTY_NAME
with
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
inside /etc/os-release
following by reboot.