Werner

There is an armbian-firmware package. I suggest to push your adjustments there: https://github.com/armbian/firmware/

Tried this? https://forum.armbian.com/topic/44964-wifi-setup/#findComment-205743

@JohnTheCoolingFan can probably answer this.

logs???

Multiple ways. Attach HDMI, attach serial console or check switch/router interface for the ip.

Hi While I like the idea IMHO avahi is a userspace thing and we don't want to overload the images with pre-installed packages as this, last but not least, eats into our resources in creating and providing them for free.

First question? Why??? Replace boot: https://docs.armbian.com/User-Guide_Recovery/#replacing-boot Easiest would be if you had another arm64 based system since you could simply chroot into the sdcard and then do regular apt operations to install correct packages again.

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Please check your /boot/config-... for "CONFIG_USB_ETH"

Supported no, possible maybe. https://docs.armbian.com/User-Guide_FAQ/#can-i-upgrade-my-userspace-flavor-like-bullseye-to-bookworm-or-jammy-to-noble

Feel free to use this one I actually made for testing purpose but hadn't had a chance to do so yet: 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

Yes. vendor kernel is also necessary for vpu to work. mainline support is still wip.

I don't think there is an oob solution. Though using an Armbian image with mesa-vpu extension should give a solid base for video hw acceleration.

mainline support for rk3588 is far from feature-complete and still under heavy development. If you need things just to work for now use vendor branch.

This is correct. Try this for the Armbian related: https://forum.armbian.com/topic/23465-apt-get-update-fails-with-public-key-errors/page/2/#findComment-178626

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.