It seems an old error has crept back into Neon Plasma, and that is the GPU identification. Plasma is seeing my GPU as GPU 2, when it should be GPU 0. Consequently I can no longer get any telemetry (clocks, power, memory) from the GPU to the desktop widgets other than “usage”. Psensors and everything else that can talk to nvidia-smi is reporting correctly.
1 Like
I tried purging the nvidia driver and regressing it back to 550, but that made no difference. Deleting the desktop widget, then repopulating the sensors with GPU 2 values at least restored the functionality. I then renamed all the labels. I also had to reset all the sensors in System Monitor itself, as it too was no longer seeing GPU-0 (or 1).
Given all the other gpu and display identification related problems I have experienced of late, it seems this might be related.
Nvidia CP and Psensors see it is GPU-0, as it should be. Only Plasma sees it as GPU-2.
1 Like
aah that explains why my widget broke
I have 2 GPUs in my system, RX 6900XT and RTX 4060, with my 4060 bound to vfio-pci, so I initially thought it was detecting that
1 Like
Yeah, this happened last year too. A gpu count routine in the ksensors source started at 1 instead of zero which broke the widgets and system monitor.
Hello,
I have the same problem.
The interesting part is that KDE and neon developers don’t take this forum very seriously, I guess.
It is not only on neon Kernel 6.8 it is on Arch Kernel 6.6…-lts too.
Using KDE, and Nvidia for that matter, for years I am quite used to the Widget with the Nvidia GPU infos constantly brake and get fixed and brake again that I would rather consider this a non-issue because at least the (re-set) widgets / system info still works.
Maybe now that some parts of the Nvidia driver get open source that gets better?
But jokes aside.
The “real” Issue I have here is while I can select “GPU-2” aka Nvidia or “all GPUs” which shows exactly the same values as “GPU-2” my (Integrated) Intel GPU is not available at all.
Because this is my first Machine with dual GPUs I am not sure if that is normal for integrated GPUs but it seem odd especially because before I switched to Arch on the Ubuntu based TuxedoOS their “Control center” showed iGPU stats.
No, its not normal. The integrated GPU is possibly lost due to the count starting at 1. When this happened last year I was running dual nvidia cards and it would only see the secondary card and skipped the primary. It was a simple string error in ksensors. I will resubmit the bug report. It is curious though that it happened after the kernel update. Last time it happened during a plasma update. But giving nothing else is showing errors, it does indeed seem to be a plasma issue.
2 Likes
I have a Radeon and the same thing is happening. This does not seem to be a NVIDIA specific or proprietary driver issue.
2 Likes
Interesting. I think the error last year was a specific nvidia-smi function in Ksensors. If it is happening with AMD GPUs as well, then nvidia-smi has nothing to do with it. I find it curious that it happened (for me at least) with the kernel 6.8 upgrade. It is further curious as Psensors, NVCP, and Hardware Info all see it correctly - especially as as psensor and hardinfo are both very (8yrs) old.
After the latest kernel update, the places that should be GPU changed to “GPU 2” and the widgets and settings that I had set in the Plasma System Monitor were all broken.
When I changed the places from “GPU 2” to GPU, everything worked as it should.
1 Like
There have been a lot of issues with the kernel 6.8 on other platforms. Users of ZorinOS which uses Gnome43 have created numerous issues, as does Wayland. At least Plasma defaults to X11 and not Wayland. My current preferences for KDE is Q4OS and best of all PCLinuxOS with Plasma 5.27. Additionally, no systemd and no Discover. All updates are via Synaptic Package Manager. I also like the fact that Tiled Menu is preinstalled.
I’m confused. What issues were you referring to?
I did see a post about a Radeon 7000-series user not being able to boot reddit, but it could’ve been a Mesa thing (I have Tuxedo OS with newer Mesa packages so most likely I got lucky), but other than that, nothing else I can think of.
Ksensors seems to be misidentifying GPUs within System Monitor and desktop widgets, using the GPU-2 label instead of just GPU or GPU-0. The rest of the system sees it correctly.
1 Like