Werner

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.

I noticed it is applied somewhere between the existing patches. Have you tried to rename it to something like zzzz_yourpatchfile.patch so, since they are ordered alphabetically, it is applied at the very end, just like your chances have been made with all the previous patches already applied.

Maybe this is why:https://patchwork.kernel.org/project/linux-rockchip/patch/20241220163227.1501912-1-alicja.michalska@9elements.com/

moved If it is a 1:1 clone of opi pc check if i2s overlay is enabled. Try armbian-config or the manual way by setting in /boot/armbianEnv.txt Check /boot subfolders for available overlays.

There is no package simply called qemu: https://packages.debian.org/search?keywords=qemu&searchon=names&suite=bookworm&section=all

Debian has some weird behaviour when using "su" because $PATH lacks /sbin for whatever reason. /sbin/chroot instead of chroot might work

If somebody adds support for it, why not? https://www.cnx-software.com/2024/12/21/rockchip-rk3588-mainline-linux-support-current-status-and-future-work-for-2025/ tl;dr: even if rk abandons it seems like collabora will continue.

Isn't the hdmirx on rk3588 able to do 4k60? https://www.rock-chips.com/uploads/pdf/2022.8.26/192/RK3588 Brief Datasheet.pdf