Werner

Have you tried pre-built images? https://github.com/armbian/os/releases/tag/25.5.0-trunk.90 Edit: Ah, no edge images available. Could you please test this one? https://fi.mirror.armbian.de/.testing/Armbian-unofficial_25.05.0-trunk_Orangepi5_bookworm_edge_6.13.4_minimal.img.xz

Seems like your /boot/armbianEnv.txt is wrong Looking like this I assume? verbosity=1 bootlogo=true console=both overlay_prefix=rockchip-rk3588 overlays=panthor-gpu fdtfile=rockchip/rk3588s-orangepi-5.dtb rootdev=UUID=af265968-c707-4182-9419-ca767922fd72 rootfstype=ext4 fdt_overlays=rk3588-ov13850-c3 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Try something like this: verbosity=1 bootlogo=true console=both overlay_prefix=rockchip-rk3588 overlays=panthor-gpu ov13850-c3 fdtfile=rockchip/rk3588s-orangepi-5.dtb rootdev=UUID=af265968-c707-4182-9419-ca767922fd72 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

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

There is a major discrepancy. This is what it ideally looks like'ish: Interestingly the 3B seems to have some sort of rtc but I assume its worthless without a puffer battery connected. At least a connector for such is there.

Since this is userspace any Debian or Ubuntu manual how to do that should work: https://www.google.com/search?q=debian+set+time+and+date

Hi, I don't know the internal mechanism of the forum software but I guess its just fine. Thanks for letting us know though. Cheers

If the time offset is too large things like ntpdate might not work. Try setting manually. Also check date. Most sbcs don't have something like an RTC module or a battery to keep date.

https://github.com/armbian/build/pull/7856

Make sure your time is properly set.

Try building an image with vendor kernel and mesa-vpu extension enabled. Not sure if a pre-built one is available.

That seems like sw from vendor. eMMC onboard memory needs to be erased. Check docs, I don't know by heart how to do it. Maybe there is some pin that can be shorted to ground to disable it. Or there is some tools or flash mode to erase/skip it. Once eMMC is nuked booting from microsd should work just fine.

https://debug.armbian.de

Good to know. Moved to off-topic.

please test again.

Something isn't right, agree. Needs investigation. Until then feel free to use any mirror from here: https://docs.armbian.com/Mirrors/ For armbianmonitor you can use this workaround until we can get that one properly back up too: PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u paste.armbian.eu works too.

I suggested to split 5 and 5B again since one works well, the other not. If it cannot be fixed consequence will be dropping it to csc or eos.

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

That's quite odd since this is the exact 3rd party driver Armbian ships with its images. An older commit though. Needs to be tested if it can be pushed.

Unless OP is using EDKII there is no bios on RK3588 boards in general. We include this driver already? https://github.com/armbian/build/blob/main/lib/functions/compilation/patch/drivers_network.sh#L292

Depends on board. Some vendor hard-wire leds, other allow software control.

A fix was recently implemented to avoid kernel panic. Try building an image by yourself or use automated images from github.com/armbian/os or github.com/armbian/community

Yes. This patch has been sent upstream and is awaiting either rejection, correction or acceptance. Without reading through it properly I assume this is an attempt to fix the initial issue with the ethernet ports.

As mentioned it might be possible or not. Depends on board. Check /sys for keywords led and trigger. cat the trigger file/s to get an idea what values it accepts.

send pr. https://docs.armbian.com/Process_Contribute/

There are multiple lines starting with overlay= Put all in one line like overlays=uart1 uart2 uart3 uart4 i2s i2c whatever Make sure the enabled overlays don't share same GPIO pins. Check your boards datasheet/manual.