From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sis5595
Date: Tue, 12 Jun 2007 16:25:47 +0000 [thread overview]
Message-ID: <20070612182547.591ed2fa@hyperion.delvare> (raw)
In-Reply-To: <200307161427.08403.linux@1g6.biz>
Hi Ivo,
On Mon, 11 Jun 2007 18:21:13 +0200, Ivo Manca wrote:
> in4: +3.55 V (min = +0.00 V, max = +0.00 V) ALARM
>
> after md5sum:
> [root@localhost ivo]# sensors -c sensors-PCChips
> (...)
> in4: +0.19 V (min = +0.00 V, max = +0.00 V) ALARM
>
> Seems like in4 dropped completely?
> Wait: it seemed like a flatcable dropped on the fan, and stopped it
> spinning. So I guess +0,19V is suppose to say "Way to hot: you're burning
> your fingers!"? (Since I actually did burn my finger)
>
> But one minute after the fan started spinning again...
> (...)
> in4: +0.00 V (min = +0.00 V, max = +0.00 V) ALARM
>
> And 30 seconds later:
> (...)
> in4: +4.03 V (min = +0.00 V, max = +0.00 V) ALARM
>
> After a complete cooldown period (30 mins idling)
> (...)
> in4: +3.42 V (min = +0.00 V, max = +0.00 V) ALARM
Strange. The value changes, so I was probably right that in4 was
connected to a thermal sensor, but OTOH, the values look odd. The
first two and last values suggest that +3.55 V / +3.42 V corresponds to
the normal running temperature, and +0.19 V means the CPU is very hot,
but the 3rd and 4th values don't really fit in that model. Or maybe it
was just too hot and the sensor got confused for some time, I don't
know.
> Is there any way to get information from PCCHIPS, or is it just a waste of
> time to request information from them?
If the board is 10-year old, it's probably hopeless, but it depends on
how much you want to get it to work and how much time you are ready to
spend on it.
If you can't get additional information, you can label in4 "CPU Temp",
observe the reading over a period of time, and set arbitrary limits
accordingly. Unfortunately we have no way to tell "sensors" that a
voltage input is actually a temperature value.
> > Well, I crafted the configuration file to make it look good, so it
> > doesn't mean much ;)
>
> Is there actually any way to see if it is correct, not involving to use a
> multimeter? I lost mine, so I should buy a new one ;p
The other possibilities are asking PCChips, or attempting to
disassemble the BIOS.
--
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:[~2007-06-12 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 sis5595 Nicolas
2005-05-19 6:24 ` sis5595 Jean Delvare
2005-05-19 6:24 ` sis5595 Nicolas
2005-05-19 6:24 ` sis5595 Mark M. Hoffman
2007-06-07 17:40 ` [lm-sensors] sis5595 Jean Delvare
2007-06-08 15:20 ` Ivo Manca
2007-06-09 9:50 ` Jean Delvare
2007-06-09 11:56 ` Ivo Manca
2007-06-11 15:06 ` Jean Delvare
2007-06-11 16:21 ` Ivo Manca
2007-06-11 16:43 ` Hans de Goede
2007-06-12 16:25 ` Jean Delvare [this message]
2007-06-12 17:42 ` Hans de Goede
2007-06-14 14:19 ` Ivo Manca
2007-06-14 19:13 ` 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=20070612182547.591ed2fa@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.