Igor

They are not empty. You need to go one level deeper:
https://armbian.nardol.ovh/dl/tinkerboard/archive/
 
BTW, try https://github.com/armbian/imager It will be much easier.

In the past (2019)
there was no chance to use the A64-CPU Jide Remix Mini with armbian, because of a blocked -u-boot

But today I found a site (from February 2025 on github)
https://github.com/r4nd3l/revived_remix_mini_pc?tab=readme-ov-file
which can make the Closed Jide Remix Mini to boot from SDCard with a modified u-boot

There at the github page is a modified u-boot and a modified A64 armbian for the Jide Remix Mini.
Jide did leave us with a closed/blocked device  AT this time the 16GB emmc isnt useable, but using SDCard is a start for upcycling the Jide Remix Mini
 

We are slowly releasing v25.11 images and here I did some mess-up, fixed now. We don't offer Bookworm anymore, so Trixie it is. If you need to Bookworm for some reason, you can build on your own or use the one from archive: http://archive.armbian.com/

Attached torrent will download super fast.
Armbian_25.11.1_Helios64_trixie_current_6.12.58_minimal.img.xz.torrent

We only provide mainline based kernel, where video acceleration might not work. If you have a need for that, than use those hints:
 
add DT here:
https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr5.1/arch/arm64/boot/dts/rockchip/rk3568-odroid-m1.dts
enable vendor kernel 
https://github.com/armbian/build/blob/main/config/boards/odroidm1s.csc#L7
build with ENABLE_EXTENSIONS="v4l2loopback-dkms,mesa-vpu" and desktop will work faster, video acceleration will most likely just work OOB.

I guess this should do:

Hello, another Odroid M1S owner and user here. I tried the Ubuntu image because I was curious about video acceleration in particular. So I installed Kodi and played a few videos. There is no acceleration. This means that this image is not usable as a player. However, it will probably be usable as an SMB/NFS server (I'll try using it that way for a while).
A few comments:
- Gnome is relatively slower, but not unusably slow (I personally don't mind, because I don't intend to use the M1S as a desktop)
- Gnome sometimes has problems rendering windows, there are strange stripes, only in certain parts of the windows, and at times it is so annoying that it becomes unusable
- Personally, I would love it if someone experienced could take a working GPU driver and put it into this image. That would solve everything, and we could all use the M1S to our full satisfaction (however, it's probably not that easy, because otherwise the guys at Odroid would have already done it).
- I will add relevant links to a functional accelerated solution that makes the M1S a fully functional driver, but based on the very old and not very usable 5.10 kernel
- https://forum.odroid.com/viewtopic.php?f=217&t=47621 here is a functional Odroid based image solution for media player.
- By the way, I managed to upgrade the image mentioned here to Ubuntu 24.04, using the Kodi build for Odroid M2 ( https://forum.odroid.com/ viewtopic.php?f=235&t=49005 ), but I had to stay on kernel 5.10, and even this version works relatively well as a functional player with accelerated videos (the old kernel is a prerequisite)
 
I hope that I have contributed at least a little to making this Armbian image gradually become the standard for M1S, because this computer deserves it.
 
 

So, here's what I had to do to successfully build the image. First, I corrected my board file in the config/board/orangepizero3.csc directory. The processor value was incorrect, it was 616, so I set it to 618.
Menuconf suggested selecting a board with a 618 chip, but in the board file it was listed as family 616.
Later, I copied my board file to the userpatches directory and added the value CONFIG_DRM_PANEL_MIPI_DBI=m. Then I ran the image build script with the menuconf viewer. I was surprised that the CONFIG_DRM_PANEL_MIPI_DBI parameter already had the value "m"; previously, it was empty.
After all these manipulations, the build went smoothly. Thank you so much for your support.

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.