[lm-sensors] iwill versus w83627thf

[lm-sensors] iwill versus w83627thf

[Charless Fowlkes]

hello -

has anyone run lm_sensors on an iwill zmaxdp motherboard?

when i run sensors-detect, i get a reasonable answer

Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus nForce2 adapter at e800'
Busdriver `i2c-nforce2', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus nForce2 adapter at e800'
Busdriver `i2c-nforce2', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)

Driver `w83627hf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627THF Super IO Sensors' (confidence: 9)

and have no problem loading the suggested modules

[fowlkes@xor ~]$ lsmod | grep i2c
i2c_sensor 7617 2 w83627hf,eeprom
i2c_isa 6337 0
i2c_nforce2 11073 0
i2c_dev 13761 0
i2c_core 25409 6 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_nforce2,i2c_dev

but sensors only gives me info from eeprom, nothing from the winbond chip.
i'm pretty sure the chip is a w83627thf. i can get sensor values from it
using
"speedfan".

this is a standard fc4 install, lm_sensors v2.9.1, kernel
2.6.13-1.1532_FC4smp.


thanks,
charless

[lm-sensors] iwill versus w83627thf

[Rudolf Marek]

Hello,

Just a quick note:

This has been written by Jean and I think it is your case too:

It's caused by PNPACPI since 2.6.10,
and has been fixed recently. See bug #4014 for additional information:
  http://bugzilla.kernel.org/show_bug.cgi?id@14
If you don't want to upgrade kernels, the workaround is to disable
PNPACPI, either when configuring your kernel or on the boot command line
(pnpacpi=off).

Let me know if you have any (other) problems,

Regards
Rudolf

[lm-sensors] iwill versus w83627thf

[Charless Fowlkes]

thank you! this workaround worked.

On 11/9/05, Rudolf Marek <r.marek@sh.cvut.cz> wrote:
>
>
> It's caused by PNPACPI since 2.6.10,
> and has been fixed recently. See bug #4014 for additional information:
> http://bugzilla.kernel.org/show_bug.cgi?id@14
> If you don't want to upgrade kernels, the workaround is to disable
> PNPACPI, either when configuring your kernel or on the boot command line
> (pnpacpi=off).
>

[lm-sensors] iwill versus w83627thf

[Charless Fowlkes]

On 11/9/05, Rudolf Marek <r.marek@sh.cvut.cz> wrote:
>
>
> It's caused by PNPACPI since 2.6.10,
> and has been fixed recently. See bug #4014 for additional information:
> http://bugzilla.kernel.org/show_bug.cgi?id@14
> If you don't want to upgrade kernels, the workaround is to disable
> PNPACPI, either when configuring your kernel or on the boot command line
> (pnpacpi=off).
>
> Let me know if you have any (other) problems,
>


an interesting thing...this motherboard (iwill zmaxdp) has two cpu
fans, one for each processor. it appears that the fan speed of
both is set to the max of their respective pwm settings on the
w83627thf.

this means that the probing performed by pwmconfig doesn't find
either fan since it only adjusts a single pwm setting at a time while
keeping the others set at their max value.

regards,
charless