Werner

Hi, best way to follow mainline development is both the Collabora sheet here https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md and the Linux/U-Boot ARM patchwork: https://patchwork.kernel.org/project/linux-arm-kernel/list/ https://patchwork.ozlabs.org/project/uboot/list/ Though none of this exists for 6.1.y or older 5.10.y since these kernels are from Rockchip SDK (and these are not even public but leaked by people who have access) and nobody knows (at least I don't ) what or if they are working on at the moment. Closest in following this development is check the commit log here https://github.com/armbian/linux-rockchip or its forks. Maybe somebody works on something: https://github.com/armbian/linux-rockchip/network

Yes, probably. Basic kernel support should be there in both vendor and (I guess) with 6.14 mainline dtb being pushed. So it narrows down to wifi drivers and some tweaks and maybe dts issues. Feel free to dive into.

This is an unsupported (community/staging/whatever you wanna call it) board and those do not get stable build. Become a maintainer and change it

As mentioned it was just a guess. Maybe something else is missing. Flaw in dts maybe? Dunno. Anyone who has some spare time might dive into and check. Armbian core team probably won't anytime soon, simply due to lack of human resources We highly appreciate contributions from our community.

My guess is that they backported patches which were merged into 6.13 and still in the pipeline. It is still on decision if we want to go through the pain backporting HDMI stuff to 6.12 LTS (our current) or simply drop everything related to that and tell users to follow edge (or stick with vendor which works very well) which will be 6.13, 6.14 and so on until a new LTS kernel is released. For server applications stability is more critical and HDMI is not needed there in most cases.

Yes you missed it https://github.com/armbian/community/releases/tag/25.2.0-trunk.266

Yes, apologies. I forgot that KERNEL_CONFIGURE is also deprecated. Anyway there is a nice write-up on how to deal with this the modern way: https://zuckerbude.org/armbian-using-kernel-config/

Fact is the Opi5, just like many other SBCs actually prefer being fed with slight over-voltage to compensate for losses across wiring and connectors. This is why, for example, the official PSU from RaspberryPi is labeled with 5.1 volts output and the official PSU from Orangepi, even though labaled as 5V actually outputs around 5.2 volts. The reason is that with such low voltages losses as mentioned across wiring and connectors become significant and the voltage will drop even further on load spikes. A while ago I did some measurements on my opi5 so I could experience and see the voltage drops by myself. For that I measured both output voltage at the PSU, which was 5.2 volts, and at on of the USB-A ports of the OPi5 which were at around 5.1 volts while the board being idle. 0.1 volts loss across wires, connectors and the PCB just for being powered on and doing nothing. Putting a heavy load on the board and the voltage dropped to something between 4.8 and 4.9 volts across everything except PSU which kept its voltage constant. At least my meter could not detect a drop higher than 10mV. Now thing about having a bad/crappy PSU. It is VERY likely that the voltage also breaks down directly at the source which adds up across the already mentioned losses. And boom, your board throws all kinds of issues which are hard to explain. Just because of undervoltage.

Is /boot/boot.env present?

Easiest is probably to copy the whole /boot directory. Make sure to adjust the UUID in armbianEnv.txt to match the target sdcard. Otherwise boot will probably stuck in initramfs. Use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } blkid to get the value.

mainline support is still under heavy development. Don't expect that 6.13 will magically make everything work properly. In fact for now the best - close to feature-complete - experience on this soc, rockchip sdk based kernel (6.1.y vendor to say) is the way to go until mainline is more matured. It took years for RK3399 to mature decently. The same is expected for RK3588 and its derivates. The only advantage there is this time, is the fact that collabora invests in its support and provides the development results for free as open source.

Have you tried with the image I linked above? This is based around updated rockchip sdk kernel.

Use vendor kernel based images, 6.1.y to say. I assume you tried mainline. Mainline images are known having incomplete hdmi support. This will be better once kernel 6.13 images are available. For even better experience check for images with mesa-vpu extension or build such by by yourself. Try these just for fun if you want: should include everything. 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 https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.02.0-trunk_Orangepi5_noble_vendor_6.1.84_kde-neon-kisak_desktop.img.xz

Easiest is probably to build a custom set of packages including headers. With the build framework this is quite simple. Clone repo https://github.com/armbian/build/ code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh BOARD=odroidn2 BRANCH=current KERNEL_CONFIGURE=no kernel Copy the debs from output/debs folder to the board and install them via code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dpkg -i

Change everything to known-good - sdcard - PSU - cables (!) - Armbian image If the behavior does not change the board is probably broken.

double-check which board you actually have so matching packages can be built. deprecated Never heard of that branch before. Try ./compile.sh BOARD=orangepizero3 KERNEL_CONFIGURE=yes kernel Adjust kernel config as needed. Check with Google or similar for necessary options to use KVM. Then check output/debs folder.

Have you read https://docs.armbian.com/User-Guide_Recovery/#replacing-boot ? There is also procedure how to extract the contents of .debs to the sdcard without chroot.

Hi, I don't there is a mechanism yet to just build this package. Because you are using an x86 machine and then the build framework uses cross compiling to create armhf/arm64 binaries.

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.