From: mhoffman@lightlink.com (Mark M. Hoffman)
To: lm-sensors@vger.kernel.org
Subject: ticket 1415
Date: Thu, 19 May 2005 06:24:22 +0000 [thread overview]
Message-ID: <20031023043830.GA4097@earth.solarsys.private> (raw)
In-Reply-To: <3F95168B.5040305@yahoo.com.au>
Hi Trevor:
* TN <tnuro@yahoo.com.au> [2003-10-23 09:52:02 +1000]:
> success.......I got the latest from cvs and sure enough, numbers! I'm
> not sure about a couple of these (ie. the voltage sensors seem to have 1
> or 2 weirdnesses about them), but it appears to be working. The fan
> speed & temperatures seem to make sense and change in a sensible manner
> (speed increases as temperature increases)
OK, first of all... I've committed another change to CVS. You should now
see in1, fan3, and temp3 which we didn't see before.
For my P4C800E, I know these things for sure:
chip "w83627thf-*"
label fan1 "Chassis Fan"
label fan2 "CPU Fan"
label fan3 "Power Fan"
I'm also assuming these:
label temp1 "MB Temp"
label temp2 "CPU Temp"
label temp3 "PWR Temp"
# PWR Temp is the 2 pin connector on the mainboard
# unless you've actually connected a sensor...
ignore temp3
I can't say anything about inX yet.
> One thing I've noticed is that on my physically accessible servers, the
> temp readings seldom agree with the bios readings.....is there a
> calivration process I need to go through ?
Yes, if possible. There is no way for us to automate this. Check
/etc/sensors.conf for examples. OTOH, if you're patient you can just wait
for me to do it. ;) I have the feeling that more source code changes are
necessary yet anyway.
BTW my temp1/MB actually looks pretty good; it's the temp2/CPU that's low
by ~6C compared to BIOS. It's also possible that neither is lying - if the
BIOS sits in a tight loop it could cause the CPU to heat up as compared to
a mostly idle/halted CPU running Linux.
Regards,
--
Mark M. Hoffman
mhoffman@lightlink.com
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 ticket 1415 T Nuro
2005-05-19 6:24 ` TN
2005-05-19 6:24 ` TN
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark M. Hoffman [this message]
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` TN
2005-05-19 6:24 ` TN
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=20031023043830.GA4097@earth.solarsys.private \
--to=mhoffman@lightlink.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.