Igor

I downloaded 'Armbian_25.11.2_Odroidc2_trixie_current_6.12.58_minimal.img.xz', flashed it to sdcard, and it booted fine.
 
As a sidenote unrelated to the issue at hand, my first try was with the sdcard on a device with emmc, and in this case the boot process stopped after block-local (?), and dropped to initramfs shell prompt.

I guess this should do:

I guess this should do:

This is confusing for me. What are you actually trying to achieve? What is on Renegade that is not on Rpi?

Yes. It is only enabled / working with 6.1 and desktop (Gnome) builds. For mainline based, perhaps 6.18.y ...

Lowest price is what makes it popular. But software is the biggest key of the package and there they are among the worst.
 
 
On this SoC, we will be cooperating with SoC maker's board directly - working with Orangepi is too damaging for us:
https://www.cnx-software.com/2025/04/27/muse-pi-pro-feature-packed-credit-card-sized-spacemit-m1-risc-v-sbc/
This will probably be done in a couple of weeks, so you can follow that and adjust accordingly.

Hello SteeMan,
Thanks for your answer
Its running now
And I will browse the getting started pages
To get this system running well
It seems faster
So i hope i can learn a lot at this forum
Greetings Herman

Also we fixed TUI / GUI way of setting UARTS, merged today:
 
https://github.com/armbian/configng/issues/360
https://github.com/armbian/configng/issues/344
fixed with 
https://github.com/armbian/configng/pull/393

Use the one that works / safe to ignore. I think one device is normal and the other for WiFi direct. 

@IgorI'm back from the brink. New job, new house build 3 hurricanes. I'm still working on my 1 acre lot to clean up the vines and stuff, but I'm starting to have more time for this kind of stuff. I need to get all my old boards up to date, hahaha

yes

Preparation  
Supported build environment is Ubuntu Focal 20.04 x64 (minimal iso image).
 
a guest inside a VirtualBox or other virtualization software, a guest managed by Vagrant . This uses Virtualbox (as above) but does so in an easily repeatable way. Please check the Armbian with Vagrant README for a quick start HOWTO, inside a Docker ,  systemd-nspawn  or other container environments (example), running natively on a dedicated PC or a server (not recommended), 20GB disk space or more and 2GB RAM or more available for the VM, container or native OS, superuser rights (configured  sudo  or root access).
  Execution apt-get -y install git git clone https://github.com/armbian/build cd build ./compile.sh This will download all necessary sources, execute compilation and/or build a boot-able image. Most of things will be cached so next run will be extremely faster!

Real time examples:
 
 
 
 
 
Documentation

Sige5 is community supported and those boards receive automatic generated images only - once per week. Since GitHub introduced additional limitations few months ago, we can't (auto)produce desktop images anymore - only one Debian stable minimal per CSC build target. However, this might change in the future.

I also upgraded from bookworm to trixie and saw this warning. I can confirm that Igor's suggested workaround addresses it:
wget https://apt.armbian.com/armbian.key gpg --dearmor < armbian.key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null apt is now happy with the armbian repo.

This isn't completely true.  Armbian still does utilize CPUMIN/CPUMAX from /etc/default/cpufrequtils if present to set corresponding frequencies via the Armbian script armbian-hardware-optimization (packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization).  This script I believe runs at every system startup.  So even without the cpufrequitls package installed, there is still some functionality in this area.  Functionally that no one has likely touched or looked at in years.
 
 
 
 

From desktops I tested Gnome - works.

R76S will be supported, but its too early at this stage. We setup download page https://www.armbian.com/nanopi-r76s/ but no images yet.

HDMI output might be broken on this kernel - mainline support is still fragile, perhaps for this board there is no device tree yet and it fails early.

https://paste.armbian.com/ehuwawexih
v25.5.1 image (Debian Bookworm minimal) runs on my Cubox i4, but HDMI out is untested ... images were released, only because I manage to spent some time testing and as I found out that build actually works.
 

Yes, I did read that. I was also thinking maybe the decompression on-the-fly could be a point of failure.
 
Just now, I installed USBImager and wrote the image to a uSD. No presets applied (.not_looged_in_yet) First boot went smoothly. I updated with armbian-upgrade and rebooted and all looked OK. 🤷🏻‍♂️ Since I changed 2 things (using USBImager and no presets) I can't say what helped.

https://github.com/armbian/build/pull/8517 appears to fix my SFP problems.
 

... straightforward and smooth.
 

Unfortunately I was not able to work on this topic appropriately and thus could not provide any helpful information.
But in the meantime, others have done a lot of work on this topic. Thank you @uablrek for the link.
So I tried and built a new image (from main branch) after https://github.com/armbian/build/pull/8449 had been merged. I can confirm that the Rock 4SE now boots with this version.
 
Thanks to everyone involved for the solution!

fussing about duplicate post, yes, same problem, different but identical machine.  I have several of these bpi-m5's in service here, And its happened several times while I have reached the age of 90 where short term memory is only weeks.
 
This then. with your link to systemd stuff, is bad code you inherited, blindly. My solution to that was/is to make hostname immutable after editing it.  Much simpler than reading thru half a gigabyte of purposely opaque docs looking for clues.
 
With the advent of led backlighting for monitor screens, CRT screens no longer get burnt in.  So one thing badly needed is a bright red, much bigger mouse pointer that moves at about 1/10 th of its present speed, and an easy way to totally disable screen and mouse blanking. On a 3d printer, they are both a hindrance, adding 10 to 30 seconds to taking action when a printer malfunctions.   And because I use this OS heavily, I also donate a smallish bit of my SS income to your cause on a monthly basis.  Thank you Igor.

@Igor Thanks.  
The weird noise is resolved. It was HDMI cable.