Михаил Шестаков

Thank you so much for your help and explaining how it should work! I tried all the cores that you ordered - it only worked on this: #unnamed -a Linux orangepi5-plus 6.16.4-edge-rockchip64 #1 SMP PREEMPT Thu Aug 28 14:34:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux I put it like this: @apt install linux-image-edge-rockchip64 linux-headers-edge-rockchip64 The old cores were not suitable because the wifi card 0002:21:00.0 Network controller: MEDIATEK Corp. Device 7925 refuses to run on cores less than 6.12.X I bow low to you! cat /boot/armbianEnv.txt verbosity=1 bootlogo=true console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=e08e0355-09a7-41ad-a6db-fa17566a7f12 rootfstype=ext4 extraargs=cma=1G usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u With the extraargs=cma=1G parameter, videos in the browser somehow load faster.

In the afternoon, I decided to look at dmesg. There: 25.729785] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 7307264 bytes), total 32768 (slots), used 11243 (slots) [ 25.734888] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1740800 bytes), total 32768 (slots), used 9297 (slots) [ 26.197594] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1150976 bytes), total 32768 (slots), used 10017 (slots) [ 26.875802] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 7307264 bytes), total 32768 (slots), used 11243 (slots) [ 26.884778] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 2097152 bytes), total 32768 (slots), used 11759 (slots) [ 27.976904] swiotlb_tbl_map_single: 1 callbacks suppressed [ 27.976917] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 2940928 bytes), total 32768 (slots), used 9787 (slots) [ 28.798413] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 438272 bytes), total 32768 (slots), used 9819 (slots) [ 30.420185] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 7307264 bytes), total 32768 (slots), used 11735 (slots) [ 30.423002] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1642496 bytes), total 32768 (slots), used 9841 (slots) [ 99.648400] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[30] not 4 pixel aligned [ 99.665159] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[29] not 4 pixel aligned [ 99.681872] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[25] not 4 pixel aligned and there: 911.698942] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[22] not 4 pixel aligned [ 911.715603] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[21] not 4 pixel aligned [ 912.032227] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[21] not 4 pixel aligned [ 912.065671] rockchip-drm display-subsystem: [drm] *ERROR* vp0 Cluster1-win0 actual_w[26] not 4 pixel aligned root@orangepi5-plus:/etc/default# dmesg | grep -i "swiotlb" # Nameless -ah Linux orangepi5-plus 6.12.44-current-rockchip64 #1 OUTPUTS SMP, August 28, 14:31:16 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux at 14:00 local time. # cat /boot/armbianEnv.txt verbosity=1 bootlogo=true console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb rootdev=UUID=e08e0355-09a7-41ad-a6db-fa17566a7f12 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u How to fix it?

Colleagues, in order to fully cover the topic and make it easier to diagnose such problems in the future, please tell us what methods and where to look for information/logs about Wayland failures.

Hurray Wayland is fixed! Thank you very much! You have no idea how important this is! I for example use this setup on a permanent basis: Web surfing, Text editors, etc. This is my main system. And you know how upset I was when the Wayland subsystem broke.