From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] bogus data from W83627HF on an ASRock K7S41
Date: Thu, 16 Jun 2005 19:56:30 +0000 [thread overview]
Message-ID: <20050616195541.2ffca10a.khali@linux-fr.org> (raw)
Hi David,
Sorry for the delay.
> I've just started to play with lm-sensors, and have almost got it
> working... however, I'm getting some bogus values, and some others are
> missing:
> - -12V is bogus
FAQ 4.6.1
"-5V and -12V readings are way out of range!
It's very frequent that negative voltage lines are not wired because
motherboard manufacturers don't think they're worth monitoring (they are
mostly unused these days). You can just add ignore inN lines to
/etc/sensors.conf to hide them."
Another possibility is that these lines are used to monitor different
voltages. If this is the case, only the motherboard manufacturer can
tell, or maybe you can have a look at what voltage values your BIOS
displays, if any.
> - Vbat looks bogus
Maybe it's simply not wired. Same rules apply as for negative voltages.
> - fan1 and fan2 both zero (even though 1 fan is installed and turning)
FAQ 4.1.1
"Fans sometimes/always read 0!!
You may not have a three-wire fan, which is required.
You may need to increase the 'fan divisor'. See doc/fan-divisors in our
package for further information."
> My motherboard is an ASRock K7S41, and the sensor appears to be a
> S83627HF
In fact it appears to be a W83697HF. All these chips have very similar
names but slightly different feature sets, so you should be careful when
announcing the name of your chip.
> ????? Why is the algorithm unavailable
Because the Linux 2.6 i2c layer doesn't provide an access to it. I tend
to think we should stop displaying it, as more people are now using 2.6
kernels and it is confusing. Nobody really cares about the algorithm,
it's an internal implementation detail.
--
Jean Delvare
reply other threads:[~2005-06-16 19:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050616195541.2ffca10a.khali@linux-fr.org \
--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.