[lm-sensors] MSI KT4V - Strange sensors output.

[lm-sensors] MSI KT4V - Strange sensors output.

[tyranix]

Hi,

Motherboard: MSI KT4V (MSI 6712):
http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID62
  Uses KT400, VT8235, w83697hf (last one reported by sensors, not in specs).
Kernel: Stock debian 2.6.15-1-k7 (2.6.15-4)
Lm-sensors: Stock debian 2.9.2-8.

Problem is I get strange output from sensors (-86 C high for temp1)
and several alarms are tripped even though I'm not an overclocker and
I never adjust any of the voltages in the BIOS:

      % sensors
      w83697hf-isa-0290
      Adapter: ISA adapter
      VCore:     +1.78 V  (min =  +1.71 V, max =  +1.89 V)
      +3.3V:     +3.33 V  (min =  +3.14 V, max =  +3.47 V)
      +5V:       +5.00 V  (min =  +4.76 V, max =  +5.24 V)
      +12V:     +12.40 V  (min = +10.82 V, max = +13.19 V)
      -12V:     -12.11 V  (min = -13.18 V, max = -10.80 V)
      -5V:       -5.35 V  (min =  -5.25 V, max =  -4.75 V)       ALARM
      V5SB:      +5.56 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
      VBat:      +3.47 V  (min =  +2.40 V, max =  +3.60 V)
      fan1:     4787 RPM  (min = 3026 RPM, div = 2)
      fan2:     1834 RPM  (min = 1814 RPM, div = 4)
      temp1:       +30?C  (high =   -86?C, hyst =   +59?C)   sensor thermistor
      temp2:     +50.0?C  (high =   +70?C, hyst =   +67?C)   sensor thermistor
      alarms:
      beep_enable:
                Sound alarm enabled

I used sensors-detect and loaded all of the modules it put into /etc/modules.

  % cat /sys/class/hwmon/hwmon0/device/temp1_max
  -86000

In addition to that, I tried using the Tyan settings since that also
uses KT400/VT8235 and w83697hf.  However, with that configuration, I
get even more alarms (and temp1 is still listed at high of -86 C). 
http://www.tyan.com/products/html/trinitykt400_spec.html

I looked through your tickets and other people with the same
motherboard don't have this problem: 
http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket 02


This is from using the Tyan settings.  These look way off:

w83697hf-isa-0290
Adapter: ISA adapter
VCore:     +1.81 V  (min =  +1.71 V, max =  +1.89 V)
VAgp:      +3.31 V  (min =  +1.42 V, max =  +1.57 V)       ALARM
+5V:       +5.03 V  (min =  +4.76 V, max =  +5.24 V)
+12V:     +12.22 V  (min = +10.82 V, max = +13.19 V)
+3.3V:     +0.53 V  (min =  +3.14 V, max =  +3.47 V)       ALARM
-5V:       +0.75 V  (min =  +2.37 V, max =  +2.62 V)       ALARM
VBat:      +3.31 V  (min =  +2.70 V, max =  +3.30 V)       ALARM
V5SB:      +5.86 V  (min =  +4.49 V, max =  +5.51 V)       ALARM
fan1:     4787 RPM  (min = 3026 RPM, div = 2)
fan2:     1844 RPM  (min = 1814 RPM, div = 4)
temp1:       +30?C  (high =   -86?C, hyst =   +59?C)   sensor thermistor
temp2:     +50.0?C  (high =   +70?C, hyst =   +67?C)   sensor thermistor
alarms:
beep_enable:
          Sound alarm enabled

Repost of pastebin:
      This is from /etc/modules:

      # Generated by sensors-detect on Sun Feb 12 18:46:41 2006
      # I2C adapter drivers
      i2c-viapro
      i2c-isa
      # I2C chip drivers
      eeprom
      w83627hf

      From lsmod after running sensors-detect (and loading the modules
in /etc/modules):

      Module                  Size  Used by
      eeprom                  6800  0
      w83627hf               23376  0
      hwmon_vid               2368  1 w83627hf
      i2c_dev                 8704  0
      i2c_matroxfb            4608  0
      matroxfb_base          28768  2 i2c_matroxfb
      matroxfb_DAC1064       10496  1 matroxfb_base
      matroxfb_accel          4288  1 matroxfb_base
      matroxfb_Ti3026         5632  1 matroxfb_base
      matroxfb_g450           6720  1 matroxfb_base
      g450_pll                5760  2 matroxfb_DAC1064,matroxfb_g450
      matroxfb_misc           8960  6
i2c_matroxfb,matroxfb_base,matroxfb_DAC1064,matroxfb_Ti3026,matroxfb_g450,g450_pll
      via686a                15368  0
      i2c_isa                 4672  2 w83627hf,via686a
      i2c_via                 4100  0
      i2c_algo_bit            8392  2 i2c_matroxfb,i2c_via


Thanks!
-tyranix

[lm-sensors] MSI KT4V - Strange sensors output.

[Jean Delvare]

Hi,

> Motherboard: MSI KT4V (MSI 6712):
> http://www.msi.com.tw/program/products/mainboard/mbd/pro_mbd_detail.php?UID62
>   Uses KT400, VT8235, w83697hf (last one reported by sensors, not in specs).
> Kernel: Stock debian 2.6.15-1-k7 (2.6.15-4)
> Lm-sensors: Stock debian 2.9.2-8.
> 
> Problem is I get strange output from sensors (-86 C high for temp1)
> and several alarms are tripped even though I'm not an overclocker and
> I never adjust any of the voltages in the BIOS:
> 
>       % sensors
>       w83697hf-isa-0290
>       Adapter: ISA adapter
>       VCore:     +1.78 V  (min =  +1.71 V, max =  +1.89 V)
>       +3.3V:     +3.33 V  (min =  +3.14 V, max =  +3.47 V)
>       +5V:       +5.00 V  (min =  +4.76 V, max =  +5.24 V)
>       +12V:     +12.40 V  (min = +10.82 V, max = +13.19 V)
>       -12V:     -12.11 V  (min = -13.18 V, max = -10.80 V)
>       -5V:       -5.35 V  (min =  -5.25 V, max =  -4.75 V)       ALARM
>       V5SB:      +5.56 V  (min =  +4.76 V, max =  +5.24 V)       ALARM

Well the values are indeed out of the 5% tolerance defined in the
default configuration file. This means that your power supply isn't
doing a very good job for these voltages. If you're worried about this
you may purchase a better power supply, but given that these voltages
are not really important, I'd simply change the configuration file to
10% tolerance for these inputs:

    set in6_max -5 * 0.90
    set in6_min -5 * 1.10
    set in7_min 5 * 0.90
    set in7_max 5 * 1.10

This will still not make it for 5VSB though; it would need 15%, which I
admit is a bit too much. Are there values displayed for these voltages
in the BIOS setup screen? If so, do the values there match the ones
displayed by "sensors"?

>       VBat:      +3.47 V  (min =  +2.40 V, max =  +3.60 V)
>       fan1:     4787 RPM  (min = 3026 RPM, div = 2)
>       fan2:     1834 RPM  (min = 1814 RPM, div = 4)

fan2 is very near from the limit you have set. You should probably lower
that limit a bit if you don't want an alarm to trigger every now and
then.

>       temp1:       +30?C  (high =   -86?C, hyst =   +59?C)   sensor = thermistor
>       temp2:     +50.0?C  (high =   +70?C, hyst =   +67?C)   sensor = thermistor

I'd guess the limits for temp1 were simply never initialized. The
default in sensors.conf (for this chip at least) is to leave the limits
to whatever the BIOS set them. It would seem that your BIOS initialized
the limits for temp2 (CPU temperature) but not for temp1 (system
temperature). The following lines in your configuration file should
help:

    label temp1 "Sys Temp"
    label temp2 "CPU Temp"

    set temp1_over 50
    set temp1_hyst 45

Remember you'll have to run "sensors -s" for the set lines to take
effect.

> In addition to that, I tried using the Tyan settings since that also
> uses KT400/VT8235 and w83697hf.  However, with that configuration, I
> get even more alarms (and temp1 is still listed at high of -86 C).

Settings are really motherboard specific, these special Tyan settings
won't work for you, as you already figured out.

-- 
Jean Delvare

[lm-sensors] MSI KT4V - Strange sensors output.

[tyranix]

I'll paste in what my motherboard reports for the readings with alarm status.

On 2/18/06, Jean Delvare <khali at linux-fr.org> wrote:
> >       -5V:       -5.35 V  (min =  -5.25 V, max =  -4.75 V)       ALARM
-5.0V:  -5.327V

> >       V5SB:      +5.56 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
+5V SB: 5.042V

> This will still not make it for 5VSB though; it would need 15%, which I
> admit is a bit too much. Are there values displayed for these voltages
> in the BIOS setup screen? If so, do the values there match the ones
> displayed by "sensors"?

I re-ran sensors and it still reports 5.59 V for V5SB but my BIOS says 5.042V.

> >       temp1:       +30?C  (high =   -86?C, hyst =   +59?C)   sensor > thermistor

> I'd guess the limits for temp1 were simply never initialized.

I checked and there is only a section for CPU critical temperature.  I
cannot set the system temperature limit.

Thanks!

[lm-sensors] MSI KT4V - Strange sensors output.

[Jean Delvare]

> I'll paste in what my motherboard reports for the readings with alarm status.
> 
> On 2/18/06, Jean Delvare <khali at linux-fr.org> wrote:
> > >       -5V:       -5.35 V  (min =  -5.25 V, max =  -4.75 V)       ALARM
> -5.0V:  -5.327V

Pretty much the same, so it's OK. Just use 10% tolerance when setting
limits and you're done.

> > >       V5SB:      +5.56 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
> +5V SB: 5.042V

Aha, so the compute formula in sensors.conf must not be correct for
your board. That's odd since this means you would have different
resistors used for +5V and 5VSB. Or maybe the input order differs. Are
the voltage values displayed in the same order in the BIOS and by
"sensors"?

If the order is the same in BIOS and "sensors", you may try the
following compute line, which should give yo roughly the same 5VSB
value your BIOS does. Whether this matches physical reality or not, I
don't know.

    compute in7 ((5/10)+1)*@ ,  @/((5/10)+1)

-- 
Jean Delvare

[lm-sensors] MSI KT4V - Strange sensors output.

[tyranix]

On 2/18/06, Jean Delvare <khali at linux-fr.org> wrote:
> > > >       V5SB:      +5.56 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
> > +5V SB: 5.042V
>
> Aha, so the compute formula in sensors.conf must not be correct for
> your board. That's odd since this means you would have different
> resistors used for +5V and 5VSB. Or maybe the input order differs. Are
> the voltage values displayed in the same order in the BIOS and by
> "sensors"?

They are in a different order.  Also, I don't have anything labeled
+3.3V in the BIOS.  Here is the order from my BIOS:

Vcore
+5.0V
+12.0V
-12.0V
-5.0V
Battery
+5V SB

And this is from /etc/sensors.conf:

chip "w83697hf-*"
    label in0 "VCore"
    label in2 "+3.3V"
    label in3 "+5V"
    label in4 "+12V"
    label in5 "-12V"
    label in6 "-5V"
    label in7 "V5SB"
    label in8 "VBat"

So based on the names, it would appear that in7 and in8 are reversed. 
But if in7 and in8 were really reversed, wouldn't I see 5.xV for VBat
and 3.xV for V5SB?

> If the order is the same in BIOS and "sensors", you may try the
> following compute line, which should give yo roughly the same 5VSB
> value your BIOS does. Whether this matches physical reality or not, I
> don't know.
>
>     compute in7 ((5/10)+1)*@ ,  @/((5/10)+1)

That is closer to what my BIOS says.  If I use that computation, then
I can set the threshold back to +- 5% for 5VSB.

Sensors now reports this:

V5SB:      +4.97 V  (min =  +4.75 V, max =  +5.26 V)

and previously my BIOS said 5.042V (and would sometimes drop down to
4.993V for a second).

[lm-sensors] MSI KT4V - Strange sensors output.

[Jean Delvare]

> > Aha, so the compute formula in sensors.conf must not be correct for
> > your board. That's odd since this means you would have different
> > resistors used for +5V and 5VSB. Or maybe the input order differs. Are
> > the voltage values displayed in the same order in the BIOS and by
> > "sensors"?
> 
> They are in a different order.  Also, I don't have anything labeled
> +3.3V in the BIOS.  Here is the order from my BIOS:
> 
> Vcore
> +5.0V
> +12.0V
> -12.0V
> -5.0V
> Battery
> +5V SB
> 
> And this is from /etc/sensors.conf:
> 
> chip "w83697hf-*"
>     label in0 "VCore"
>     label in2 "+3.3V"
>     label in3 "+5V"
>     label in4 "+12V"
>     label in5 "-12V"
>     label in6 "-5V"
>     label in7 "V5SB"
>     label in8 "VBat"
> 
> So based on the names, it would appear that in7 and in8 are reversed.

Correct, there are a number of boards where this is the case.

> But if in7 and in8 were really reversed, wouldn't I see 5.xV for VBat
> and 3.xV for V5SB?

Not it you also swap the compute lines. Given that VBat doesn't need
one, it's down to simply replacing "compute in7" by "compute in8".

> Sensors now reports this:
> 
> V5SB:      +4.97 V  (min =  +4.75 V, max =  +5.26 V)
> 
> and previously my BIOS said 5.042V (and would sometimes drop down to
> 4.993V for a second).

Sounds good. Will be slightly different after you switch in7 and in8,
but all in all it should stay within a reasonable range.

-- 
Jean Delvare