Re: System Monitor cannot read sensors anymore

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jean,
thanks for your prompt answer!

Jean Delvare wrote:
> On Thu, 11 Dec 2014 12:26:30 +0100, Richard Llom wrote:
>> Hi,
>> after a recent kernel update to 3.17.4 in my distro I can't read my
>> sensors anymore with my beloved ksysguard (/System Monitor). Strange
>> thing is, I can still see the sensors with "sensors" (see below).
>> 
>> So I was wondering if something changed with this kernel or if there are
>> known issues?
> 
> We are in the process of converting many drivers to have their
> attributes attached to the hwmon class device instead of the physical
> device. Any application not relying on libsensors may get confused by
> this change. We had reports of this happening already. That being said,
> the drivers you are using have not been converted in 3.17. k10temp was
> converted in 3.18, while it87 was not converted yet. So I'm a bit
> confused. Plus I think ksysguard is using libsensors anyway. Which
> verions of ksysguard and libsensors are you using?
> 
System Monitor Version 4.11.14
Using KDE Development Platform 4.14.3

pacman -Qo /usr/lib/libsensors.so.4.3.2
/usr/lib/libsensors.so.4.3.2 is owned by lm_sensors 3.3.5-1

>> What daemon/service (?) is responsible for providing the sensor data to
>> programs? How can I check if it is running correctly?
> 
> No service is doing that. The information is available in sysfs, and
> libsensors gets it from there and makes it available to applications in
> an easy way.
> 
Where exactly in /sys ? Because here I can't find anything there related to 
my sensors...

> I'm not too sure how to debug this further. Can you describe the
> symptoms better?
> 
Well, ksysguard comes with a "Sensor Browser", you can find it in a new tab 
(File -> New Tab). In this sensor browser I had the very same sensors 
provided by "sensors" e.g.
nouveau-pci-0100
∟ temp1
k10temp-pci-00c3
∟ temp1
it8720-isa-0228
∟ fan1
∟ fan2
∟ fan3
∟ in0
∟ ...
But not so after the update anymore...
There are still other sensors (CPU Load, Disk, Network, etc...) which still 
work.

> Can you run ksysguard from a terminal and see if it's
> spitting any error message (or logging them somewhere maybe?)
> 
This is the output from the terminal
ksysguard(3168) KSGRD::SensorAgent::processAnswer: Received UNKNOWN COMMAND 
for:  "lmsensors/k10temp-pci-00c3/temp1?"
ksysguard(3168) KSGRD::SensorAgent::processAnswer: Received UNKNOWN COMMAND 
for:  "lmsensors/it8720-isa-0228/temp1?"
ksysguard(3168) KSGRD::SensorAgent::processAnswer: Received UNKNOWN COMMAND 
for:  "lmsensors/nouveau-pci-0100/temp1?"
ksysguard(3168) KSGRD::SensorAgent::processAnswer: Received UNKNOWN COMMAND 
for:  "lmsensors/it8720-isa-0228/fan1?"
ksysguard(3168) KSGRD::SensorAgent::processAnswer: Received UNKNOWN COMMAND 
for:  "lmsensors/it8720-isa-0228/fan2?"
...


cheers
richard


_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux