From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Creating alarm for fans
Date: Fri, 04 Sep 2009 15:17:01 +0000 [thread overview]
Message-ID: <20090904171701.1decd339@hyperion.delvare> (raw)
In-Reply-To: <4A9823A2.2010907@xtronics.com>
Hi Karl,
Please keep the list Cc'd.
On Thu, 03 Sep 2009 23:05:38 -0500, Karl Schmidt wrote:
> Jean Delvare wrote:
>
> >
> > This will dump all the device registers. I will then check against the
> > datasheet and see if I spot anything.
>
> I don't think this is a hardware problem - the readings make sense - where is it that the levels are
> compared to the set statements? This used to work on this computer until there was an upgrade to --
> I think version 3... Unless they are ignoring the set statements - thinking the chip will generate
> all alarms?
Alarms are computed by the chips in hardware. "sensors" merely reports
what the driver tells it to, and the driver in turn merely reports the
hardware state.
>
> I have a different machine - different sensors - same version of software and it works.
>
> I was trying things and listed out the working modules - if that might help:
>
> lsmod |grep dme
> dme1737 43168 0
> hwmon_vid 7296 2 dme1737,lm85
> i2c_core 27936 4 dme1737,eeprom,lm85,i2c_nforce2
>
> I tired loading different permutations of the modules - nothing seems to work.
>
>
> I tried purging the lm-sensors package and reinstalling... no joy?????
It is interesting that you have two full-featured hardware monitoring
chips in your system. I'm rather surprised, I admit.
I'll look at the dump you sent when I have a moment, but I have a lot
of work these days, so please be patient.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-09-04 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 18:36 [lm-sensors] Creating alarm for fans Karl Schmidt
2009-09-02 13:16 ` Jean Delvare
2009-09-02 16:41 ` Karl Schmidt
2009-09-02 16:49 ` Jean Delvare
2009-09-02 17:02 ` Karl Schmidt
2009-09-02 17:12 ` Mark E. Hansen
2009-09-02 19:06 ` Jean Delvare
2009-09-04 15:17 ` Jean Delvare [this message]
2009-09-04 21:40 ` Karl Schmidt
2009-09-05 12:23 ` Jean Delvare
2009-09-05 19:07 ` Karl Schmidt
2009-09-05 19:16 ` Karl Schmidt
2009-09-05 21:04 ` Jean Delvare
2009-09-05 21:10 ` Jean Delvare
2009-09-05 22:03 ` Karl Schmidt
2009-09-05 22:13 ` Karl Schmidt
2009-09-06 7:46 ` Jean Delvare
2009-09-06 8:21 ` Jean Delvare
2009-09-06 18:05 ` Karl Schmidt
2009-09-06 18:28 ` Karl Schmidt
2009-09-07 19:08 ` Karl Schmidt
2009-09-07 19:42 ` Jean Delvare
2009-09-10 7:56 ` Jean Delvare
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=20090904171701.1decd339@hyperion.delvare \
--to=khali@linux-fr.org \
--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.