Re: System Monitor cannot read sensors anymore

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

 



Guenter Roeck wrote:
> On Thu, Dec 11, 2014 at 04:06:02PM +0100, Richard Llom wrote:
>> Jean Delvare wrote:
>>> On Thu, 11 Dec 2014 12:26:30 +0100, Richard Llom wrote:
>>>> 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).
>>>> 
>>> 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?"
>> ...
>> 
> FWIW, I tried ksysguard with a 3.18 kernel and did not see any problems.
> I currently have acpitz-virtual, coretemp, nct6792, max6695, tmp435, and
> tmp451 connected to the system. I tried with Ubuntu 14.04 and 14.10.
> 
I tried it with a former kernel (3.16) on a live session of chakra and it 
works there, too...


Is there any information on how to debug this further?


_______________________________________________
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