[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

Hello list,

I have the Abit AT8 mobo described in the subject line and I'm trying to 
get lm_sensors working properly for this board.  I see there is still 
very recent activity concerning getting this Winbond chip fully 
supported.  In the latest 2.10.2 release I see Dave Platt added these 
changes relavent to my board:

Program sensord:
                        Add w83627ehf voltage support (Dave Platt)
                        Add k8temp support (Dave Platt)

These additions appear to be working properly OOTB as the "sensors" 
command produces the following output:

[riwright at box ~]$ sensors
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:
             +45 ?C
Core1 Temp:
             +46 ?C

w83627ehf-isa-0290
Adapter: ISA adapter
VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)


So, as advertized, the Voltage support seems to be working.  However, 
the fan speeds and temperatures do not.  Are these items currently 
supported yet?  Or do I have a configuration problem?  If not yet 
supported, is this planned for the future?

Any input/hints/pointers greatly appreciated.

Thanks,
Rick

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

Appologies for those of you who may have received this initial mail with
HTML formatting.  Won't happen again....

Rick Wright wrote:

>Hello list,
>
>I have the Abit AT8 mobo described in the subject line and I'm trying to 
>get lm_sensors working properly for this board.  I see there is still 
>very recent activity concerning getting this Winbond chip fully 
>supported.  In the latest 2.10.2 release I see Dave Platt added these 
>changes relavent to my board:
>
>Program sensord:
>                        Add w83627ehf voltage support (Dave Platt)
>                        Add k8temp support (Dave Platt)
>
>These additions appear to be working properly OOTB as the "sensors" 
>command produces the following output:
>
>[riwright at box ~]$ sensors
>k8temp-pci-00c3
>Adapter: PCI adapter
>Core0 Temp:
>             +45 ?C
>Core1 Temp:
>             +46 ?C
>
>w83627ehf-isa-0290
>Adapter: ISA adapter
>VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
>in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
>AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
>3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
>in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
>in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
>in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
>VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
>VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
>in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
>Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
>CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
>Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
>fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
>fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
>Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
>CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
>AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
>
>
>So, as advertized, the Voltage support seems to be working.  However, 
>the fan speeds and temperatures do not.  Are these items currently 
>supported yet?  Or do I have a configuration problem?  If not yet 
>supported, is this planned for the future?
>
>Any input/hints/pointers greatly appreciated.
>
>Thanks,
>Rick
>
>_______________________________________________
>lm-sensors mailing list
>lm-sensors at lm-sensors.org
>http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
>  
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[David Hubbard]

Hi Rick,

The 0 RPM fan speeds are probably due to the minimum fan speed limits
for triggering the alarms. To be brief, add something like this to
your sensors.conf:

set fan1_min 0
set fan2_min 0
set fan3_min 0
set fan4_min 0
set fan5_min 0

(Note that after you do this, you have changed what will trigger an
alarm. You should check that your system does not overheat.)

This should get the driver to look "low enough" to find your fan RPM.
You can then modify sensors.conf to have a reasonable minimum for your
fans, or possible even ignore alarms generated by your fans.

Hope that helps,
David

On 2/12/07, Rick Wright <riwright at vt.edu> wrote:
> Rick Wright wrote:
>
> >Hello list,
> >
> >I have the Abit AT8 mobo described in the subject line and I'm trying to
> >get lm_sensors working properly for this board.  I see there is still
> >very recent activity concerning getting this Winbond chip fully
> >supported.  In the latest 2.10.2 release I see Dave Platt added these
> >changes relavent to my board:
> >
> >Program sensord:
> >                        Add w83627ehf voltage support (Dave Platt)
> >                        Add k8temp support (Dave Platt)
> >
> >These additions appear to be working properly OOTB as the "sensors"
> >command produces the following output:
> >
> >[riwright at box ~]$ sensors
> >k8temp-pci-00c3
> >Adapter: PCI adapter
> >Core0 Temp:
> >             +45 ?C
> >Core1 Temp:
> >             +46 ?C
> >
> >w83627ehf-isa-0290
> >Adapter: ISA adapter
> >VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
> >in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
> >AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
> >3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
> >in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
> >in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
> >in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
> >VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
> >VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
> >in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
> >Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
> >CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
> >Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
> >fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
> >fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
> >Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
> >CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
> >AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
> >
> >
> >So, as advertized, the Voltage support seems to be working.  However,
> >the fan speeds and temperatures do not.  Are these items currently
> >supported yet?  Or do I have a configuration problem?  If not yet
> >supported, is this planned for the future?
> >
> >Any input/hints/pointers greatly appreciated.
> >
> >Thanks,
> >Rick
> >
> >_______________________________________________
> >lm-sensors mailing list
> >lm-sensors at lm-sensors.org
> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >
> >
> >
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors at lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

David,

Thanks for the advice.  Tried the set fanX_min 0 commands below.  There 
was no change in behavior.  All fan RPM's still reported as 0.  Any 
other ideas?

Thanks,
Rick

David Hubbard wrote:

> Hi Rick,
>
> The 0 RPM fan speeds are probably due to the minimum fan speed limits
> for triggering the alarms. To be brief, add something like this to
> your sensors.conf:
>
> set fan1_min 0
> set fan2_min 0
> set fan3_min 0
> set fan4_min 0
> set fan5_min 0
>
> (Note that after you do this, you have changed what will trigger an
> alarm. You should check that your system does not overheat.)
>
> This should get the driver to look "low enough" to find your fan RPM.
> You can then modify sensors.conf to have a reasonable minimum for your
> fans, or possible even ignore alarms generated by your fans.
>
> Hope that helps,
> David
>
> On 2/12/07, Rick Wright <riwright at vt.edu> wrote:
>
>> Rick Wright wrote:
>>
>> >Hello list,
>> >
>> >I have the Abit AT8 mobo described in the subject line and I'm 
>> trying to
>> >get lm_sensors working properly for this board.  I see there is still
>> >very recent activity concerning getting this Winbond chip fully
>> >supported.  In the latest 2.10.2 release I see Dave Platt added these
>> >changes relavent to my board:
>> >
>> >Program sensord:
>> >                        Add w83627ehf voltage support (Dave Platt)
>> >                        Add k8temp support (Dave Platt)
>> >
>> >These additions appear to be working properly OOTB as the "sensors"
>> >command produces the following output:
>> >
>> >[riwright at box ~]$ sensors
>> >k8temp-pci-00c3
>> >Adapter: PCI adapter
>> >Core0 Temp:
>> >             +45 ?C
>> >Core1 Temp:
>> >             +46 ?C
>> >
>> >w83627ehf-isa-0290
>> >Adapter: ISA adapter
>> >VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
>> >in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
>> >AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
>> >3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
>> >in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
>> >in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
>> >in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
>> >VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
>> >VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
>> >in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
>> >Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
>> >CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
>> >Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
>> >fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
>> >fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
>> >Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
>> >CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
>> >AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
>> >
>> >
>> >So, as advertized, the Voltage support seems to be working.  However,
>> >the fan speeds and temperatures do not.  Are these items currently
>> >supported yet?  Or do I have a configuration problem?  If not yet
>> >supported, is this planned for the future?
>> >
>> >Any input/hints/pointers greatly appreciated.
>> >
>> >Thanks,
>> >Rick
>> >
>> >_______________________________________________
>> >lm-sensors mailing list
>> >lm-sensors at lm-sensors.org
>> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>> >
>> >
>> >
>>
>>
>> _______________________________________________
>> lm-sensors mailing list
>> lm-sensors at lm-sensors.org
>> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>>
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[David Hubbard]

Hi Rick,

Did the dividers change? In your previous email, they are all 128.

David

On 2/13/07, Rick Wright <riwright at vt.edu> wrote:
> David,
>
> Thanks for the advice.  Tried the set fanX_min 0 commands below.  There
> was no change in behavior.  All fan RPM's still reported as 0.  Any
> other ideas?
>
> Thanks,
> Rick
>
> David Hubbard wrote:
>
> > Hi Rick,
> >
> > The 0 RPM fan speeds are probably due to the minimum fan speed limits
> > for triggering the alarms. To be brief, add something like this to
> > your sensors.conf:
> >
> > set fan1_min 0
> > set fan2_min 0
> > set fan3_min 0
> > set fan4_min 0
> > set fan5_min 0
> >
> > (Note that after you do this, you have changed what will trigger an
> > alarm. You should check that your system does not overheat.)
> >
> > This should get the driver to look "low enough" to find your fan RPM.
> > You can then modify sensors.conf to have a reasonable minimum for your
> > fans, or possible even ignore alarms generated by your fans.
> >
> > Hope that helps,
> > David
> >
> > On 2/12/07, Rick Wright <riwright at vt.edu> wrote:
> >
> >> Rick Wright wrote:
> >>
> >> >Hello list,
> >> >
> >> >I have the Abit AT8 mobo described in the subject line and I'm
> >> trying to
> >> >get lm_sensors working properly for this board.  I see there is still
> >> >very recent activity concerning getting this Winbond chip fully
> >> >supported.  In the latest 2.10.2 release I see Dave Platt added these
> >> >changes relavent to my board:
> >> >
> >> >Program sensord:
> >> >                        Add w83627ehf voltage support (Dave Platt)
> >> >                        Add k8temp support (Dave Platt)
> >> >
> >> >These additions appear to be working properly OOTB as the "sensors"
> >> >command produces the following output:
> >> >
> >> >[riwright at box ~]$ sensors
> >> >k8temp-pci-00c3
> >> >Adapter: PCI adapter
> >> >Core0 Temp:
> >> >             +45 ?C
> >> >Core1 Temp:
> >> >             +46 ?C
> >> >
> >> >w83627ehf-isa-0290
> >> >Adapter: ISA adapter
> >> >VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
> >> >in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
> >> >AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
> >> >3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
> >> >in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
> >> >in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
> >> >in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
> >> >VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
> >> >VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
> >> >in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
> >> >Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
> >> >CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
> >> >Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
> >> >fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
> >> >fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
> >> >Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
> >> >CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
> >> >AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
> >> >
> >> >
> >> >So, as advertized, the Voltage support seems to be working.  However,
> >> >the fan speeds and temperatures do not.  Are these items currently
> >> >supported yet?  Or do I have a configuration problem?  If not yet
> >> >supported, is this planned for the future?
> >> >
> >> >Any input/hints/pointers greatly appreciated.
> >> >
> >> >Thanks,
> >> >Rick
> >> >
> >> >_______________________________________________
> >> >lm-sensors mailing list
> >> >lm-sensors at lm-sensors.org
> >> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >> >
> >> >
> >> >
> >>
> >>
> >> _______________________________________________
> >> lm-sensors mailing list
> >> lm-sensors at lm-sensors.org
> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >>
> >
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

No, dividers did not change.  Fans 1-4 are 128, fan 5 is 8.  Note, this 
is the same as below.

However, before adding the "set fan' commands in the sensors.conf file 
and issuing "sensors -s" (as root), I recall running "sensors" 
repeatedly would output different divider values.  For example (from 
memory), the on first issue of "sensors" I would get all dividers=8, 
immediately issuing "sensors" again might give all dividers (maybe all 
but #5?) 16.  Then 32.  Then 64.  Then all subsequent "sensors" command 
would top out the dividers at the 128 value seen below.  Is this 
expected behavior?  It seems that implementing your "set fanX_min" 
commands has eliminated the "climbing divider values".

Thanks for the support,
Rick


David Hubbard wrote:

> Hi Rick,
>
> Did the dividers change? In your previous email, they are all 128.
>
> David
>
> On 2/13/07, Rick Wright <riwright at vt.edu> wrote:
>
>> David,
>>
>> Thanks for the advice.  Tried the set fanX_min 0 commands below.  There
>> was no change in behavior.  All fan RPM's still reported as 0.  Any
>> other ideas?
>>
>> Thanks,
>> Rick
>>
>> David Hubbard wrote:
>>
>> > Hi Rick,
>> >
>> > The 0 RPM fan speeds are probably due to the minimum fan speed limits
>> > for triggering the alarms. To be brief, add something like this to
>> > your sensors.conf:
>> >
>> > set fan1_min 0
>> > set fan2_min 0
>> > set fan3_min 0
>> > set fan4_min 0
>> > set fan5_min 0
>> >
>> > (Note that after you do this, you have changed what will trigger an
>> > alarm. You should check that your system does not overheat.)
>> >
>> > This should get the driver to look "low enough" to find your fan RPM.
>> > You can then modify sensors.conf to have a reasonable minimum for your
>> > fans, or possible even ignore alarms generated by your fans.
>> >
>> > Hope that helps,
>> > David
>> >
>> > On 2/12/07, Rick Wright <riwright at vt.edu> wrote:
>> >
>> >> Rick Wright wrote:
>> >>
>> >> >Hello list,
>> >> >
>> >> >I have the Abit AT8 mobo described in the subject line and I'm
>> >> trying to
>> >> >get lm_sensors working properly for this board.  I see there is 
>> still
>> >> >very recent activity concerning getting this Winbond chip fully
>> >> >supported.  In the latest 2.10.2 release I see Dave Platt added 
>> these
>> >> >changes relavent to my board:
>> >> >
>> >> >Program sensord:
>> >> >                        Add w83627ehf voltage support (Dave Platt)
>> >> >                        Add k8temp support (Dave Platt)
>> >> >
>> >> >These additions appear to be working properly OOTB as the "sensors"
>> >> >command produces the following output:
>> >> >
>> >> >[riwright at box ~]$ sensors
>> >> >k8temp-pci-00c3
>> >> >Adapter: PCI adapter
>> >> >Core0 Temp:
>> >> >             +45 ?C
>> >> >Core1 Temp:
>> >> >             +46 ?C
>> >> >
>> >> >w83627ehf-isa-0290
>> >> >Adapter: ISA adapter
>> >> >VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
>> >> >in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
>> >> >AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
>> >> >3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
>> >> >in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
>> >> >in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
>> >> >in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
>> >> >VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
>> >> >VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
>> >> >in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
>> >> >Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
>> >> >CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
>> >> >Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
>> >> >fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
>> >> >fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
>> >> >Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
>> >> >CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
>> >> >AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
>> >> >
>> >> >
>> >> >So, as advertized, the Voltage support seems to be working.  
>> However,
>> >> >the fan speeds and temperatures do not.  Are these items currently
>> >> >supported yet?  Or do I have a configuration problem?  If not yet
>> >> >supported, is this planned for the future?
>> >> >
>> >> >Any input/hints/pointers greatly appreciated.
>> >> >
>> >> >Thanks,
>> >> >Rick
>> >> >
>> >> >_______________________________________________
>> >> >lm-sensors mailing list
>> >> >lm-sensors at lm-sensors.org
>> >> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >> _______________________________________________
>> >> lm-sensors mailing list
>> >> lm-sensors at lm-sensors.org
>> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>> >>
>> >
>>
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[David Hubbard]

Hi Rick,

Next week I'm going to be out of town. I'm the one who should be
figuring this out, but I'm going to pass the buck (at least until the
26th). To Jean and Rudolf: what's the next step in debugging this one?

David

On 2/13/07, Rick Wright <riwright at vt.edu> wrote:
> No, dividers did not change.  Fans 1-4 are 128, fan 5 is 8.  Note, this
> is the same as below.
>
> However, before adding the "set fan' commands in the sensors.conf file
> and issuing "sensors -s" (as root), I recall running "sensors"
> repeatedly would output different divider values.  For example (from
> memory), the on first issue of "sensors" I would get all dividers=8,
> immediately issuing "sensors" again might give all dividers (maybe all
> but #5?) 16.  Then 32.  Then 64.  Then all subsequent "sensors" command
> would top out the dividers at the 128 value seen below.  Is this
> expected behavior?  It seems that implementing your "set fanX_min"
> commands has eliminated the "climbing divider values".
>
> Thanks for the support,
> Rick
>
>
> David Hubbard wrote:
>
> > Hi Rick,
> >
> > Did the dividers change? In your previous email, they are all 128.
> >
> > David
> >
> > On 2/13/07, Rick Wright <riwright at vt.edu> wrote:
> >
> >> David,
> >>
> >> Thanks for the advice.  Tried the set fanX_min 0 commands below.  There
> >> was no change in behavior.  All fan RPM's still reported as 0.  Any
> >> other ideas?
> >>
> >> Thanks,
> >> Rick
> >>
> >> David Hubbard wrote:
> >>
> >> > Hi Rick,
> >> >
> >> > The 0 RPM fan speeds are probably due to the minimum fan speed limits
> >> > for triggering the alarms. To be brief, add something like this to
> >> > your sensors.conf:
> >> >
> >> > set fan1_min 0
> >> > set fan2_min 0
> >> > set fan3_min 0
> >> > set fan4_min 0
> >> > set fan5_min 0
> >> >
> >> > (Note that after you do this, you have changed what will trigger an
> >> > alarm. You should check that your system does not overheat.)
> >> >
> >> > This should get the driver to look "low enough" to find your fan RPM.
> >> > You can then modify sensors.conf to have a reasonable minimum for your
> >> > fans, or possible even ignore alarms generated by your fans.
> >> >
> >> > Hope that helps,
> >> > David
> >> >
> >> > On 2/12/07, Rick Wright <riwright at vt.edu> wrote:
> >> >
> >> >> Rick Wright wrote:
> >> >>
> >> >> >Hello list,
> >> >> >
> >> >> >I have the Abit AT8 mobo described in the subject line and I'm
> >> >> trying to
> >> >> >get lm_sensors working properly for this board.  I see there is
> >> still
> >> >> >very recent activity concerning getting this Winbond chip fully
> >> >> >supported.  In the latest 2.10.2 release I see Dave Platt added
> >> these
> >> >> >changes relavent to my board:
> >> >> >
> >> >> >Program sensord:
> >> >> >                        Add w83627ehf voltage support (Dave Platt)
> >> >> >                        Add k8temp support (Dave Platt)
> >> >> >
> >> >> >These additions appear to be working properly OOTB as the "sensors"
> >> >> >command produces the following output:
> >> >> >
> >> >> >[riwright at box ~]$ sensors
> >> >> >k8temp-pci-00c3
> >> >> >Adapter: PCI adapter
> >> >> >Core0 Temp:
> >> >> >             +45 ?C
> >> >> >Core1 Temp:
> >> >> >             +46 ?C
> >> >> >
> >> >> >w83627ehf-isa-0290
> >> >> >Adapter: ISA adapter
> >> >> >VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
> >> >> >in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
> >> >> >AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
> >> >> >3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
> >> >> >in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
> >> >> >in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
> >> >> >in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
> >> >> >VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
> >> >> >VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
> >> >> >in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
> >> >> >Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
> >> >> >CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
> >> >> >Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
> >> >> >fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
> >> >> >fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
> >> >> >Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
> >> >> >CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
> >> >> >AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
> >> >> >
> >> >> >
> >> >> >So, as advertized, the Voltage support seems to be working.
> >> However,
> >> >> >the fan speeds and temperatures do not.  Are these items currently
> >> >> >supported yet?  Or do I have a configuration problem?  If not yet
> >> >> >supported, is this planned for the future?
> >> >> >
> >> >> >Any input/hints/pointers greatly appreciated.
> >> >> >
> >> >> >Thanks,
> >> >> >Rick
> >> >> >
> >> >> >_______________________________________________
> >> >> >lm-sensors mailing list
> >> >> >lm-sensors at lm-sensors.org
> >> >> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> lm-sensors mailing list
> >> >> lm-sensors at lm-sensors.org
> >> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >> >>
> >> >
> >>
> >
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

Rick Wright wrote:
> Hello list,
> 
> I have the Abit AT8 mobo described in the subject line and I'm trying to 
> get lm_sensors working properly for this board.  I see there is still 
> very recent activity concerning getting this Winbond chip fully 
> supported.  In the latest 2.10.2 release I see Dave Platt added these 
> changes relavent to my board:
> 
> Program sensord:
>                         Add w83627ehf voltage support (Dave Platt)
>                         Add k8temp support (Dave Platt)
> 
> These additions appear to be working properly OOTB as the "sensors" 
> command produces the following output:
> 

You probably do NOT have a w83627ehf, but an Abit uGuru custom sensor 
chip, most likely revision 3 of the abituguru. A couple of weeks ago 
I've posted a patch with a new kernel driver for revision 3 of the uguru 
(the current abituguru driver only supports revision 1 and 2).

If your manual/driver cd says uGuru anywhere then you really do have 
one. I've also written a userspace utility which can read from the uguru 
when run as root try dowloading:
http://people.atrpms.net/~hdegoede/openguru2.3.1.tar.gz

Compile it like this:
gcc -O2 -Wall -o oguru main2.c openGuru.c

And then as root run: ./oguru

Let me know if and how it works for you any feedback is much appreciated.

Regards,

Hans

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

Rick Wright wrote:
> 
> I tested this userspace utility and it seems to be more correct, but 
> gives a strange warning in the immediate output that uGuru wasn't found 
> on the motherboard.

Yeah, the detect code needs work, hence the result of the detect is 
ignored and the utility continue as if nothing is wrong :)

>  The manual and BIOS definitely talk about uGuru 
> (TM!), though.
> 
> Output from openguru2.3.1 is attached.  This appears to be correctly 
> reading the chip info.  Running several time in a row gave small 
> fluctuations in fan RPM as one would expect.
> 

Yes, you definitely have an uguru motherboard otherwise openguru would 
be filling the screen with errors instead of usefull readings.

> I just joined the list so I will have to search the archives for your 
> kernel patch & instructions.  (unless you want to resend :) )  Thanks 
> for your help.
> 

I wonder where you want to go next, even if you compile and load the 
kernel module, most applications still won't see the sensors as 
libsensors the userspace part of sensors also requires updating and I 
haven't written a patch for that yet.

Regards,

Hans

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Jean Delvare]

David, Rick,

Could you please stop top-posting? It's very hard to follow what's
going on here.

On Wed, 14 Feb 2007 12:12:37 -0700, David Hubbard wrote:
> Next week I'm going to be out of town. I'm the one who should be
> figuring this out, but I'm going to pass the buck (at least until the
> 26th). To Jean and Rudolf: what's the next step in debugging this one?

Given that the W83627EHF chip doesn't appear to provide temperatures
either, my guess is that there is a second hardware monitoring chip
taking care of the fans and temperatures. I suggest that Rick provides
the output of a recent version of sensors-detect.

Rick, please also report what hardware monitoring values are presented
in the BIOS setup screen.

-- 
Jean Delvare

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

David Hubbard wrote:

> Hi Rick,
>
> Next week I'm going to be out of town. I'm the one who should be
> figuring this out, but I'm going to pass the buck (at least until the
> 26th). To Jean and Rudolf: what's the next step in debugging this one?
>
> David

Hi David,

Thanks for the support  Hans de Goede responded to me off list 
suggesting that, in fact, I probably have a abituguru ver3 chip, not a 
w83627ehf chip afterall.  The problem is that this ver3 abituguru chip 
is not fully supported by sensors, libsensors, etc.  However, he did 
point me to a userspace utility he wrote that I was able to use to 
successfully interrogate my uGuru chip.  All along I knew this board 
probably used a uGuru setup.  I will forward those messages back to the 
list under this thread for others' benefit.

On the other hand, the problem that lm_sensors still has is that it was 
the sensors-detect script that originally reported that I had a 
w83627ehf chip and ultimately led me down this path.  Hans suggested 
this is not a correct identification job and that sensors-detect should 
be fixed.

Correspondence with Hans to follow.

Thanks again,
Rick


(David, sorry you received this post twice)

>
> On 2/13/07, Rick Wright <riwright at vt.edu> wrote:
>
>> No, dividers did not change.  Fans 1-4 are 128, fan 5 is 8.  Note, this
>> is the same as below.
>>
>> However, before adding the "set fan' commands in the sensors.conf file
>> and issuing "sensors -s" (as root), I recall running "sensors"
>> repeatedly would output different divider values.  For example (from
>> memory), the on first issue of "sensors" I would get all dividers=8,
>> immediately issuing "sensors" again might give all dividers (maybe all
>> but #5?) 16.  Then 32.  Then 64.  Then all subsequent "sensors" command
>> would top out the dividers at the 128 value seen below.  Is this
>> expected behavior?  It seems that implementing your "set fanX_min"
>> commands has eliminated the "climbing divider values".
>>
>> Thanks for the support,
>> Rick
>>
>>
>> David Hubbard wrote:
>>
>> > Hi Rick,
>> >
>> > Did the dividers change? In your previous email, they are all 128.
>> >
>> > David
>> >
>> > On 2/13/07, Rick Wright <riwright at vt.edu> wrote:
>> >
>> >> David,
>> >>
>> >> Thanks for the advice.  Tried the set fanX_min 0 commands below.  
>> There
>> >> was no change in behavior.  All fan RPM's still reported as 0.  Any
>> >> other ideas?
>> >>
>> >> Thanks,
>> >> Rick
>> >>
>> >> David Hubbard wrote:
>> >>
>> >> > Hi Rick,
>> >> >
>> >> > The 0 RPM fan speeds are probably due to the minimum fan speed 
>> limits
>> >> > for triggering the alarms. To be brief, add something like this to
>> >> > your sensors.conf:
>> >> >
>> >> > set fan1_min 0
>> >> > set fan2_min 0
>> >> > set fan3_min 0
>> >> > set fan4_min 0
>> >> > set fan5_min 0
>> >> >
>> >> > (Note that after you do this, you have changed what will trigger an
>> >> > alarm. You should check that your system does not overheat.)
>> >> >
>> >> > This should get the driver to look "low enough" to find your fan 
>> RPM.
>> >> > You can then modify sensors.conf to have a reasonable minimum 
>> for your
>> >> > fans, or possible even ignore alarms generated by your fans.
>> >> >
>> >> > Hope that helps,
>> >> > David
>> >> >
>> >> > On 2/12/07, Rick Wright <riwright at vt.edu> wrote:
>> >> >
>> >> >> Rick Wright wrote:
>> >> >>
>> >> >> >Hello list,
>> >> >> >
>> >> >> >I have the Abit AT8 mobo described in the subject line and I'm
>> >> >> trying to
>> >> >> >get lm_sensors working properly for this board.  I see there is
>> >> still
>> >> >> >very recent activity concerning getting this Winbond chip fully
>> >> >> >supported.  In the latest 2.10.2 release I see Dave Platt added
>> >> these
>> >> >> >changes relavent to my board:
>> >> >> >
>> >> >> >Program sensord:
>> >> >> >                        Add w83627ehf voltage support (Dave 
>> Platt)
>> >> >> >                        Add k8temp support (Dave Platt)
>> >> >> >
>> >> >> >These additions appear to be working properly OOTB as the 
>> "sensors"
>> >> >> >command produces the following output:
>> >> >> >
>> >> >> >[riwright at box ~]$ sensors
>> >> >> >k8temp-pci-00c3
>> >> >> >Adapter: PCI adapter
>> >> >> >Core0 Temp:
>> >> >> >             +45 ?C
>> >> >> >Core1 Temp:
>> >> >> >             +46 ?C
>> >> >> >
>> >> >> >w83627ehf-isa-0290
>> >> >> >Adapter: ISA adapter
>> >> >> >VCore:     +2.04 V  (min =  +0.00 V, max =  +1.74 V) ALARM
>> >> >> >in1:      +13.46 V  (min = +13.46 V, max = +12.36 V) ALARM
>> >> >> >AVCC:      +3.22 V  (min =  +3.02 V, max =  +4.08 V)
>> >> >> >3VCC:      +3.22 V  (min =  +3.92 V, max =  +3.82 V) ALARM
>> >> >> >in4:       +1.66 V  (min =  +2.01 V, max =  +1.01 V) ALARM
>> >> >> >in5:       +1.66 V  (min =  +1.16 V, max =  +0.95 V) ALARM
>> >> >> >in6:       +5.32 V  (min =  +6.53 V, max =  +6.32 V) ALARM
>> >> >> >VSB:       +3.07 V  (min =  +4.08 V, max =  +3.06 V) ALARM
>> >> >> >VBAT:      +2.16 V  (min =  +2.02 V, max =  +2.38 V)
>> >> >> >in9:       +1.56 V  (min =  +1.98 V, max =  +1.75 V) ALARM
>> >> >> >Case Fan:    0 RPM  (min = 1318 RPM, div = 128) ALARM
>> >> >> >CPU Fan:     0 RPM  (min = 1757 RPM, div = 128) ALARM
>> >> >> >Aux Fan:     0 RPM  (min = 10546 RPM, div = 128) ALARM
>> >> >> >fan4:        0 RPM  (min = 10546 RPM, div = 128) ALARM
>> >> >> >fan5:        0 RPM  (min = 168750 RPM, div = 8) ALARM
>> >> >> >Sys Temp:    -48 ?C  (high =   +45 ?C, hyst =   +40 ?C)
>> >> >> >CPU Temp:  -48.0 ?C  (high = +45.0 ?C, hyst = +40.0 ?C)
>> >> >> >AUX Temp:  -48.0 ?C  (high = +80.0 ?C, hyst = +75.0 ?C)
>> >> >> >
>> >> >> >
>> >> >> >So, as advertized, the Voltage support seems to be working.
>> >> However,
>> >> >> >the fan speeds and temperatures do not.  Are these items 
>> currently
>> >> >> >supported yet?  Or do I have a configuration problem?  If not yet
>> >> >> >supported, is this planned for the future?
>> >> >> >
>> >> >> >Any input/hints/pointers greatly appreciated.
>> >> >> >
>> >> >> >Thanks,
>> >> >> >Rick
>> >> >> >
>> >> >> >_______________________________________________
>> >> >> >lm-sensors mailing list
>> >> >> >lm-sensors at lm-sensors.org
>> >> >> >http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >> _______________________________________________
>> >> >> lm-sensors mailing list
>> >> >> lm-sensors at lm-sensors.org
>> >> >> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>> >> >>
>> >> >
>> >>
>> >
>>
>

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

Rick Wright wrote:
> Hans de Goede wrote:
> Forgot to ask:  Do you have any clue as to why the sensors-detect script 
> would set me up to use the w83627ehf chip?  Is this just the sane 
> fallback since the latest uGuru isn't mainline supported yet?  If I 
> understand correctly, uGuru is a modified Winbond chip, right?
> 

I have no clue, and it isn't a sane fallback as the uguru is a piece of 
software running on a microcontroller, which just happens to be produced 
by winbond, but it is totally different from the w83627ehf chip.

I really should teach sensors-detect about the abituguru one of these 
days, but that would probably require identifying by dmi data as the 
uguru otherwise is almost impossible to detect with reasonable certainty.

Regards,

Hans

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Jean Delvare]

Rick,

On Wed, 14 Feb 2007 14:43:09 -0500, Rick Wright wrote:
> Thanks for the support  Hans de Goede responded to me off list 
> suggesting that, in fact, I probably have a abituguru ver3 chip, not a 
> w83627ehf chip afterall.  The problem is that this ver3 abituguru chip 
> is not fully supported by sensors, libsensors, etc.  However, he did 
> point me to a userspace utility he wrote that I was able to use to 
> successfully interrogate my uGuru chip.  All along I knew this board 
> probably used a uGuru setup.  I will forward those messages back to the 
> list under this thread for others' benefit.
> 
> On the other hand, the problem that lm_sensors still has is that it was 
> the sensors-detect script that originally reported that I had a 
> w83627ehf chip and ultimately led me down this path.  Hans suggested 
> this is not a correct identification job and that sensors-detect should 
> be fixed.

Hans is probably wrong. The Super-I/O chip detection is very reliable
and I would ve very surprised if you do not have a Winbond W83627EHF.
As a matter of fact, this hi-res picture of your motherboard:
  http://www.techpowerup.com/reviews/Abit/AT8/images/board_fullsize.jpg
clearly shows a W83627EHF in the top-left-hand corner.

But indeed there's also a uGuru chip on the board. Bad luck.

-- 
Jean Delvare

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Hans de Goede]

Jean Delvare wrote:
> Rick,
> 
> On Wed, 14 Feb 2007 14:43:09 -0500, Rick Wright wrote:
>> Thanks for the support  Hans de Goede responded to me off list 
>> suggesting that, in fact, I probably have a abituguru ver3 chip, not a 
>> w83627ehf chip afterall.  The problem is that this ver3 abituguru chip 
>> is not fully supported by sensors, libsensors, etc.  However, he did 
>> point me to a userspace utility he wrote that I was able to use to 
>> successfully interrogate my uGuru chip.  All along I knew this board 
>> probably used a uGuru setup.  I will forward those messages back to the 
>> list under this thread for others' benefit.
>>
>> On the other hand, the problem that lm_sensors still has is that it was 
>> the sensors-detect script that originally reported that I had a 
>> w83627ehf chip and ultimately led me down this path.  Hans suggested 
>> this is not a correct identification job and that sensors-detect should 
>> be fixed.
> 
> Hans is probably wrong. The Super-I/O chip detection is very reliable
> and I would ve very surprised if you do not have a Winbond W83627EHF.
> As a matter of fact, this hi-res picture of your motherboard:
>   http://www.techpowerup.com/reviews/Abit/AT8/images/board_fullsize.jpg
> clearly shows a W83627EHF in the top-left-hand corner.
> 
> But indeed there's also a uGuru chip on the board. Bad luck.
> 

Ah, so this board has 2 sensors chips. Rick, can you see if the 
W83627EHF voltage are any good (IOW match the ones given by openguru)?


Jean, about the bad luck part, the uguru revision 3 actually is a pretty 
nice chip (except for the lack of specs) as Rick writes I've written a 
userspace reading utility for it and it works fine for all people who 
have tested it (about 7 or so). I've also written a new kernel driver 
for this new revision (it uses an entirely different "protocol") which 
I've posted for review some time ago. If when can get some movement on 
that review then users with a newer uguru will no longer have bad luck, 
but instead a support chip.

Regards,

Hans

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Rick Wright]

Hans de Goede wrote:

> Jean Delvare wrote:
>
>> Rick,
>>
>> On Wed, 14 Feb 2007 14:43:09 -0500, Rick Wright wrote:
>>
>>> Thanks for the support  Hans de Goede responded to me off list 
>>> suggesting that, in fact, I probably have a abituguru ver3 chip, not 
>>> a w83627ehf chip afterall.  The problem is that this ver3 abituguru 
>>> chip is not fully supported by sensors, libsensors, etc.  However, 
>>> he did point me to a userspace utility he wrote that I was able to 
>>> use to successfully interrogate my uGuru chip.  All along I knew 
>>> this board probably used a uGuru setup.  I will forward those 
>>> messages back to the list under this thread for others' benefit.
>>>
>>> On the other hand, the problem that lm_sensors still has is that it 
>>> was the sensors-detect script that originally reported that I had a 
>>> w83627ehf chip and ultimately led me down this path.  Hans suggested 
>>> this is not a correct identification job and that sensors-detect 
>>> should be fixed.
>>
>>
>> Hans is probably wrong. The Super-I/O chip detection is very reliable
>> and I would ve very surprised if you do not have a Winbond W83627EHF.
>> As a matter of fact, this hi-res picture of your motherboard:
>>   http://www.techpowerup.com/reviews/Abit/AT8/images/board_fullsize.jpg
>> clearly shows a W83627EHF in the top-left-hand corner.
>>
>> But indeed there's also a uGuru chip on the board. Bad luck.
>>
>
> Ah, so this board has 2 sensors chips. Rick, can you see if the 
> W83627EHF voltage are any good (IOW match the ones given by openguru)?
>
Due to labeling differences, I'm not 100% sure how to match up the 
output values for comparison.  That said, both sensors & oguru give 
"reasonable" values.  The oguru information is much more complete.  With 
sensors: w83627ehf only gives voltage readings; (no valid fan speeds, no 
valid temps), but k8temp seems to give correct temp readings.

Attached is the output from both sensors & oguru run ~2 seconds apart.

I'm happy to continue to help testing, etc.  I'd really like to get this 
board supported as I've deployed 3 into production environments and 
would like to implement automated health monitoring.  Let me know how I 
can help.


Rick
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: sensors.txt
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070215/1d02bb2b/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: oguru.txt
Url: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20070215/1d02bb2b/attachment-0001.txt 

[lm-sensors] Abit AT8 (non-32X) / Winbond 83627EHF

[Jean Delvare]

Hi Hans,

On Thu, 15 Feb 2007 08:04:15 +0100, Hans de Goede wrote:
> Jean Delvare wrote:
> > On Wed, 14 Feb 2007 14:43:09 -0500, Rick Wright wrote:
> >> Thanks for the support  Hans de Goede responded to me off list 
> (...)
> >> On the other hand, the problem that lm_sensors still has is that it was 
> >> the sensors-detect script that originally reported that I had a 
> >> w83627ehf chip and ultimately led me down this path.  Hans suggested 
> >> this is not a correct identification job and that sensors-detect should 
> >> be fixed.
> > 
> > Hans is probably wrong. The Super-I/O chip detection is very reliable
> > and I would ve very surprised if you do not have a Winbond W83627EHF.
> > As a matter of fact, this hi-res picture of your motherboard:
> >   http://www.techpowerup.com/reviews/Abit/AT8/images/board_fullsize.jpg
> > clearly shows a W83627EHF in the top-left-hand corner.
> > 
> > But indeed there's also a uGuru chip on the board. Bad luck.
> > 
> 
> Ah, so this board has 2 sensors chips. Rick, can you see if the 
> W83627EHF voltage are any good (IOW match the ones given by openguru)?
> 
> 
> Jean, about the bad luck part, the uguru revision 3 actually is a pretty 
> nice chip (except for the lack of specs)

My definition of a bad chip.

>                                          as Rick writes I've written a 
> userspace reading utility for it and it works fine for all people who 
> have tested it (about 7 or so). I've also written a new kernel driver 
> for this new revision (it uses an entirely different "protocol") which 
> I've posted for review some time ago. If when can get some movement on 
> that review then users with a newer uguru will no longer have bad luck, 
> but instead a support chip.

I have many other driver and i2c-core reviews in the works at the
moment so it's unlikely that I will have a spare cycle anytime soon.
Someone else will have to do it.

My "bad luck" still applies. If Abit were using standard chips instead
of their own proprietary undocumented stuff, Rick would have full
hardware monitoring support for his board already. But of course if the
design of these new uGuru chips is better than the original ones,
that's still good news.

-- 
Jean Delvare