Without the cma-384 I can run at 1920x1080 without issue, but when using a 4K monior I must increase the video memory or I get weird video issues and kde crashes. I am unsure if setting it up to cma-512 is beneficial or not. I suspect 512 is better for 4K, with 384 being the minimum.
You can run:
$ cat /proc/meminfo
At the bottom there are two lines concerning the CMA. CmaFree shows available video memory and this number changes as you run apps.
I think you need hdmi_group in addition to the hdmi_mode. If your hdmi cable is bi-directional, I would try removing the hdmi_mode and let the driver read the TV/monitor.
Yeah I did. I’m wonder if it could have any issues with the color space? I had UHD color set on the TV but just turned it off. no change. tvservice reports state 0xa [HDMI CUSTOM RGB lim 16:9], 3840x2160 @ 60.00Hz, progressive
Trying to decode the edid again.
I even tried switching to testing, updating, and tried installing QT6.
I know I’m being picky and can just switch to conky or run XFCE instead, but I’m hoping that I found some kind of bug and can help out the community if we can get it solved.
Running plasmapkg2 --type=KSysguard/SensorFace --list -g on both my virtualbox install and my RPi4:
Virtualbox:
[mike@gamma ~]$ plasmapkg2 --type=KSysguard/SensorFace --list -g
Listing service types: KSysguard/SensorFace in /usr/share/ksysguard/sensorfaces/
org.kde.ksysguard.barchart
org.kde.ksysguard.horizontalbars
org.kde.ksysguard.linechart
org.kde.ksysguard.piechart
org.kde.ksysguard.textonly
RPi4:
[mike@tittysprinkles org.kde.ksysguard.linechart]$ plasmapkg2 --type=KSysguard/SensorFace --list -g
Listing service types: KSysguard/SensorFace in /usr/share/ksysguard/sensorfaces/
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.barchart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.horizontalbars/metadata.desktop"
org.kde.ksysguard.barchart
org.kde.ksysguard.horizontalbars
org.kde.ksysguard.linechart
org.kde.ksysguard.piechart
org.kde.ksysguard.textonly
I cannot believe it… I got the thumbnails to show up in add widgets. However in all my testing, I broke the system monitor widgets lmao. I know I made progress because the Y-axis bars are there in the widget.
What I think finally fixed it was the commenting out QT_QUICK_BACKEND in /etc/environment but I changed that after I installed mesa-git and vulkan-tools. The problem is I also updated pretty much everything else to the -git variants. At least all of KDE, KF5 and plasma.
I also updated my config.txt to have gpu_mem=128 and cma-512 so TBH I don’t know what fixed it, but without doing a complete reflash I won’t know which one actually fixed it.
I’m going to reflash again fresh, stay on stable, update everything, and change just that to see if that does it.
We are working on a plymouth screen, but yes, we will do this by default now. Last we tested, hardware acceleration didn’t work on the V3D driver yet. But I tested some stuff the last couple of days and seems to work pretty well now.