ABIT IP35 Pro mainboard wrong values from 'sensors'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi James,

>  I have a system with an Intel Q6600 quad core on a ABit IP35 Pro mainboard,
> using Fedora 7 x64, and lm_sensors-2.10.4-1.fc7.  The output from sensors is
> wrong.  Is there a preformatted config file for these mainboard somewhere
> that I can find?  Or can you give me a hit on what I need to know in order
> to create/adjust one?

I think you'll need to create one. I haven't seen any emails on the
lm-sensors list about your motherboard.

Creating a new config file isn't too hard. Look at the man page for
sensors.conf: http://www.lm-sensors.org/wiki/man/sensors.conf

You should also have one already (maybe in /etc/sensors.conf) and
reading it is very helpful.

>  The cpu cores are really in the high 30's, cpu  & case fans are not
> present, ....

I'm looking at the IP32 pro manual, page 11, and I see six fans
(CPUfan1, SYSfan1, AUXfan1-4). The w83627dhg only reads the RPM from 5
fans, which makes me wonder if your southbridge (possibly an Intel
ICH9) is controlling one fan. Do you have zero fans connected? Or just
one (a CPU fan?). Page 22 of the manual mentions "abit's exclusive
Guru Panel." Do you have a uguru on the motherboard? (I'm not really
familiar with abit's uguru, but there are some other people here on
lm-sensors who know a lot more about it.)

The sensors.conf file we figure out here, for the sake of all IP32 pro
users, should probably not disable the fan input readings and alarms.
But if you want, you can set "ignore" statements for all the fans, so
they don't show up in the sensors output, since you don't have fans
connected to the motherboard.

>  [jscott at vserv ~]$ sensors
>  w83627dhg-isa-0290
>  Adapter: ISA adapter

OK, the above lines are fine.

>  VCore:     +1.46 V  (min =  +1.03 V, max =  +1.74 V)
>  in1:       +8.76 V  (min = +11.30 V, max =  +2.80 V) ALARM
>  AVCC:      +3.20 V  (min =  +2.06 V, max =  +0.88 V) ALARM
>  3VCC:      +3.20 V  (min =  +1.87 V, max =  +0.58 V) ALARM
>  in4:       +1.48 V  (min =  +0.34 V, max =  +1.20 V) ALARM
>  in5:       +1.34 V  (min =  +1.03 V, max =  +1.03 V) ALARM
>  in6:       +4.28 V  (min =  +5.99 V, max =  +3.30 V) ALARM
>  VSB:       +3.10 V  (min =  +3.47 V, max =  +2.02 V) ALARM
>  VBAT:      +0.51 V  (min =  +0.99 V, max =  +2.06 V) ALARM

It would be really helpful to match these voltages against voltages in
your BIOS. Also, try to find information on what the min and max for
each should be. The most important ones, of course, are VCore, 3VCC,
VBAT, and 12V (which I don't see there).

This means that the voltages are not being calculated correctly. This
isn't a surprise. The w83627dhg chip reads voltages, but each
motherboard is wired differently, so the voltage arriving at the 'dhg
pins is never the same.

>  Case Fan:    0 RPM  (min = 10546 RPM, div = 128) ALARM
>  CPU Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
>  Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
>  fan4:        0 RPM  (min =  439 RPM, div = 128) ALARM
>  fan5:        0 RPM  (min =   81 RPM, div = 128) ALARM

So it looks like nothing's connected to your fans. We'll just leave
them there for now.

>  Sys Temp:    +21?C  (high =   +58?C, hyst =   +78?C)
>  CPU Temp:  +30.0?C  (high = -126.0?C, hyst = +75.5?C)
>  AUX Temp:  -23.0?C  (high = +80.0?C, hyst = +75.0?C)

The temps don't look right. I think coretemp is reporting the right
temperature, and sensors.conf will need to scale the temps it gets
(which are just voltages) to match coretemp.

>  coretemp-isa-0000
>  Adapter: ISA adapter
>  Core 0:      +54?C  (high =  +100?C)
>
>  coretemp-isa-0001
>  Adapter: ISA adapter
>  Core 1:      +51?C  (high =  +100?C)
>
>  coretemp-isa-0002
>  Adapter: ISA adapter
>  Core 2:      +49?C  (high =  +100?C)
>
>  coretemp-isa-0003
>  Adapter: ISA adapter
>  Core 3:      +52?C  (high =  +100?C)
>
>  [jscott at vserv ~]$
>
>
>
>  [jscott at vserv ~]$ cat /etc/sysconfig/lm_sensors
>  ...
>  #
>  # Generated by sensors-detect on Fri Oct 19 00:26:53 2007
>  MODULE_0=w83627ehf
>  MODULE_1=coretemp
>  [jscott at vserv ~]$

Well, that's a start. Please reply with information about what chips
you have (you can run 'lspci -n' for that) and look at your BIOS setup
screen for voltages and temperatures. The numbers reported by BIOS
will be the most accurate. We'll try to match those numbers in
sensors.

HTH,
David




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux