Yes. This is an example of a rk3588 based board of mine: overlay_prefix=rockchip-rk3588 overlays=panthor-gpu opp-oc-24ghz The overlay names come from /boot/dtb/*/ find an overlay matching your soc and needs and enable by putting its name to overlays=. Then reboot. Having a serial console to read uboot logs can show if it has been loaded properly or in case it did not why.

This is the default configuration: verbosity=1 bootlogo=false console=both extraargs=cma=256M overlay_prefix=rk35xx fdtfile=rockchip/rk3566-radxa-zero3.dtb rootdev=UUID=526007c3-3a0f-451d-a7a7-6d896d15f910 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Update: I just ran Ubuntu 13 (25.10 (development branch)), downloaded from their site (not Armbian), running their kernel. There I installed KDE Plasma 6.. Wayland performance was excellent. The bug I described here didn't show up at all. This version of Ubuntu seems more similar to Trixie than Bookworm. And some of their related package names, like Trixie's, did seem to mention porting from QT5 to QT6. So whatever bug is existing in Trixie was either not created, skipped, or solved by Ubuntu. Operating System: Ubuntu 13 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.17.0 Qt Version: 6.8.3 Kernel Version: 6.16.0-13-generic (64-bit) Graphics Platform: Wayland

Hi there, Then I would advise to try to: bridge NIC1 and NIC2, then configure the resulting bridge interface br0 to 192.168.100.101/24 configure 'device 1' to 192.168.100.102/24 or some other IP address that does not overlap/conflict with any other device on the 192.168.100.0/24 network. This setup should present "one interface" to the 192.168.100.0/24 network, pulling 'device 1' into the network as it were. I'm not sure if you have to enable ip forwarding in case you create a bridge, my experience with bridge (both networking and card wise) is limited. Groetjes, Btw, there has to be a reason why PC1 and the gateway/router in the red box are not able to be changed 😉 Perhaps the people that set it up that way were actively trying to prevent fanning out into different additional networks. (I know many employers do not allow this on their office network for example, for very good reasons...)

Well I was able to build by changing the docker image with this option : DOCKER_ARMBIAN_BASE_IMAGE=ubuntu:jammy The two other images (debian:bookworm and ubuntu:noble) simply do not work