From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] 5VSB computing on it87
Date: Tue, 12 May 2009 19:06:04 +0000 [thread overview]
Message-ID: <20090512210604.35ba4f16@hyperion.delvare> (raw)
In-Reply-To: <BLU120-W7191DFD982F4E48F88CBAD8630@phx.gbl>
On Tue, 12 May 2009 19:55:10 +0200, Mr. Tux wrote:
>
> Thank you Jean
>
> So, this sensor is not assigned correctly, I could life with that for the moment, but my problem
> is the alarm flag this sensors is causing, since the value for some reason is saturated.
>
> I'd like to put this sensor on ignore for the moment, but I don't know how to do that:
>
> *) ignore in7 - only prevents the sensor to be listed using the 'sensors' command
Not just the "sensors" command, but all problems using libsensors. And
all monitoring programs should use it.
> *) comment every line mentioning in7 in sensors3.conf - makes it appear under
> /sys/devices/plattform/[...]/ anyway ! With the alarm flag in "in7_alarm" set to 1 - I need to get rid
> of that...
This doesn't make any sense. Statements mentioning in7 for other chips
you do not have on your board have no effect for you in the first place.
> *) trying to set in7 to value 0 (= unused): 'set in7_type 0' causes a parse error with 'sensors -s'
You can't invent symbols like that. Only a few sensors have a
selectable type, thermal sensors mostly.
> *) trying to raise the max_value barrier switching on the alarm: 'set in7_max 7 * 1.05'
> this does not have an effect - the max limit stays at 6,.85, triggering the alarm!
Some chips to strict comparisons on limits and some do loose
comparisons. Apparently the IT87xxF chips do loose comparisons on upper
limits, so you're doomed. That's the reason why chip manufacturer
recommend to connect unused voltage inputs to the ground, a
recommendation your motherboard vendor did not follow - blame them!
> What else can I try? I need the alarm flag in /sys/devices/plattform/[...]/in7_alarm to
> be set to '0' - since I'm writing a small daemon who will parse for alarm values
> only, starting a speaker beep when a alarm is discovered.
Your small daemon should link with libsensors and use it's API, instead
of accessing /sys files directly. That way you can ignore faulty inputs
through /etc/sensors3.conf.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
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-05-12 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 8:07 [lm-sensors] 5VSB computing on it87 Mr. Tux
2009-05-11 8:55 ` Jean Delvare
2009-05-12 17:55 ` Mr. Tux
2009-05-12 18:57 ` Mark E. Hansen
2009-05-12 19:06 ` Jean Delvare [this message]
2009-05-12 19:07 ` Mark E. Hansen
2009-05-14 9:09 ` Mr. Tux
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=20090512210604.35ba4f16@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.