Re: Sensors on Asus P2B-F?

[Paul Goyette <paul%whooppee.com@localhost>]

On Mon, 2 Nov 2009, Hauke Fath wrote:

> At 8:38 Uhr -0800 02.11.2009, Paul Goyette wrote:
> > OK, your i2c bus is defined.
> >
> > 1. There's a LMDEBUG option which can be used to enable a debug printf()
> >    in the bus-independant probe routine.
>
> Applied.
>
> > 2. Please also enable I2C_SCAN option (read the warning in options(4)
> >    man page!)
>
> Read and applied.
>
> > 3. Make sure your kernel build includes the file sys/dev/ic/nslm7x.c
>
> Check.
>
> The resulting kernel is very chatty, but has
>
> Nov  2 18:54:42 Riffel /netbsd: iic0 at piixpm0: I2C bus

Hmmm.  If you applied I2C_SCAN, I would have expected to see another 
line similar to

iic0: devices at 0x2e 0x50 0x51

> Nov  2 18:54:42 Riffel /netbsd: lm_probe: rv = 0, cr = 69
> Nov  2 18:54:42 Riffel /netbsd: lm_probe: rv = 1, cr = 1
> Nov  2 18:54:42 Riffel /netbsd: lm3 at iic0 addr 0x2e
> Nov  2 18:54:42 Riffel /netbsd: wb_match: winbond vend id 0x6f6f
> Nov  2 18:54:42 Riffel /netbsd:
> Nov  2 18:54:42 Riffel /netbsd: lm3: Unknown chip (ID 88)
> Nov  2 18:54:42 Riffel /netbsd: lm_probe: rv = 1, cr = 1
> Nov  2 18:54:42 Riffel /netbsd: lm4 at iic0
> Nov  2 18:54:42 Riffel /netbsd: wb_match: winbond vend id 0x0
> Nov  2 18:54:42 Riffel /netbsd:
> Nov  2 18:54:42 Riffel /netbsd: lm4: Unknown chip (ID 88)

Hmmm.  That's an unknown vendor ID as well as an unknown chip.

> and says

Looks like the debug printf() has prevented the match routine from 
returning a failure indication!  With the unknown vendor/chip id's, we 
should never have matched or attached, and none of the following should 
have been possible.  :)  I'll have a look at fixing that soon.

> [hf@Riffel] /var/log # envstat
>              Current  CritMax  CritMin  CritCap     Unit
> [lm3]
>  VCore A:      0.272                                   V
>  VCore B:      1.408                                   V
>    +3.3V:      1.408                                   V
>      +5V:      2.365                                   V
>     +12V:      5.632                                   V
>     -12V:     -5.632                                   V
>      -5V:     -2.347                                   V
>    Temp0:    -36.000                                degC
>     Fan0:       7670                                 RPM
>     Fan1:       7670                                 RPM
>     Fan2:       7670                                 RPM
> [lm4]
>  VCore A:      1.408                                   V
>  VCore B:      1.408                                   V
>    +3.3V:      1.408                                   V
>      +5V:      2.365                                   V
>     +12V:      5.632                                   V
>     -12V:     -5.632                                   V
>      -5V:     -2.347                                   V
>    Temp0:    -36.000                                degC
>     Fan0:       7670                                 RPM
>     Fan1:       7670                                 RPM
>     Fan2:       7670                                 RPM
> [hf@Riffel] /var/log #
>
> The values are a bit off, though... I guess the "Unknown chip id" needs to be 
> registered somewhere?

Pretty much, we're reading nonsense.  This is to be expected if there is 
either no device there, or if the device there doesn't behave as 
expected (ie, doesn't respond to specific "commands").


-------------------------------------------------------------------------
|   Paul Goyette   | PGP DSS Key fingerprint: |  E-mail addresses:      |
| Customer Service | FA29 0E3B 35AF E8AE 6651 |  paul at whooppee.com   |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------