Igor

FYI. I tested booting Rock64 with latest images, but there are several revisions of this hardware and not all might work (well).

Yes. Then we have automatic test install on target release while making a PR. If that passes, merge is good to go.

Yes, it does. But AFAIK only for selecting a correct board: https://docs.armbian.com/User-Guide_Armbian-Config/System/#select-odroid-board-configuration If you know what you are doing, no problem. That's why. And yes, you need to edit boot.ini. We had an idea to remove this Hardkernel proprietary configuration, but never managed to moved to modern boot loader. This HW is 10 years old, if someone wants to change this, else it will stay in this (a bit confusing) state. But it should work. Bigger problem is dying armhf architecture and complex suites such as OMV, might not be build-able anymore and there is nothing we can do about. Alternatively, one can use general tools like Samba / NFS for storage.

Via web: https://packages.ubuntu.com/ by checking dependencies https://packages.ubuntu.com/jammy-updates/zfsutils-linux and figuring out what is the next numbers. As its not always n+1 Askig AI: https://chatgpt.com/share/67e04381-7ecc-8005-b3c3-ade19c10e450

Yes. If you stay with Jammy, you are on old stable user-space, updated directly from Ubuntu, kernels from us. Packages on (old) stable base are rarely updated, usually only if some security problem is detected. If you want to have all packages updating, you need to use Plucky nightly build for your board - accessible at the bottom of download pages. There much more packages will be receiving updates, daily, but that also means bigger risk for running into troubles.

But you can step up and maintain this for everyone? We don't provide direct contact email, as we don't have capacity to deal with all packages that exists in open source world and as you discovered by yourself, some maintainers are not longer with us, so many packages doesn't really have anyone doing this. In our system - all you need to do is changing / bumping numbers and open PR. If build and test succeeds, someone with merge rights, merge it into the system and within few hours, packages are available on repository. PR: https://github.com/armbian/os/pull/300 Pool and test install was successful: https://github.com/armbian/os/actions/runs/14016836904/job/39243546741 Merge follows, packages will be out with next repo sync.

We had to gave up with maintaining this hardware so there is absolutely no warranty that it builds and boots. To verify if your build environment is operational, try to build some supported targets by using a switch ARTIFACT_IGNORE_CACHE=yes This will force recompilation and will tell you if everything is alright. Try with Raspberry Pi or any other supported target to see if things are right at your side.

By community is already supported for some time we even discussed option for official support in cooperation with its maker. We do that for their CB1. Which is Allwinner based, thus pretty different. As @Werner proposed, build is best, also there you can enable HA extension and build with preinstalled Home Assistant. We don't make stable pre-build images, but nighties are generating https://github.com/armbian/os/releases/

If its not in https://archive.armbian.com/, then we don't have it anymore.

If you are using kernel 6.12.y, perhaps related: https://www.armbian.com/newsflash/armbian-weekly-highlights-11/ -> https://github.com/armbian/build/commit/bf9ffa6eedd5df804e3f9a86c84e00607289cd59 which means fix just landed nightly builds.

https://docs.armbian.com/User-Guide_Armbian-Config/System/#install-alternative-kernels

Best recommendation is to drop vendor kernel and start using mainline derived (6.12.y at this point). Can be switched to (CURRENT) in armbian-config. Features that are missing are not much relevant for server setup. We are using RK3588 with mainline kernel in build farm for about a year (even with some development kernel). There ZFS will work without issues / the same as on x86 mainstream Linux distro. This kernel comes from https://github.com/armbian/linux-rockchip and might be very different then kernel.org

- reducing DRAM speed (u-boot) - reading this to get some ideas https://github.com/crust-firmware/crust (it was implemented into Armbian some time ago https://github.com/armbian/build/pulls?q=is%3Apr+crust+is%3Aclosed)

We are having an alias - probably bad move, removing: https://github.com/armbian/build/pull/7962

Single board computers are purpose oriented devices, where booting and using live OS is common. This is how installer was designed - you can boot and run OS from SD card. And move OS to internal memory at any moment - freshly & clean, after one year, never.