Igor

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.

Correct. It's a problem of: https://github.com/armbian/os/blob/main/.github/workflows/complete-artifact-matrix-all-stable.yml and this configuration: https://github.com/armbian/os/blob/main/userpatches/targets-all-not-eos.yaml It is something to study

This kernel is available only when you change repository to beta.armbian.com , which provides daily builds. EDGE kernels comes as is - glad to hear it works, but beware it might also break down as kernel is changing rapidly.

Long time no see! This doesn't look right. I checked docents of commits and so far couldn't find anything that would stand out. nand-sata-install only copies / rsync file-system, recreate boot scripts and flash boot-loader if necessary. If usb_storage is missing from initird, its normal that it doesn't boot. Its as module: https://github.com/armbian/build/blob/main/config/kernel/linux-odroidxu4-current.config#L1274 I would say its something to do with initird generation. Could be on the build / distro tools side. @belegdol perhaps knows something?

yes

What do you mean by that? You mean LCD screen on the device and HDMI monitor. This should probably work OOB on vendor 6.1.y kernel. It should also work with mainline, but I haven't tested that and I am not sure that this is included in latest stable build as it was added not long ago. Try build from sources, use EDGE kernel perhaps. It is very specific case - probably nobody asked for that before. At least I don't recall. Core features are based on SoC, so when you are looking for clues, look wider - Orange 5 *, Khadas Edge 2, Bananapi M7, ... all that carries RK3588 SoC. Best is to start with recommended Gnome image. That is most polished.

"*** Warning - bad CRC, using default environment" This is safe to ignore. It is strange why Ubuntu doesn't work, while Bookworm does. This could be some build infrastructure issue. https://docs.armbian.com/Developer-Guide_Build-Preparation/

HW (features are determined by kernel used in the image) related issues are shared among all variants, desktop, cli, minimal, Debian or Ubuntu.

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.

Kernel packages comes from the same (main) repository. This won't cause you problems, if you upgrade from bookworm to trixie, but we can't guarantee for packages that comes from Debian. You might try this way: https://docs.armbian.com/User-Guide_Armbian-Config/System/#stable-distro-upgrade Note that you might need to download updated Armbian key: wget -qO - https://apt.armbian.com/armbian.key | gpg --dearmor | \ sudo tee /usr/share/keyrings/armbian.gpg > /dev/null cat << EOF | sudo tee /etc/apt/sources.list.d/armbian-config.sources > /dev/null Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg EOF

I think official stand from open ZFS project is: "ZFS is not designed for 32-bit kernels" ... it still might work(ed). IMO stay on kernel 6.6.y. I doubt there is anything wrong on Armbian side ... worth experimenting with Ubuntu Noble minimal image to rule out possible headers incompatibility.

OK. I think workaround is to re-download / re-install armbian.key from repository. As key was already changed.

I think the core problem is that headers were compiled with Ubuntu compiler / userspace and you try to use it on Debian. I used this on Ubuntu, which is the reason why it worked. We are aware of this problem - headers should be distro specific. Which adds complexity on our side ...

We already did that. I think the problem is that our keys are not packed (yet) but added at build time. When a person upgrades from Bookworm to Trixie, this will show up, while on new Trixie images this shouldn't manifest. @zital debian Is this the case? https://github.com/armbian/configng/commit/5d866b9b105bfd46cb341c21c70ba76e32e1fea2 We are signing with old and new key (which is aligned with current standards) since then.

Currently yes. A replacement for this package / service needs to be found and implement - in case you want to get involved. Thank you! It's a work of many people, impossible for me to poke into every issue or feature that exists

From desktops I tested Gnome - works.

Recommended. It looks like its not that far away. With rebase you will see the diff and if this is all you need to apply.