All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sis5595
Date: Mon, 11 Jun 2007 15:06:11 +0000	[thread overview]
Message-ID: <20070611170611.323f77ca@hyperion.delvare> (raw)
In-Reply-To: <200307161427.08403.linux@1g6.biz>

Hi Ivo,

On Sat, 9 Jun 2007 13:56:43 +0200, Ivo Manca wrote:
> Sensors gives a temprature after removing & loading the module:
> 
> [root@localhost ~]# sensors -c /dev/null
> sis5595-isa-0290
> Adapter: ISA adapter
> in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> temp:       +158°C  (high =   +52°C, hyst =   +52°C)
> alarms:   Board temperature input (usually LM75 chips) ALARM

Not exactly a good temperature though. According to the driver source,
158°C corresponds to a register value of 127 degree C - which means
saturation. So it's no good.

One possibility that I am only thinking of now, is that the temperature
might be provided by a thermistor and not a diode. In which case it
would make sense that the BIOS leaves in4 as a voltage input. So can
you please revert the PCI configuration change:

setpci -d 1039:0008 7a.b\0:80

Then reload the driver, check the voltage values, then put some load on
the CPU (e.g. md5sum /dev/zero) for several minutes and check if any of
the voltages changed significantly. If one did, then this input might
be connected to a thermistor. Unfortunately, without technical
information from the manufacturer, it will be difficult to find out how
to translate the voltage into a temperature.

> > For fans, do you have 3-wire fans? Are they connected to headers on
> > the motherboard? If they are relatively slow, maybe we need to increase
> > the divider to get a reading.
>
> As far as I can remember (I'll have to look into it tomorrow), my fan is 
> connected directly to the PSU, bypassing the motherboard.

OK, then it's no surprise that you get no reading, neither in the BIOS
no in "sensors". You need a 3-wire fan plugged into the motherboard fan
header to get a speed reading.

> [root@localhost ivo]# sensors -c sensors-PCChips -s
> [root@localhost ivo]# sensors -c sensors-PCChips
> sis5595-isa-0290
> Adapter: ISA adapter
> +2.5V:     +2.96 V  (min =  +2.26 V, max =  +2.75 V)   ALARM
> +3.3V:     +3.41 V  (min =  +3.14 V, max =  +3.47 V)
> +5.0V:     +5.09 V  (min =  +4.76 V, max =  +5.24 V)
> Vcore:     +2.05 V  (min =  +1.90 V, max =  +2.10 V)
> fan1:        0 RPM  (min =  998 RPM, div = 8)          ALARM
> fan2:        0 RPM  (min =  998 RPM, div = 8)          ALARM
> CPU Temp:   +158°C  (high =   +52°C, hyst =   +52°C)
> 
> It seems like the +5,0V actually makes complete sense now!

Well, I crafted the configuration file to make it look good, so it
doesn't mean much ;)

> However, what's 
> up with the Temp? The default sensors.conf speaks about a vendor.ini. I 
> suppose this should be coming with AMI's utility?
> I''m not really sure if I understand what's ment with all the computing 
> stuff standing there ;)

No idea what vendor.ini they're talking about. The computing stuff is
there to account for different thermal diode types, but as I said
above, I don't think you have a thermal diode, so no amount of
computing will give you a temperature value while in4 is in temperature
mode.

> > What's your CPU? Do you happen to know its nominal vcore?
> It's an Intel Celeron 366. According to this page 
> (http://www.intel.com/support/processors/celeron/sb/CS-007435.htm#Voltage%20Requirements), 
> it is 2,00V.

Good, exactly what I put in the config file :)

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-06-11 15:06 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 Mark M. Hoffman
2005-05-19  6:24 ` sis5595 Nicolas
2005-05-19  6:24 ` sis5595 Jean Delvare
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 [this message]
2007-06-11 16:21 ` Ivo Manca
2007-06-11 16:43 ` Hans de Goede
2007-06-12 16:25 ` Jean Delvare
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=20070611170611.323f77ca@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.