Summary: | GPU Information for Dedicated NVIDIA GPU not showing on widget or plasma system monitor application. | ||
---|---|---|---|
Product: | [Applications] plasma-systemmonitor | Reporter: | n1ghtf4l1 <anubhavde2002> |
Component: | general | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 1koylrj4, ahiemstra, dashonwwIII, mason2371, nate, plasma-bugs, rockingcat, trm109 |
Priority: | NOR | Keywords: | regression |
Version: | 5.26.2 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=461389 | ||
Latest Commit: | https://invent.kde.org/plasma/ksystemstats/commit/00b1f21b0fe8164c4bcda9109e08bf7a69c0ce24 | Version Fixed In: | 5.27 |
Sentry Crash Report: |
Description
n1ghtf4l1
2022-11-03 14:21:13 UTC
I am having the same issue; System Monitor is unable to display details about my NVIDIA dGPU (reports default stats; 0C, 0%, etc.), but my AMD iGPU reports just fine. (In my laptop, amd is 'GPU 1' and nvidia is 'GPU 2') nvidia-smi is functioning as intended. The 'GPU Name' sensor correctly reports my iGPU's name as 'Rembrandt [Radeon 680m', but incorrectly reports my dGPU as 'GPU 2' Hardware: Laptop: ASUS Flow X16 CPU: AMD Ryzen 7 6800HS with Radeon Graphics (16) @ 3.200GHz GPUs: AMD Rembrandt Radeon 680M, NVIDIA RTX 3060 Mobile / Max-Q Software: OS: Arch Linux x86_64 Kernel: 6.0.6-arch1-1 DE: Plasma 5.26.2 WM: Kwin Nvidia Driver: 520.56.06 Additional information: $ plasma-systemmonitor --version plasma-systemmonitor 5.26.2 As of writing this post, all installed packages are up-to-date. If any other datapoints are required to pinpoint this issue, let me know, I'd be happy to provide more info. *** This bug has been marked as a duplicate of bug 461389 *** (In reply to Nate Graham from comment #2) > > *** This bug has been marked as a duplicate of bug 461389 *** In bug 461389 gpu name for dedicated nvidia gpu changed from gpu 0 to 1 but in my case as well as @saik's case it changed from gpu 1 to 2. As a result default values are shown i.e 0%, 0 degree C etc. I believe there is some error in the update which mistakenly changed gpu name from 1 to 2 as a result of which system can't find gpu 2 hence displaying default values. If somehow we can change gpu name of our dedicated nvidia gpu from gpu2 to gpu1, i think problem will be solved. In bug 461389, NVIDIA gpu was set as primary gpu, but in my case intel gpu is set as primary gpu. Even though expected result is same, conditions are different. (In reply to n1ghtf4l1 from comment #3) > In bug 461389, NVIDIA gpu was set as primary gpu, but in my case intel gpu > is set as primary gpu. Even though expected result is same, conditions are > different. Before I updated the system, I've also set Intel as primary GPU. I think it has caused the name change of Nvidia GPU. (In reply to n1ghtf4l1 from comment #3) > In bug 461389 gpu name for dedicated nvidia gpu changed from gpu 0 to 1 but > in my case as well as @saik's case it changed from gpu 1 to 2. I think we're talking about the same thing. In the widget settings and in System Monitor, the GPU name has changed from "GPU 1" to "GPU 2" for me as well. But if you look for example in `~/.config/plasma-org.kde.plasma.desktop-appletsrc`, you'll probably find the paths to GPU sensors like `gpu/gpu1/usage`. So for "GPU 2" in the widget settings, the config name is "gpu1". Git commit 00b1f21b0fe8164c4bcda9109e08bf7a69c0ce24 by David Redondo. Committed on 09/01/2023 at 12:48. Pushed by davidre into branch 'master'. plugins/gpu: Use pci address to identify nvidia gpus The DRM index does not correspond to the nvidia index. Identify cards by their pci addresses and derive the index from the position in the query. Related: bug 463033 FIXED-IN:5.27 M +1 -1 plugins/gpu/LinuxBackend.cpp M +19 -13 plugins/gpu/LinuxNvidiaGpu.cpp M +5 -2 plugins/gpu/LinuxNvidiaGpu.h M +2 -0 plugins/gpu/NvidiaSmiProcess.cpp M +1 -0 plugins/gpu/NvidiaSmiProcess.h M +1 -1 plugins/network/NetworkManagerBackend.cpp https://invent.kde.org/plasma/ksystemstats/commit/00b1f21b0fe8164c4bcda9109e08bf7a69c0ce24 this issue seems to be back with latest nvidia driver 535.54.03 That's Bug 470474. Please don't re-open old bug reports; always create a new one. Thanks! |