All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Llom <richard.llom@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] System Monitor cannot read sensors anymore
Date: Tue, 16 Dec 2014 23:10:22 +0000	[thread overview]
Message-ID: <m6qe4v$4n6$1@ger.gmane.org> (raw)
In-Reply-To: <m6bv17$gsp$1@ger.gmane.org>

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@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2014-12-16 23:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 11:26 [lm-sensors] System Monitor cannot read sensors anymore Richard Llom
2014-12-11 13:47 ` Jean Delvare
2014-12-11 15:06 ` Richard Llom
2014-12-12 16:36 ` Guenter Roeck
2014-12-16 23:10 ` Richard Llom [this message]
2014-12-17  3:01 ` Guenter Roeck
2014-12-17  3:12 ` Guenter Roeck
2014-12-17 10:01 ` Jean Delvare
2014-12-18 12:29 ` Richard Llom
2014-12-18 14:05 ` Guenter Roeck
2014-12-18 15:39 ` Jean Delvare
2014-12-18 15:41 ` Richard Llom
2014-12-18 15:49 ` Jean Delvare
2014-12-18 16:33 ` Richard Llom
2014-12-18 16:49 ` Jean Delvare
2014-12-18 18:17 ` Guenter Roeck
2014-12-18 19:03 ` Richard Llom
2014-12-19  0:34 ` Guenter Roeck
2014-12-19 13:34 ` Richard Llom
2014-12-19 14:03 ` Guenter Roeck
2014-12-21 21:22 ` Richard Llom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='m6qe4v$4n6$1@ger.gmane.org' \
    --to=richard.llom@gmail.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.