Werner

Use this one instead

This is expected for current. If it boots its good enough for server application. To make use of all the other hw features either wait a few years or try to make vendor kernel work.

I did a last minute fix when you read through the pr. Please test https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.05.0-trunk_Orangepi5-ultra_bookworm_current_6.12.17_minimal.img.xz

maybe related https://askubuntu.com/questions/1217252/boot-process-hangs-at-systemd-networkd-wait-online

moved

Well then there are two options, either use an older kernel with the image or try latest mainline. edge got bumped to 6.14.0-rc4 recently and desktop usage becomes better and better with it. Though no idea if these overlays are already present there.

I assume you mean device tree overlays rather than kernel modules. Sometimes due to naming scheme armbian-config does not detect available overlays for specific hardware correctly. You can check manually by looking into /boot/dtb/rockchip/overlay As for me with an 5+ and vendor kernel I have these available: test@orangepi5-plus:/boot/dtb/rockchip/overlay$ ls|grep -i i2c rk3576-i2c0-m1.dtbo rk3576-i2c1-m0.dtbo rk3576-i2c2-m0.dtbo rk3576-i2c3-m0.dtbo rk3576-i2c4-m3.dtbo rk3576-i2c5-m3.dtbo rk3576-i2c6-m0.dtbo rk3576-i2c7-m1.dtbo rk3576-i2c8-m2.dtbo rk3588-i2c0-m1.dtbo rk3588-i2c1-m0.dtbo rk3588-i2c1-m2.dtbo rk3588-i2c1-m4.dtbo rk3588-i2c2-m0.dtbo rk3588-i2c2-m4.dtbo rk3588-i2c3-m0.dtbo rk3588-i2c3-m1.dtbo rk3588-i2c4-m3.dtbo rk3588-i2c5-m3.dtbo rk3588-i2c6-m0.dtbo rk3588-i2c6-m3.dtbo rk3588-i2c6-m4.dtbo rk3588-i2c7-m3.dtbo rk3588-i2c8-m2.dtbo rk3588-i2c8-m4.dtbo rock-5a-i2c5-rtc-hym8563.dtbo test@orangepi5-plus:/boot/dtb/rockchip/overlay$ uname -a Linux orangepi5-plus 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux To enable an overlay edit /boot/armbianEnv.txt Edit: Yeah just checked, I bet if you rename (for example) rk3588-i2c2-m4.dtbo to rockchip-rk3588-i2c2-m4.dtbo it will pop up in armbian-config.

No. And I don't know further. Maybe anyone else got an idea. if you have a usb uart adapter you can grab u-boot log output while booting from serial console. It will tell whether the overlays are correctly loaded.

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

code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -U sends output to stdout instead of paste service

Having HDMI or video output work in U-Boot is more an exception rather than standard. While I don't know the reason I guess it is just too much effort to port such drivers into U-Boot while using the debug serial console is dirt cheap and always works.

There is also oldarchive: https://fi.mirror.armbian.de/oldarchive/odroidm1/archive/

Try an image with mesa-vpu extension present or build one. I think that ships a modified version to make use of hw acceleration better than stock.

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

Maybe firmware packages are frozen? Check with apt-mark showhold

agree, this doesn't make sense. Though I also wonder why it should not be included by default. I never ran into this issue and tried several minimal images on various boards...

Hi The logs you provided (besides that they're incomplete) are from u-boot and have nothing to do with OS level. it might be possible that u-boot supports the 2nd NIC but it is broken in kernel. Could be a device tree issue, could also be something else. I suggest to try the available kernel branches (legacy, current, edge) first to check if one of them works properly. You can use armbian-config to switch between kernels or swap sdcards with written Armbian images with various kernels beneath on. @jock has some insights in some older rockchips I think?

There is no log level 8. 7 is max https://linuxconfig.org/introduction-to-the-linux-kernel-log-levels

title updated to something that is actually useful

Latter.

Kernel versions might differ depending on hardware since board families have individual patchsets which might require specific Linux versions. If it is the same board then I think current has been bumped from 6.6.y to 6.12.y recently. You can try legacy instead if you need 6.6.y version. It is not possible to build a specific version like 6.7.2 because the patches Armbian puts on top of mainline kernel are following recent versions which means sooner or later some will break compilation. If you need a specific version you are on your own to specify the version necessary in the board configuration and fix issues that might occour.

since the full boot log is missing in armbianmonitor output can you check or provide (like from kern.log) if the uart devices are actually loaded or mentioned during boot? overlay prefix and names looking good.

Would you mind providing me with the contents of /boot/armbianEnv.txt?

Unfortunately no. But this is basically what happens while building when this extension is enabled: https://github.com/armbian/build/blob/main/extensions/mesa-vpu.sh

At this time I bet it will work better with vendor kernel since it is close to feature-complete while mainline is still under heavy development. But well, worth a try I guess.