Werner

https://docs.armbian.com/#what-is-the-difference-between-armbian-and-debianubuntu

https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel
 
Build your own if you need it: https://docs.armbian.com/Developer-Guide_Build-Preparation/

https://docs.armbian.com/User-Guide_Networking/

Existing installations can simply be apt update/upgraded since both Ubuntu and Debian released fixed versions for their supported userspaces.
Armbians rootfs packages, which are used for building new images, have been recreated and pre-built images available for download are being rebuilt/replaced as well.
 
tl;dr: mitigation is in the works/already done

There is no UEFI or Secureboot available on this board. However you may want to try this: https://github.com/edk2-porting/edk2-rk3588
and then https://github.com/tianocore/tianocore.github.io/wiki/How-to-Enable-Security

Make sure to 
- write SPI during the mentioned armbian-install process
- that /boot directory has been populated on the NVMe. If not mount and copy files from sd manually there.

https://archive.armbian.com

known issue
https://github.com/armbian/build/issues/6568

https://debug.armbian.de

Not necessarily.  IIRC Gnome was selected because of its mature Wayland support. So the UX might differ on other constellations.

Maybe the mirror in question was syncing at the moment. If EU works fine other should as well after a bit of waiting.

Ubuntu can, we cannot. Unfortunately.
https://docs.armbian.com/User-Guide_FAQ/#why-are-old-stable-distributions-like-ubuntu-focal-or-debian-buster-not-supported
 
About userspace upgrades:
 
 

Not support yet
We also need some time to prepare and roll-over stuff to a new environment.
Also check https://github.com/armbian/build/issues/6527

Did you try installing armbian-firmware-full via apt?

Hi,
 
Unfortunately this is not the case (yet). Tags are more or less just for archiving the state of the build framework at a certain point of time (usually at release). Due to its design we are not there yet to have working tags that could reproduce older images.
It is our goal to have this working at some point but things are processing very slow.
 
VERSION doesn't do anything and is pure cosmetics.

Both 5.10 and 6.1 are vendor bsp and have nothing in common with collabora/mainline.
Their hw support status should be more or less identical.
 
mainline is 6.8 or 6.9-rc

armbian-install is meant to be used inside the running Armbian system from microSD card. It copies itself to NVMe or eMMC or whatever options are available and can be utilized. This tool does not work "offline".
 
Anyway. I never did something like that by myself but maybe you find some hints when you google for keywords like "h616 fel sunxi-fel emmc".
fel mode seems something like Rockchips maskrom to utilized the rkdevtool. Maybe Allwinner has something similar

Maybe they are still being assembled. Release is planned.
Check for server images here and then do apt update/upgrade once its released: https://fi.mirror.armbian.de/archive/orangepi5-plus/archive/

Hi,
 
=y means the driver/functionality is directly compiled into the kernel
=m means it will be built and made available as kernel module
 

https://openzfs.github.io/openzfs-docs/Developer Resources/Building ZFS.html
 
[ 424.596656] zfs: module license taints kernel. [ 425.491531] ZFS: Loaded module v2.2.99-311_gd9cb42da9, ZFS pool version 5000, ZFS filesystem version 5  
tested on OPi5 with kernel 6.7.1
 
Getting it working on legacy 5.10.y rk Android-hackedtogether kernel is a bot tougher.
https://github.com/radxa/kernel/issues/54
Spoiler: patching method does not work anymore, at least not for me . Tested with 5.10.160...
 

You need the kernel headers matching your kernel version. Older headers will not work.
However we  had (have?) some issues with the repository so you may need to switch to a different kernel version which also has the matching headers in the repo.

Providing logs with 
armbianmonitor -u  helps with troubleshooting and significantly raises chances that issue gets addressed.

Provide boot logs to get an idea what happens inside.
 
 

Enable OC overlay via armbian-config