Well, I do think X11 is going to fall behind at some point if it continues to lack support of new things. I don't know the status for gaming on Wayland. I use lutris and wine to play WoW. Which doesn't yet work on these machines. Perhaps with 6.16. I'm an Xmonad user and I wouldn't touch gnome or kde with a ten foot pole. I'll use fvwm2 in a pinch. So far there isn't a "wm" on Wayland that compares to Xmonad, and I wouldn't use hypr land or any thing related to it for politics. Nasty people. Sway is the most promising at the moment, but it is too close to i3 which is too limited. There is no way Xmonad will become a compositor. So something has to happen. Not using 2 screens might be the easiest. I don't need two. But the Nanopi m6 has two. I can just get another without a screen and use this one as a server. Just living in the increasingly limited realm of X11 seems to be the thing to do unless I want to write a compositor. I've thought about adding compositing abilities to emacs. Someone has done a bit of that. Might be politically difficult to get it in. It would also mean writing a new Exwm. I'll just hang on to X because Wayland still doesn't meet my needs, and it has nothing capable of replacing what I have on X.

@emor acid Here's some information on H616/H618 ethernet phy. This is the 100Mbit ethernet built inside the H618 SOC. https://lore.kernel.org/linux-sunxi/20250526002924.2567843-1-james.hilliard1@gmail.com/T/#t In your dmesg log it shows your box is loading a generic phy. It should be loading the Allwinner phy. For example @NiTr0 logs above. Your box might be using a 1000Mbit external ethernet chip. If that's the case your dts settings will be very different. You'll need check if your box supports Gigabit Ethernet and find the Ethernet chip on your board. @NiTr0 Just freeze the kernel updates using armbian-config. My armbian build is unofficial so you can't use the official armbian kernels. I'm using patches created by warpme and my own custom patches. So the kernel update feature will not work. https://www.google.com/search?q=armbian+config+freeze+kernel&oq=armbian+config+freeze+kernel&gs_lcrp=EgZjaHJvbWUyBggAEEUYOdIBCDY4MDJqMGo3qAIAsAIA&sourceid=chrome&ie=UTF-8

This bug is not showing again with Trixie, and the repository labwc 0.8.3 (same), same orange pi zero 3, same HDMI monitor.

@Nick A here， compile with this patch +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +}; journalctl.log dmesg.log

First resize framebuffer to a convenient one and then start x11vnc xrandr --fb 1920x1080 -d :0 x11vnc -display :0