Igor

Old automated builds are not kept. Only last three releases https://github.com/armbian/community/releases Its 300Gb / week

fixed

It is not recommended to match ZFS with vendor kernel(s). In general. Use mainline based current / edge kernels. Here v6.18.y we also might not have suitable ZFS yet as the kernel is too fresh. But if not today, it will be avail within days / weeks.

First testing on similar device (Odroid N2) didn't reveal any troubles. Need to locate VIM3 and try to recreate.

And others: https://docs.armbian.com/Mirrors/#current-mirrors

Sure, no worries. You will notice once its fixed. as this is not something you should adjust on the APT client side. You didn't and won't loose anything except current updating mechanism is broken.

I spent practically whole holidays to rework repository management and there are still some problems, even it was tested on and on before going into production. But beta repository, which you are having troubles with, was never tested. Only stable. Motive: https://github.com/armbian/build/pull/9150 Affected: https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/infrastructure-repository-update.yml https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/infrastructure-download-external.yml https://github.com/armbian/armbian.github.io/blob/main/scripts/sync-repository.sh https://github.com/armbian/armbian.github.io/blob/main/scripts/copy-kernel-packages.sh https://github.com/armbian/build/blob/main/tools/repository/extract-repo.sh https://github.com/armbian/build/blob/main/tools/repository/repo.sh ... so you might get an idea on the problem complexity

Current way of installing is as written on the download pages. It was verified with latest v24.11.2 image.

Yes, highly recommended in order to avoid troubles. We mainly use Noble and all of our build & test automation runs on Jammy / Noble. However, when using Docker, you should have more freedom.

Welcome! Strange. Works here without a problem: https://paste.armbian.com/uqutokajas

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.

I though some older images worked ... here you are on your own. Compare device tree from cubox and this hardware and repeate this on modern kernel, and apply difference. Just an idea. Sadly, no simple solution such as download and play.

If you need older images for cubox-i, archive and oldarchieve at https://fi.mirror.armbian.de/

You need this for m1s. As I said, those were hints / clues, not an actual how-to. Writing how-to takes more time then doing it

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.