https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #51 from Maciej Stanczew ---
> The point is that lm-sensor is already installed
Do you also have development headers installed?
> and i can't install libnl
Why?
It looks like you don't have your development environment set up correctly.
https://bugs.kde.org/show_bug.cgi?id=438318
patane...@outlook.it changed:
What|Removed |Added
CC||patane...@outlook.it
--- Comment #50
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #49 from David Redondo ---
The cpu temp is not shown in lmsensors plugin because it is in the CPU plugin
as I said multiple times
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
bq666 changed:
What|Removed |Added
CC||wojciech.gaud...@gmail.com
--- Comment #48 from bq666
https://bugs.kde.org/show_bug.cgi?id=438318
AM changed:
What|Removed |Added
CC||a.mor...@live.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #47 from David Redondo ---
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #46 from Martin ---
(In reply to diminom...@gmail.com from comment #45)
> (In reply to David Redondo from comment #44)
> > I am closing this bug since the original issue was fixed. If you have
> > another bug such as a missing GPU sensor
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #45 from diminom...@gmail.com ---
(In reply to David Redondo from comment #44)
> I am closing this bug since the original issue was fixed. If you have
> another bug such as a missing GPU sensor please file a new bug so we can act
> on it.
https://bugs.kde.org/show_bug.cgi?id=438318
David Redondo changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #44 from David Redondo ---
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #43 from Matthias Mueller ---
(In reply to David Redondo from comment #42)
> Because the bug report was about amd gpu sensors missing which was fixed
> with the commit mentioned in comment #16
It's not fixed for amdgpu either, as "power"
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #42 from David Redondo ---
Because the bug report was about amd gpu sensors missing which was fixed with
the commit mentioned in comment #16
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #41 from Martin ---
This is sensors output. The only way I can get CPU temp is k10temp-pci-00c3.
Blacklisting it seems like an obvious bug to me.
I'm not sure what temperatures reported by it8720-isa-0228 are. One seems like
temperature
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #40 from diminom...@gmail.com ---
hi! i like to know, why this bug is marked as resolved if the problem still
present?
thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
Martin changed:
What|Removed |Added
CC||martin...@gmx.com
--- Comment #39 from Martin ---
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #38 from diminom...@gmail.com ---
(In reply to Artem from comment #37)
> (In reply to diminom...@gmail.com from comment #36)
> > (In reply to Artem from comment #35)
> > > (In reply to Maciej Stanczew from comment #33)
> > > > there is a
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #37 from Artem ---
(In reply to diminom...@gmail.com from comment #36)
> (In reply to Artem from comment #35)
> > (In reply to Maciej Stanczew from comment #33)
> > > there is a simple blacklist in ksystemstats code
> >
> > It was so
https://bugs.kde.org/show_bug.cgi?id=438318
diminom...@gmail.com changed:
What|Removed |Added
CC||diminom...@gmail.com
--- Comment #36
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #35 from Artem ---
(In reply to Maciej Stanczew from comment #33)
> there is a simple blacklist in ksystemstats code
It was so simple... I am ashamed that I could not find it myself.
Thank you, this workaround will help me wait for the
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #34 from Shmerl ---
(In reply to Maciej Stanczew from comment #33)
> For anyone who just wants to get rid of filtering and use the hardware
> sensors directly, there is a simple blacklist in ksystemstats code
Thanks!
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #33 from Maciej Stanczew ---
Created attachment 143878
--> https://bugs.kde.org/attachment.cgi?id=143878=edit
Remove blacklist in lmsensors plugin
For anyone who just wants to get rid of filtering and use the hardware sensors
directly,
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #32 from Matthias Mueller ---
(In reply to David Redondo from comment #31)
> The power1 sensor in the outputs? Let's create a new issue anyways since
> were we can collect relevant info since it's slightly different that it
> should be now
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #31 from David Redondo ---
The power1 sensor in the outputs? Let's create a new issue anyways since were
we can collect relevant info since it's slightly different that it should be
now there but isn't.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #30 from Matthias Mueller ---
(In reply to David Redondo from comment #29)
> To clarify we do not skip any sensors for gpus anymore, all GPU sensors are
> exposed under GPU, closing this because of that.
> As this bug is about GPU I am
https://bugs.kde.org/show_bug.cgi?id=438318
David Redondo changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #28 from Shmerl ---
Looks like the whole thing is built on top of libksysguard, so I need to figure
out how to filters sensors from there to skip ones for CPU and GPU.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #27 from Shmerl ---
I'll take a look into making a patch that simply removes this filtering.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #26 from Sebastian E. ---
KSysGuard and KDE System Monitor are system utilities, and as such should first
and foremost display system information as it is. Any processing that helps to
better dig through and display that information is a
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #25 from Shmerl ---
(In reply to Ilia Kats from comment #24)
> I'm all for making KDE beginner-friendly, but it shouldn't be at the cost of
> advanced users. Perhaps there can be an option, off by default, to show all
> the sensors under
https://bugs.kde.org/show_bug.cgi?id=438318
p3dima...@hotmail.it changed:
What|Removed |Added
CC||p3dima...@hotmail.it
--
You are
https://bugs.kde.org/show_bug.cgi?id=438318
Ilia Kats changed:
What|Removed |Added
CC||ilia-k...@gmx.net
--- Comment #24 from Ilia Kats
https://bugs.kde.org/show_bug.cgi?id=438318
Oscar Fuentes changed:
What|Removed |Added
CC||bugs-...@axeitado.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438318
Matthias Mueller changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #22 from Artem ---
Exactly the same problem, I am missing the coretemp-isa- sensor to measure
the temperature of my entire Intel processor, not each core individually. I was
hoping that with the release of Plasma 5.23 the problem will
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #21 from Shmerl ---
For now I'm sticking to ksysguard which is not enforcing any pointless
artificial limitations like that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #20 from Shmerl ---
I can confirm that power consumption isn't being picked up from lm sensors for
amdgpu.
Here is what I see when running sensors:
amdgpu-pci-0f00
Adapter: PCI adapter
vddgfx:6.00 mV
fan1: 0 RPM (min =
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #19 from Sebastian E. ---
What about k10temp? I have a Pie Chart System Monitor Sensor in my bottom panel
which used to display Tctl, until it unfortunately stopped working after an
update. I left it there, hoping it would work again after
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #18 from Shmerl ---
I hold there still should be a way to add any kind of sensors, not filtering
GPU ones out on purpose.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #17 from tgnff...@gmail.com ---
Was this patch supposed to also make the power(watt) monitor/sensor available?
If so, the bug should be reopened, as it seems to still be hidden.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=438318
Paul Sadauskas changed:
What|Removed |Added
CC||p...@sadauskas.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=438318
David Redondo changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #15 from Matthias Mueller ---
i agree that filtered choice as the only option isn't the best way to go -
maybe add a checkbox "display raw sensor data" or something to still have the
filtered few for less confusion for not-so-tech-savvy
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #14 from Shmerl ---
To give another example. Imagine, tomorrow k10temp and amdgpu will add another
metric. Since CPU / GPU UI doesn't anticipate it, it will be missing there
until you implement it. While if you simply read all that sensors
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #13 from Shmerl ---
(In reply to David Redondo from comment #6)
> The cause of the problem is, that in the new sensors plugin coretemp,
> k10temp and amdgpu are intentionally excluded to not expose duplicated
> sensors because these are
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #12 from Maciej Stanczew ---
My usecases for all of the filtered drivers:
coretemp: Similarly to what Artem mentioned, I'm interested in package
temperature, not per-core temperatures.
k10temp: Ryzen CPUs have a peculiar way of reporting
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #11 from David Redondo ---
This bug report is sufficient to track the issue
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #10 from Artem ---
David Redondo, that is, can we expect that this will be fixed after some time?
Should I start a separate issue on GitLab, or is it enough just to observe the
current development?
I doubt that I will be able to implement
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #9 from David Redondo ---
Thanks Artem, that's a good idea.
> PCI-adresses is nothing that can be done in userspace but has to be patched
> in? Or am i missing something?
Yes it has to be done in the code.
I mentioned it because I am
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #8 from Matthias Mueller ---
My usecase is/was monitoring the GPU-Power - i guess the mentioned mapping of
PCI-adresses is nothing that can be done in userspace but has to be patched in?
Or am i missing something?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438318
--- Comment #7 from Artem ---
Well, I would like to have the correct information about the CPU temperature.
The "sensors" command shows that the temperatures of the processor in general
and specific cores in particular may differ, so using the
https://bugs.kde.org/show_bug.cgi?id=438318
David Redondo changed:
What|Removed |Added
CC||k...@david-redondo.de
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=438318
Artem changed:
What|Removed |Added
CC||kde_bts@knebergish.fastmail
|
https://bugs.kde.org/show_bug.cgi?id=438318
Michal Kec (MiK) changed:
What|Removed |Added
CC||k...@kecnet.cz
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=438318
Arjen Hiemstra changed:
What|Removed |Added
CC||shtetl...@gmail.com
--- Comment #4 from Arjen
https://bugs.kde.org/show_bug.cgi?id=438318
tgnff...@gmail.com changed:
What|Removed |Added
CC||tgnff...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438318
Matthias Mueller changed:
What|Removed |Added
CC||mat.muel...@mailbox.org
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=438318
Sebastian E. changed:
What|Removed |Added
CC||kde-b...@foobarlibre.net
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=438318
Maciej Stanczew changed:
What|Removed |Added
CC||maciej.stancze...@gmail.com
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=438318
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Keywords|
https://bugs.kde.org/show_bug.cgi?id=438318
nttkde changed:
What|Removed |Added
CC||watisthis...@outlook.com
--- Comment #1 from nttkde
59 matches
Mail list logo
