Werner

Hi, this issue is unrelated to Armbian. I suggest to ask at openhab about the expired key signature. They should know.

Feel free to try with rpi4 since we provide 64bit images for it.

You're in luck Built one this morning for testing myself. Didn't have a chance to do so yet though but feel free to use: https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_noble_vendor_6.1.84_kde-neon-kisak_desktop.img.xz

If you have a chance please also test against the Trixie image with updated vendor bsp kernel (6.1.84) I mentioned above. Just to be sure this wasn't fixed by rockchip already. Also as a last resort check old archives for images based on 5.10.y which is (almost) the same kernel as the images provided by Orangepi: https://fi.mirror.armbian.de/oldarchive/orangepi5-plus/archive/

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

That is just a small script for user convenience which does this: #!/bin/bash trap "exit" INT TERM [[ $EUID != 0 ]] && exec sudo "$0" "$@" apt update apt -y upgrade apt clean apt -y autoremove exit 0 Nothing weird, nothing fancy, just upgrades and house-keeping.

https://www.armbian.com/orange-pi-5-plus/ Scroll down to either server or desktop images featuring 6.1 kernel. These come with 6.1.75 I think. Shortly after the release there was a transition to the most recent rockchip sdk kernel which bumped to the version to 6.1.84. You can find a pre-made Trixie based one as pre-release image here for testing: https://github.com/armbian/os/releases

Hi, regardless of the image you are going to use we at this forum can only support Armbian images downloaded here: https://www.armbian.com/bigtreetech-cb1/ If you miss fixes or features that should already be included in Armbian you can also try pre-release images from here: https://github.com/armbian/os/releases

Already done: https://github.com/armbian/build/blob/main/extensions/uefi-edk2-rk3588.sh

Hi That one probably uses old vendor bsp kernel while the Armbian image you tried follows mainline which isn't feature-complete yet. I suggest to retry an Armbian vendor kernel based image.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

moved to staging. https://docs.armbian.com/User-Guide_FAQ/#why-is-there-no-image-for-board-with-bookwormjammynobletrixie-and-minimalclignomekdexfce-with-vendorlegacycurrentedge-kernel

duplicate https://forum.armbian.com/topic/48456-collabora-upstream-support-for-rockchips-rk3588-progress-and-future-plans/#comment-208966

Everything is here: https://github.com/armbian/build/

You can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -U to force output to stdout. Then copy&paste to a paste service manually.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

This means your Armbian is very outdated. We replaced ix.io with our own services quite a while ago.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

@Igor can do that. My guess is that the previous owners of the domain forgot to extend and therefore it expired and now some domain grabber registered it.

Why not ask where it might more sense and chances for answers are greater? https://forums.rockylinux.org/

Actually the first bsp was that which was built around a 5.10.110 and later .160 android hacked together kernel. 6.1 is AFAIK a real linux kernel rockchip used for newer bsp.

There is nothing we can do about this error.

https://developer.arm.com/Arm Security Center/Speculative Processor Vulnerability On the bottom line there is nothing we can do about this. If mitigation is upstreamed to ATF, Kernel or wherever needed/possible Armbian will adapt it most likely automatically. Dug a bit deeper https://developer.arm.com/-/media/Arm Developer Community/PDF/Security update 21 May 18/Software_Overview_for_Arm_Cores_PUBLIC v1.2.pdf?revision=7bb9a901-9a1d-4975-b460-743f5da90502&hash=14B19D60AC5650AF05225AEECC5E3D816E08B47B https://cateee.net/lkddb/web-lkddb/MITIGATION_PAGE_TABLE_ISOLATION.html Though this seems to be a software mitigation for x86 only. No clue if there is further development ongoing.

https://backports.debian.org/news/Removal_of_buster-backports_from_the_debian_archive/

Debugging boot issues: https://debug.armbian.de