All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@paradyne.com (Mark D. Studebaker)
To: lm-sensors@vger.kernel.org
Subject: [lm_sensors] wrong sensors readings from w83782d on Tyan Dual
Date: Thu, 19 May 2005 06:23:26 +0000	[thread overview]
Message-ID: <3C04648D.3B32C61D@paradyne.com> (raw)
In-Reply-To: <20011115152423.03BD910A3@shrek.lisa.de>

It's very confusing, but you can't adjust the fan value by
changing the fan divisor. You have to add a compute line
in /etc/sensors.conf, like 
	compute fan1 @/2,2*@

I just enhanced our FAQ and doc/fan-divisors in our package to
explain better.

In testing, I uncovered a bug in the library for w83* chips.
If you had a compute line for a fan it didn't affect the
fan_min values. Fixed in CVS.

To feel better or worse about your temp. values and them changing or
not,
try the 'cpuburn' utility (link on our links page).

Negative voltage readings are a problem, each board uses different
resistor values, so it's hard to figure out the correct formula.
Sorry.

mds


Hans-Peter Jansen wrote:
> 
> Dan, thanks, for your ultimate help on this topic.
> 
> On Thursday, 15. November 2001 03:50, Dan Hollis wrote:
> > On Wed, 14 Nov 2001, Hans-Peter Jansen wrote:
> > > fan1:     7180 RPM  (min = 3000 RPM, div = 2)
> > > <3590> fan2:     7105 RPM  (min = 3000 RPM, div = 2)
> > >  <3515>
> >
> > Fan divisor is wrong.
> > adjust /proc/sys/dev/sensors/w83782d-i2c-0-2d/fan_div as needed.
> 
> ok, then
> 
> tyrex:~# echo "4 4 4" > /proc/sys/dev/sensors/w83782d-i2c-0-2d/fan_div
> tyrex:~# sensors | egrep ^fan
> fan1:     6887 RPM  (min = 1500 RPM, div = 4)
> fan2:     7031 RPM  (min = 1500 RPM, div = 4)
> 
> tyrex:~# echo "1 1 1" > /proc/sys/dev/sensors/w83782d-i2c-0-2d/fan_div
> tyrex:~# sensors | egrep ^fan
> fan1:     7142 RPM  (min = 6000 RPM, div = 1)
> fan2:     6716 RPM  (min = 6000 RPM, div = 1)
> 
> Is adjusting the min value the intended behaviour?
> I also tried this in /etc/sensors.conf:
>    set fan1_div 4
>    set fan2_div 4
>    set fan1_min 2000
>    set fan2_min 2000
>    ignore fan3
> 
> Again, with no success. The fan value isn't corrected. Or is this
> a userland problem. (Divide yourself and get happy?)
> 
> > > temp1:    +77.0?C   (limit = +60?C, hysteresis = +50?C) sensor > > > thermistor <46?C>
> > > temp2:    +76.5?C   (limit = +60?C, hysteresis = +50?C) sensor > > > thermistor <41?C>
> > > temp3:    +77.0?C   (limit = +60?C, hysteresis = +50?C) sensor > > > thermistor <46?C>
> >
> > thermistor type is wrong.
> >
> > echo "2" > /proc/sys/dev/sensors/w83782d-i2c-0-2d/sensor{1..3}
> 
> That does the trick. I was looking at the wrong place ("w83781d")...
> 
>    set sensor1 2
>    set sensor2 2
>    set sensor3 2
> 
> # examples for temperature limits
>     set temp1_over 65???
>     set temp1_hyst 55???
>     set temp2_over 65???
>     set temp2_hyst 55???
>     set temp3_over 65???
>     set temp3_hyst 55???
> 
> Readings from temp2 are always lower than from 1 and 3.
> BIOS says:
> temp1 = cpu0
> temp2 = cpu1
> temp3 = chassis
> 
> I tend to distrust the BIOS and think that 1 and 3 are cpu temps,
> and 2 is chassis temp, but I also tend to distrust these reading
> generally, because of the low variance between the readings:
> tyrex:~# sensors | egrep ^temp
> temp1:    +46.0?C   (limit = +65?C, hysteresis = +55?C) sensor = 3904
> transistor
> temp2:    +42.0?C   (limit = +65?C, hysteresis = +55?C) sensor = 3904
> transistor
> temp3:    +45.0?C   (limit = +65?C, hysteresis = +55?C) sensor = 3904
> transistor
> 
> tyrex:~# sensors | egrep ^temp
> temp1:    +46.0?C   (limit = +65?C, hysteresis = +55?C) sensor = 3904
> transistor
> temp2:    +43.0?C   (limit = +65?C, hysteresis = +55?C) sensor = 3904
> transistor
> temp3:    +46.0?C   (limit = +65?C, hysteresis = +55?C) sensor = 3904
> transistor
> 
> More of a headache are the voltage readings:
> VCore 1:   +1.74 V  (min =  +1.74 V, max =  +1.93 V)       ALARM
> VCore 2:   +2.84 V  (min =  +1.74 V, max =  +1.93 V)
> +3.3V:     +3.32 V  (min =  +3.13 V, max =  +3.45 V)
> +5V:       +4.89 V  (min =  +4.72 V, max =  +5.24 V)
> +12V:      +4.71 V  (min = +10.79 V, max = +13.19 V)
> -12V:      -2.11 V  (min = -10.90 V, max = -13.21 V)
> -5V:       +2.71 V  (min =  -4.76 V, max =  -5.26 V)
> V5SB:      +4.32 V  (min =  +4.72 V, max =  +5.24 V)
> VBat:      +3.29 V  (min =  +2.40 V, max =  +3.60 V)
> vid:      +1.85 V
> 
> VCore 2, +12V, -12V, -5V, V5SB are bogus (and no ALARM flag)
> 
> I have no idea how to correct the corresponding formulas in
> /etc/sensors.conf. Does somebody did it, before?
> 
> > -Dan
> 
> Cheers,
> Hans-Peter

  parent reply	other threads:[~2005-05-19  6:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 18:04 [lm_sensors] hard lockup on modprobe w83781d with Tyan Dual K7/Thunder Hans-Peter Jansen
2005-05-19  6:23 ` Hans-Peter Jansen
2001-11-14 20:13 ` Dan Hollis
2001-11-14 20:32   ` Need info on kernel philosofy Giorgio A.
2001-11-14 21:49     ` Mike Fedyk
2001-11-14 21:52 ` [lm_sensors] hard lockup on modprobe w83781d with Tyan Dual K7/Thunder Hans-Peter Jansen
2005-05-19  6:23   ` Hans-Peter Jansen
2001-11-15  2:50   ` Dan Hollis
2001-11-15 15:06     ` [lm_sensors] wrong sensors readings from w83782d on " Hans-Peter Jansen
2005-05-19  6:23       ` Hans-Peter Jansen
2001-11-15 19:25       ` Dan Hollis
2005-05-19  6:23       ` Mark D. Studebaker [this message]
2005-05-19  6:23 ` [lm_sensors] hard lockup on modprobe w83781d with " phil

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=3C04648D.3B32C61D@paradyne.com \
    --to=mds@paradyne.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.