Bug 469298 - GPU-related stats fail to work with NVIDIA 530 driver
Summary: GPU-related stats fail to work with NVIDIA 530 driver
Status: RESOLVED DUPLICATE of bug 462512
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-03 07:35 UTC by starrah
Modified: 2023-05-03 10:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
The screenshot of observed result (50.96 KB, image/png)
2023-05-03 07:35 UTC, starrah
Details

Note You need to log in before you can comment on or make changes to this bug.
Description starrah 2023-05-03 07:35:03 UTC
Created attachment 158646 [details]
The screenshot of observed result

After I upgrade to NVIDIA driver version 530.41.03, the statistical numbers of GPU in system monitor is wrong.
The GPU utilization value is always 0%, the used VRAM value is always blank, the GPU temperature value is always 0°C,and the GPU frequency values are always 0Hz. Only two statistics work: GPU name and total VRAM.
Please see the screenshot in the attachment.


STEPS TO REPRODUCE
1.  Install nvidia proprietary driver version 530 (eg, on Kubuntu, `apt install nvidia-driver-530 nvidia-utils-530` ).
2.  Open the System Monitor. 
3. Click the "New Page" button in the left panel, to add a new page.
4. Configure the new page: add all sensors below `GPU/GPU1`, like temperature, frequency & VRAM.

OBSERVED RESULT
Please see the screenshot in the attachment.

EXPECTED RESULT
All sensors should output correct values, not 0% or 0°C.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel: 5.15.0-71-generic (amd64)
My GPU: NVIDIA RTX 2080 Ti
NVIDIA driver version: 530.41.03
Comment 1 starrah 2023-05-03 10:00:41 UTC
Seemed duplicate of 462512.

*** This bug has been marked as a duplicate of bug 462512 ***