Igor

Problem is in Balena decompression of xz files. Use USB imager or something else (or 2 years old version of Balena). It will work. We filed bug when it was discovered, but it was not fixed by this day. We can't fix this app for them ... BTW. Its all here: https://docs.armbian.com/User-Guide_Getting-Started/#flash-to-sd-card

6.6 is LTS kernel https://www.kernel.org/category/faq.html When some security issue is found, it goes into all LTS kernels. Higher version number does not guarantee bigger safety. Most recent has more functional bug fixes and new features and is generally more fragile - bugs / holes yet to be found. Yes, v25.11.1 with 6.12.y https://www.armbian.com/odroid-hc4/ doesn't have those problems. At least I could not recreate them. Booting HC4, plugged in two usb devices, all good: https://paste.armbian.com/ibifozegof P.S. Life is deadly dangerous

It is now.

Strange. Well, I tested recently released v25.11.1 images https://www.armbian.com/nanopi-m4-v2/ and they boot (Noble Gnome). I won't be testing older images. (image upload still working in this moment - will take an hour or so to appear on /dl pages) @GuestWho

I tested v25.11.1 https://www.armbian.com/orangepi-5/ released yesterday - vendor kernel, Gnome desktop, acceleration works, 4k video playing with Chromium, audio works ... Since I don't have model + right on hand, i didn't test it. But its very similar board and I assume it works. It should even boot with image for normal Opi 5 but all peripherals won't be working correctly.

We don't have resources to deal with this question, but I think, in case of this hardware, there is just firmware package (armbian-firmware / linux-firmware) that fits into this. Perhaps some other util. There must be some scripts to scan Debian packages and tell? From my head, I remember iozon3 package (might not be by default on minimal) that is non-free https://packages.debian.org/bookworm/iozone3

One interface is for STA (client mode / normal wireless) and one for AP (access point, where you connect to) or P2P (Wi-Fi Direct). Some firmware / drivers enables this by default. Usually it is in Makefile (just example https://github.com/armbian/rtl8723ds/blob/main/Makefile) but it could also be deep in the code. Don't know.

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

Try from here: https://fi.mirror.armbian.de/incoming/igorpecovnik/ (this is going to be next release - first test build).

There are no other images available at the moment. Regarding this, there is some initial but incomplete work in progress here: https://github.com/armbian/build/pull/8831 We can’t merge it in its current state, as it still requires a significant amount of additional work and refinement. Unfortunately, this means there isn’t a quick solution right now, so we’ll need to wait until the implementation is completed and validated.

Is SSD in good shape and is SPI flash o.k. ... logs would tell more.

Attached freshly build bootloaders - normally they are packed into uboot deb. flash-image-DDR4-2g_2cs_6-800_800.bin flash-image-DDR4-2g_2cs_6-600_600.bin flash-image-DDR4-2g_2cs_6-1200_750.bin flash-image-DDR4-2g_2cs_6-1000_800.bin flash-image-DDR4-1g_1cs_5-800_800.bin flash-image-DDR4-1g_1cs_5-600_600.bin flash-image-DDR4-1g_1cs_5-1200_750.bin flash-image-DDR4-1g_1cs_5-1000_800.bin flash-image-DDR3-512m_1cs_0-800_800.bin flash-image-DDR3-512m_1cs_0-600_600.bin flash-image-DDR3-512m_1cs_0-1200_750.bin flash-image-DDR3-512m_1cs_0-1000_800.bin flash-image-DDR3-2g_2cs_7-800_800.bin flash-image-DDR3-2g_2cs_7-600_600.bin flash-image-DDR3-2g_2cs_7-1200_750.bin flash-image-DDR3-2g_2cs_7-1000_800.bin flash-image-DDR3-1g_2cs_2-800_800.bin flash-image-DDR3-1g_2cs_2-600_600.bin flash-image-DDR3-1g_2cs_2-1200_750.bin flash-image-DDR3-1g_2cs_2-1000_800.bin flash-image-DDR3-1g_1cs_4-800_800.bin flash-image-DDR3-1g_1cs_4-600_600.bin flash-image-DDR3-1g_1cs_4-1200_750.bin flash-image-DDR3-1g_1cs_4-1000_800.bin

I tested self build opi5 few days ago and there was no problem installing and booting from nvme, legacy kernel, Noble Gnome desktop. Make sure you select second option when updating SPI bootloader (not sata).

Hard to say how far that work has progressed and what currently functions. You are welcome to use it and continue development on your own. Armbian is primarily a build framework, and our capacity for maintaining hardware is very limited — typically to just a few boards or platforms. Tony played a key role in this effort, though he may not be available to continue contributing in his personal time. Getting to this point was already a loss of our precious time.

We have discontinued maintenance and support for this hardware, as our collaboration agreement with the vendor did not move forward as planned.

Yes, but I haven't test it. I used pre-flashed to boot my image and I am done with this board / platform. Someone else has to take it from here. If board gets maintained status, this will start working automatically. Links point to our servers where this board images are not present - we only keep supported on our servers, for things we know they at least boot.

https://github.com/armbian/os/commits/25.11.0-trunk.367/git_sources.json This file determine state (hash) of sources. It's not a straightforward process, but one can recreate exact image (except userspace packages, which versions are not stored) This file has to be here https://github.com/armbian/build/commit/31e82512cc60a74f56b710aa2971d7dc2beec9b9 One day, this will be done better Sadly there is too much of such e-waste and way way too little people willing to maintain them in their limited private time. I am sure you can find a working image somewhere in our archives so you don't need to throw it away, but we cannot fool you & ourselves to be able to keep this board maintained.

I put it together, bumped kernels, uboot, briefly test. Anyone volunteer to become a maintainer? https://github.com/armbian/build/pull/8873 https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support

Integrated with bump of uboot and kernel. https://github.com/armbian/build/pull/8873 Test image: https://k-space.ee.armbian.com/incoming/igorpecovnik/ebin/Armbian-unofficial_25.11.0-trunk_Espressobin_trixie_current_6.12.57_minimal.img.xz

Weekly community image produced: https://www.armbian.com/odroid-m1s/ If anyone wants to volunteer as maintainer, a full set of images can follow: https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support

I had to rebuild server and this was not fixed yet. Temporally location https://stpete-mirror.armbian.com/users.armbian.com/

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.

Only that its a known issue. In open source world it is normal to see magnitude more issues then its resolving capacity. I'll look into when possible - its high on 2do list. No need.