Rui C Posted July 21 Posted July 21 (edited) Hi there I'm using Ubuntu 24.04 (Noble) KDE Neon image from may 26, 2025. After download this image and installing it, Wayland was working fine, not problems at all. Then, after a system upgrade, if i choose Wayland from session manager, the system freezes and i can't boot with Wayland, only X11... Before the update, the system was smooth, now it's really laggy....Like i said, i'm using Desktop image with Armbian Linux v6.12 KDE Neon (Ubuntu 24.04) There's something wrong with the update Anyone knows why is this happening, and any turnaround to use Wayland again? Edited July 21 by Rui C 0 Quote
Werner Posted July 21 Posted July 21 55 minutes ago, Rui C said: v6.12 Expected. tl;dr: use vendor or edge kernel and retry 0 Quote
Rui C Posted July 21 Author Posted July 21 Hi, Thanks a lot for your help. 👍 Indeed i'm using 6.12... Where can i find vendor or edge kernel? In another PC's i use mainline kernels without problems, but i think that can't be used on arm system... Once again, many thanks 0 Quote
Werner Posted July 21 Posted July 21 Just now, Rui C said: but i think that can't be used on arm system... Well yes and no. This depends in board family and how well support is matured. In case of rk3588 support is very basic. This is also an LTS kernel which means no new features will be available and only security fixes will be applied. Enhanced hdmi support is available in edge kernel and also in rockchip bsp which we call vendor. If the system is accessible via terminal or ssh, use armbian-config to switch kernels. Otherwise - if available - download an image matching DE and kernel or use the build framework to build your own. 0 Quote
Rui C Posted July 21 Author Posted July 21 Hi, again, Once again, thanks for your help. Well, change to edge kernel, and no joy... Gonna try a vendor kernel... Don't know if the problem is kernel related or files, since this happened when i just received the update... 0 Quote
Werner Posted July 21 Posted July 21 Well other option is the upstream broke somehow. KDE neon is based on their testing branch so if there is a faulty package uploaded desktop breaks. Though we won't dive into this since KDE is no officially supported desktop environment by us. We mostly do GNOME and XFCE only. We don't have resources to deal with more while we wish we would/could. 0 Quote
JFL Posted July 22 Posted July 22 Device: Opi5-Plus Armbian Image: Armbian_25.5.1_Orangepi5-plus_noble_vendor_6.1.115_kde-neon_desktop.img.xz Upgraded successfully and reboot up with no issue on Wayland session. Operating System: Ubuntu 24.04 KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.1 Kernel Version: 6.1.115-vendor-rk35xx (64-bit) Graphics Platform: Wayland Processors: 4 × ARM Cortex-A55, 4 × ARM Cortex-A76 Memory: 15.6 GiB of usable RAM Graphics Processor 1: Mali-G610 Graphics Processor 2: Mali-G610 Graphics Processor 3: llvmpipe Product Name: Orange Pi 5 Plus 0 Quote
Михаил Шестаков Posted July 23 Posted July 23 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. 0 Quote
Михаил Шестаков Posted July 24 Posted July 24 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. 0 Quote
Михаил Шестаков Posted 6 hours ago Posted 6 hours ago 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? 0 Quote
Werner Posted 3 hours ago Posted 3 hours ago 2 hours ago, Михаил Шестаков said: How to fix it? 2 hours ago, Михаил Шестаков said: 6.12.44-current-rockchip64 Switch to edge or vendor kernel (latter either with panthor overlay or proprietary mali blobs). current is a bad choice for desktop usage. 0 Quote
Михаил Шестаков Posted 3 hours ago Posted 3 hours ago (edited) 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. Edited 3 hours ago by Михаил Шестаков 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.