https://bugs.kde.org/show_bug.cgi?id=427603
Christoph Cullmann changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=427603
mason2...@gmail.com changed:
What|Removed |Added
CC||mason2...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #22 from Mathias Homann ---
(In reply to Erik Kurzinger from comment #19)
> If you do so, it would help if you could run the nvidia-bug-report.sh script
> that we distribute with the driver and attach the file it generates.
mail sent.
--
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #21 from Mathias Homann ---
Created attachment 133791
--> https://bugs.kde.org/attachment.cgi?id=133791&action=edit
nvidia bug report logfile
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #20 from Mathias Homann ---
I'm running glxspheres, and "nvidia-smi dmon" and "nvidia-smi pmon" both show
only zeros for sm,%, mem%, power consumption, and encoder/decoder usage, but
running "nvidia-smi" without any parameters shows the actu
https://bugs.kde.org/show_bug.cgi?id=427603
Henrique Sant'Anna changed:
What|Removed |Added
CC||hsanta...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #19 from Erik Kurzinger ---
Ok, that is strange. It's kind of a separate issue to this ksysguard bug,
though. Would you mind either sending an email to linux-b...@nvidia.com or
starting a thread on
https://forums.developer.nvidia.com/c/gpu-u
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #18 from Mathias Homann ---
(In reply to Mathias Homann from comment #17)
> (In reply to Erik Kurzinger from comment #14)
> > Bar1 is the portion of video memory that can be accessed by the CPU over
> > PCIe.
> >
> > And yes, a graphical de
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #17 from Mathias Homann ---
(In reply to Erik Kurzinger from comment #14)
> Bar1 is the portion of video memory that can be accessed by the CPU over
> PCIe.
>
> And yes, a graphical desktop environment would be expected to utilize GPU
> mem
https://bugs.kde.org/show_bug.cgi?id=427603
David Edmundson changed:
What|Removed |Added
Status|REOPENED|CONFIRMED
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=427603
David Edmundson changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #15 from Erik Kurzinger ---
sorry, forgot to answer this...
> and is there a way to have nvidia-smi report only the total framebuffer
> memory size?
no, I don't think so, sorry. You could always pipe its output through some
other tool lik
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #14 from Erik Kurzinger ---
Bar1 is the portion of video memory that can be accessed by the CPU over PCIe.
And yes, a graphical desktop environment would be expected to utilize GPU
memory bandwidth, but only if you're actually interacting w
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #13 from Mathias Homann ---
waitaminute. when you're running a graphical desktop with all kind of openGL
based eye candy, wouldn't the BANDWIDTH greater than zero?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #12 from Mathias Homann ---
...what is bar1?
and is there a way to have nvidia-smi report only the total framebuffer memory
size?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=427603
--- Comment #11 from Erik Kurzinger ---
The mem value reported by "nvidia-smi dmon" refers to memory bandwidth
utilization. If the GPU isn't actively rendering anything, it's normal for it
to be zero. It should increase if you run a game or something, t
https://bugs.kde.org/show_bug.cgi?id=427603
David Edmundson changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
17 matches
Mail list logo
