lmsensors on Abit IC7-G

lmsensors on Abit IC7-G

[Nicolai Langfeldt]

Hi,

On my Abit IC7-G there is a ICH5 chipset.  Once sensors-detect has been
updated with the 24d3 device id it generates a nice lm-sensors
configuration. Unfortunately there are no real temperature readings 
(there should be quite a few according to BIOS) or any fan-speeds (2 to 
4 should be right).  I also wonder about the corectness of the voltage 
readings.  In the BIOS display they are all 10% or less off nominal.

Is there anything I can test to see if I get more or more correct readings?

# lspci -n -v -s 00:1f.3
00:1f.3 Class 0c05: 8086:24d3 (rev 02)
         Subsystem: 147b:1014
         Flags: medium devsel, IRQ 17
         I/O ports at 0500 [size2]
# lspci -v -s 00:1f.3
00:1f.3 SMBus: Intel Corp. 82801EB SMBus (rev 02)
         Subsystem: ABIT Computer Corp.: Unknown device 1014
         Flags: medium devsel, IRQ 17
         I/O ports at 0500 [size2]

# cat /etc/sysconfig/lm_sensors
..
# Generated by sensors-detect on Mon Nov 17 20:01:45 2003
MODULE_0=i2c-i801
MODULE_1=lm80
MODULE_2îprom
# sensors
lm80-i2c-0-2e
Adapter: SMBus I801 adapter at 0500
Algorithm: Non-I2C SMBus adapter
+5V:       +6.71 V  (min =  +6.71 V, max =  +6.71 V)
VTT:       +2.55 V  (min =  +2.55 V, max =  +2.55 V)
+3.3V:     +4.43 V  (min =  +4.43 V, max =  +4.43 V)
+Vcore:    +3.76 V  (min =  +3.76 V, max =  +3.76 V)   ALARM
+12V:     +16.10 V  (min = +16.10 V, max = +16.10 V)
-12V:     -16.11 V  (min = -16.11 V, max = -16.11 V)
-5V:       -6.70 V  (min =  -6.70 V, max =  -6.70 V)
fan1:        0 RPM  (min =    0 RPM, div = 1)
fan2:        0 RPM  (min =    0 RPM, div = 1)
temp:     -1.00 ?C (hot:limit =  -1?C,  hysteresis =  -1?C)
          (os: limit =  -1?C,  hysteresis =  -1?C)
alarms:   Board temperature input (LM75)               ALARM

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0500
Algorithm: Non-I2C SMBus adapter
Memory type:            DDR SDRAM DIMM SPD
SDRAM Size (MB):        512

eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0500
Algorithm: Non-I2C SMBus adapter
Memory type:            DDR SDRAM DIMM SPD
SDRAM Size (MB):        512

Thanks and regards,
   Nicolai

lmsensors on Abit IC7-G

[Jean Delvare]

> MODULE_0=i2c-i801
> MODULE_1=lm80
> MODULE_2îprom
> # sensors
> lm80-i2c-0-2e
> Adapter: SMBus I801 adapter at 0500
> Algorithm: Non-I2C SMBus adapter
> +5V:       +6.71 V  (min =  +6.71 V, max =  +6.71 V)
> VTT:       +2.55 V  (min =  +2.55 V, max =  +2.55 V)
> +3.3V:     +4.43 V  (min =  +4.43 V, max =  +4.43 V)
> +Vcore:    +3.76 V  (min =  +3.76 V, max =  +3.76 V)   ALARM
> +12V:     +16.10 V  (min = +16.10 V, max = +16.10 V)
> -12V:     -16.11 V  (min = -16.11 V, max = -16.11 V)
> -5V:       -6.70 V  (min =  -6.70 V, max =  -6.70 V)
> fan1:        0 RPM  (min =    0 RPM, div = 1)
> fan2:        0 RPM  (min =    0 RPM, div = 1)
> temp:     -1.00 ?C (hot:limit =  -1?C,  hysteresis =  -1?C)
>           (os: limit =  -1?C,  hysteresis =  -1?C)
> alarms:   Board temperature input (LM75)               ALARM

Wild guess: this isn't a LM80. No value here make sense. What you have
here is obviously another model of sensoring chipset.

Which version of lm_sensors are you using? Please try a recent version
of sensors-detect (preferably from CVS), it should be able to identify
the chip correctly.

If not, please send the output of "i2cdump 0 0x2e", we'll take a look
and try to identify the chip.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

lmsensors on Abit IC7-G

[Nicolai Langfeldt]

Jean Delvare wrote:
>>MODULE_0=i2c-i801
>>MODULE_1=lm80
>>MODULE_2îprom
>># sensors
>>lm80-i2c-0-2e
>>Adapter: SMBus I801 adapter at 0500
>>Algorithm: Non-I2C SMBus adapter
>>+5V:       +6.71 V  (min =  +6.71 V, max =  +6.71 V)
>>VTT:       +2.55 V  (min =  +2.55 V, max =  +2.55 V)
>>+3.3V:     +4.43 V  (min =  +4.43 V, max =  +4.43 V)
>>+Vcore:    +3.76 V  (min =  +3.76 V, max =  +3.76 V)   ALARM
>>+12V:     +16.10 V  (min = +16.10 V, max = +16.10 V)
>>-12V:     -16.11 V  (min = -16.11 V, max = -16.11 V)
>>-5V:       -6.70 V  (min =  -6.70 V, max =  -6.70 V)
>>fan1:        0 RPM  (min =    0 RPM, div = 1)
>>fan2:        0 RPM  (min =    0 RPM, div = 1)
>>temp:     -1.00 ?C (hot:limit =  -1?C,  hysteresis =  -1?C)
>>          (os: limit =  -1?C,  hysteresis =  -1?C)
>>alarms:   Board temperature input (LM75)               ALARM
> 
> 
> Wild guess: this isn't a LM80. No value here make sense. What you have
> here is obviously another model of sensoring chipset.
> 
> Which version of lm_sensors are you using? Please try a recent version
> of sensors-detect (preferably from CVS), it should be able to identify
> the chip correctly.

It is 2.8.1 and the corresponding patch to 2.4.22.

> If not, please send the output of "i2cdump 0 0x2e", we'll take a look
> and try to identify the chip.

# i2cdump 0 0x2e
No size specified (using byte-data access)
   WARNING! This program can confuse your I2C bus, cause data loss and 
worse!
   I will probe file /dev/i2c-0, address 0x2e, mode byte
   You have five seconds to reconsider and press CTRL-C!

      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 11 08 02 00 00 03 08 ff ff ff ff ff ff ff ff ff    ???..??.........
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................

That's very negative isn't it :-)

Nicolai

lmsensors on Abit IC7-G

[Jean Delvare]

> # i2cdump 0 0x2e
> (...)
> That's very negative isn't it :-)

Yes it is. I don't know what it is, but this is no LM80 for sure. We
would need to enhance our detection routine so that doesn't fall in that
kind of trap.

I'm curious. If you dump the chip again now, does it contain exactly the
same data or not?

According to MBM's site, the monitoring chip on your motherboard is a 
W83627HF. They also have that note: "select your board from the
installer to avoid problems". It could mean that there is some special
action to take before being able to access the chip.

Could you provide the full output of sensors-detect (CVS version if
possible)?
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/prog/detect/sensors-detect

If it doesn't show that chipset, we'll have to ask Alex (MBM's author)
how he has been solving the problem.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

lmsensors on Abit IC7-G

[Nicolai Langfeldt]

Jean Delvare wrote:
>># i2cdump 0 0x2e
>>(...)
>>That's very negative isn't it :-)
>
> Yes it is. I don't know what it is, but this is no LM80 for sure. We
> would need to enhance our detection routine so that doesn't fall in that
> kind of trap.
> 
> I'm curious. If you dump the chip again now, does it contain exactly the
> same data or not?

# i2cdump 0 0x2e
..
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 11 08 02 00 00 03 08 ff ff ff ff ff ff ff ff ff    ???..??.........
..

Yes.  That is exactly the same data.

> Could you provide the full output of sensors-detect (CVS version if
> possible)?
>> http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/prog/detect/sensors-detect

OK.  Downloaded that and ran.  Assumptions:
- This is a pure PCI system, no ISA bus so no ISA probe, Intel ICH5 
chipset is correct.
- The ABIT mobo docs refers to this as a SMBus.

Here is the complete run:

# ./sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built-in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

  BIOS vendor (ACPI): IntelR
  We can start with probing for (PCI) I2C or SMBus adapters.
  You do not need any special privileges for this.
  Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

  We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
  Do you now want to be prompted for non-detectable adapters? (yes/NO): no
  To continue, we need module `i2c-dev' to be loaded.
  If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

  We are now going to do the adapter probings. Some adapters may hang 
halfway
  through; we can't really help that. Also, some chips will be double 
detected;
  we choose the one with the highest confidence value in that case.
  If you found that the adapter hung after probing a certain address, 
you can
  specify that address to remain unprobed. That often
  includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 0500 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x08
Client at address 0x2e can not be probed - unload all client drivers first!
Client found at address 0x44
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x52 can not be probed - unload all client drivers first!
Client found at address 0x69

  Some chips are also accessible through the ISA bus. ISA probes are
  typically a bit more dangerous, as we have to write to I/O ports to do
  this.  Do you want to scan the ISA bus? (YES/no): no

  Some Super I/O chips may also contain sensors. Super I/O probes are
  typically a bit more dangerous, as we have to write to I/O ports to do
  this.  Do you want to scan for Super I/O sensors? (YES/no): no

  Sorry, no chips were detected.
  Either your sensors are not supported, or they are
  connected to an I2C bus adapter that we do not support.
  See doc/FAQ, doc/lm_sensors-FAQ.html, or
  http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/lm_sensors-FAQ.html
  (FAQ #4.24.3) for further information.
  If you find out what chips are on your board, see
  http://secure.netroedge.com/~lm78/newdrivers.html for driver status.


This suggests some more addresses on the bus to dump:

root@roke /var/tmp # i2cdump 0 0x8
..
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX

# i2cdump 0 0x44
..
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 0f 2a 00 00 00 00 00 00 00 00 00 00 00 00    ..?*............

# i2cdump 0 0x69
..
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
10: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
20: 0f 1f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
30: 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f 0f    ????????????????
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX

I also got this in dmesg:

i2c-dev.o: Registered 'SMBus I801 adapter at 0500' as minor 0
Intel Corp. 82801EB SMBus Controller: Bus collision! SMBus may be locked 
until next hard reset. (sorry!)

I then reran after unloading all i2c modules:

# ./sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built-in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

  BIOS vendor (ACPI): IntelR
  We can start with probing for (PCI) I2C or SMBus adapters.
  You do not need any special privileges for this.
  Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

  We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
  Do you now want to be prompted for non-detectable adapters? (yes/NO): no
  To continue, we need module `i2c-dev' to be loaded.
  If it is built-in into your kernel, you can safely skip this.
  i2c-dev is not loaded. Do you want to load it now? (YES/no): yes
  Module loaded succesfully.

  We are now going to do the adapter probings. Some adapters may hang 
halfway
  through; we can't really help that. Also, some chips will be double 
detected;
  we choose the one with the highest confidence value in that case.
  If you found that the adapter hung after probing a certain address, 
you can
  specify that address to remain unprobed. That often
  includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 0500 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): ues

  Some chips are also accessible through the ISA bus. ISA probes are
  typically a bit more dangerous, as we have to write to I/O ports to do
  this.  Do you want to scan the ISA bus? (YES/no): yes
Probing for `National Semiconductor LM78'
   Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
   Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
   Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
   Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
   Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
   Trying address 0x0290... Success!
     (confidence 8, driver `w83781d')
Probing for `Winbond W83697HF'
   Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
   Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
   Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
   Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
   Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
   Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
   Trying address 0x0ca8... Failed!

  Some Super I/O chips may also contain sensors. Super I/O probes are
  typically a bit more dangerous, as we have to write to I/O ports to do
  this.  Do you want to scan for Super I/O sensors? (YES/no): no

  Now follows a summary of the probes I have just done.
  Just press ENTER to continue:

Driver `w83781d' (should be inserted):
   Detects correctly:
   * ISA bus address 0x0290 (Busdriver `i2c-isa')
     Chip `Winbond W83627HF' (confidence: 8)


  I will now generate the commands needed to load the I2C modules.
  Sometimes, a chip is available both through the ISA bus and an I2C bus.
  ISA bus access is faster, but you need to load an additional driver module
  for it. If you have the choice, do you want to use the ISA bus or the
  I2C/SMBus (ISA/smbus)? smbus

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83781d
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
root@roke /var/tmp # modprobe i2c-isa
root@roke /var/tmp # modprobe w83781d
# LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/sensors -s #>
No sensors found!

Try over again:

# rmmod i2c-i801 i2c-dev i2c-isa w83781d
# insmod i2c-isa
Using /lib/modules/2.4.22-ICH5II+lvm+i2c/kernel/drivers/i2c/i2c-isa.o
# insmod w83781d
Using /lib/modules/2.4.22-ICH5II+lvm+i2c/kernel/drivers/i2c/w83781d.o
# modprobe i2c-dev
# modprobe i2c-proc
# LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/sensors -s
No sensors found!

Regards,
   Nicolai

lmsensors on Abit IC7-G

[Jean Delvare]

> - This is a pure PCI system, no ISA bus so no ISA probe, Intel ICH5 
> chipset is correct.

You're wrong. You might not have ISA slots, still you *do* have an ISA
bus. Almost everybody does. And that's probably where your monitoring
chipset is hiding.

> Probing for `Winbond W83627HF'
>    Trying address 0x0290... Success!
>      (confidence 8, driver `w83781d')

Here it is.

>   Some Super I/O chips may also contain sensors. Super I/O probes are
>   typically a bit more dangerous, as we have to write to I/O ports to
>   do this.  Do you want to scan for Super I/O sensors? (YES/no): no

Error. You want to say yes. It will detect the W83627HF driver again,
and propose an alternate (and better) driver.

That said, the w83781d should have worked also, but W83627HF detection
is known to be broken in 2.8.1. I have fixed it since (2003-10-25) so if
you check lm_sensors2 CVS out, you should be able to use the w83781d
driver. But anyway, try Super I/O, it should give even better results.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

lmsensors on Abit IC7-G

[Jean Delvare]

> I don't know what it is, but this is no LM80 for sure. We
> would need to enhance our detection routine so that doesn't fall in
> that kind of trap.

I just commited such a change to sensors-detect in CVS. Could you please
check it out and give it a try (after unloading all chip drivers, of
course)? If shouldn't detect a LM80 anymore.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

lmsensors on Abit IC7-G

[Nicolai Langfeldt]

Jean Delvare wrote:
>>- This is a pure PCI system, no ISA bus so no ISA probe, Intel ICH5 
>>chipset is correct.
> 
> 
> You're wrong. You might not have ISA slots, still you *do* have an ISA
> bus. Almost everybody does. And that's probably where your monitoring
> chipset is hiding.
> 
> 
>>Probing for `Winbond W83627HF'
>>   Trying address 0x0290... Success!
>>     (confidence 8, driver `w83781d')
> 
> 
> Here it is.

Oh well O:-)

> That said, the w83781d should have worked also, but W83627HF detection
> is known to be broken in 2.8.1. I have fixed it since (2003-10-25) so if
> you check lm_sensors2 CVS out, you should be able to use the w83781d
> driver. But anyway, try Super I/O, it should give even better results.

The CVS version worked better:

# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

  BIOS vendor (ACPI): IntelR
  We can start with probing for (PCI) I2C or SMBus adapters.
  You do not need any special privileges for this.
  Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

  We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
  Do you now want to be prompted for non-detectable adapters? (yes/NO): no
  To continue, we need module `i2c-dev' to be loaded.
  If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

  We are now going to do the adapter probings. Some adapters may hang 
halfway
  through; we can't really help that. Also, some chips will be double 
detected;
  we choose the one with the highest confidence value in that case.
  If you found that the adapter hung after probing a certain address, 
you can
  specify that address to remain unprobed. That often
  includes address 0x69 (clock chip).

Next adapter: SMBus I801 adapter at 0500 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively): yes

  Some chips are also accessible through the ISA bus. ISA probes are
  typically a bit more dangerous, as we have to write to I/O ports to do
  this.  Do you want to scan the ISA bus? (YES/no): yes
Probing for `National Semiconductor LM78'
   Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
   Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
   Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
   Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
   Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
   Trying address 0x0290... Success!
     (confidence 8, driver `w83781d')
Probing for `Winbond W83697HF'
   Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
   Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
   Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
   Trying general detect... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'
   Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
   Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
   Trying address 0x0ca8... Failed!

  Some Super I/O chips may also contain sensors. Super I/O probes are
  typically a bit more dangerous, as we have to write to I/O ports to do
  this.  Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `SMSC 47M10x Super IO Fan Sensors'
   Failed! (0x00)
Probing for `SMSC 47M14x Super IO Fan Sensors'
   Failed! (0x00)
Probing for `VT1211 Super IO Sensors'
   Failed! (0x52)
Probing for `Winbond W83627HF Super IO Sensors'
   Success... found at address 0x0290
Probing for `Winbond W83627THF Super IO Sensors'
   Failed! (0x52)
Probing for `Winbond W83637HF Super IO Sensors'
   Failed! (0x52)
Probing for `Winbond W83697HF Super IO Sensors'
   Failed! (0x52)
Probing for `Winbond W83697UF Super IO PWM'
   Failed! (0x52)

  Now follows a summary of the probes I have just done.
  Just press ENTER to continue:

Driver `w83781d' (may not be inserted):
   Misdetects:
   * ISA bus address 0x0290 (Busdriver `i2c-isa')
     Chip `Winbond W83627HF' (confidence: 8)

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


  I will now generate the commands needed to load the I2C modules.
  Sometimes, a chip is available both through the ISA bus and an I2C bus.
  ISA bus access is faster, but you need to load an additional driver module
  for it. If you have the choice, do you want to use the ISA bus or the
  I2C/SMBus (ISA/smbus)? smbus

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
modprobe w83627hf
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
# rmmod w83627hf i2c-isa i2c-proc i2c-dev i2c-i801 i2c-core
# /etc/init.d/lm_sensors start
Starting up sensors: starting module __i2c-isa__
starting module __w83627hf__
                                                            [  OK  ]
# /usr/local/bin/sensors
w83627hf-isa-0290
Adapter: ISA adapter
Algorithm: ISA algorithm
VCore 1:   +1.50 V  (min =  +0.00 V, max =  +0.00 V)
VCore 2:   +2.59 V  (min =  +0.00 V, max =  +0.00 V)
+3.3V:     +3.24 V  (min =  +3.13 V, max =  +3.45 V)
+5V:       +4.97 V  (min =  +4.72 V, max =  +5.24 V)
+12V:     +11.97 V  (min = +10.79 V, max = +13.19 V)
-12V:      -8.33 V  (min = -13.21 V, max = -10.90 V)
-5V:       -2.94 V  (min =  -5.26 V, max =  -4.76 V)
V5SB:      +5.53 V  (min =  +4.72 V, max =  +5.24 V)
VBat:      +3.29 V  (min =  +2.40 V, max =  +3.60 V)
fan1:     2008 RPM  (min =  166 RPM, div = 32)
fan2:     5273 RPM  (min =  166 RPM, div = 32)
fan3:        0 RPM  (min =  332 RPM, div = 16)              ALARM
temp1:       +31?C  (high =    +0?C, hyst =    +0?C)   sensor = thermistor
temp2:     +44.0?C  (high =   +85?C, hyst =   +80?C)   sensor = 
PII/Celeron diode
temp3:     +33.0?C  (high =   +85?C, hyst =   +80?C)   sensor = thermistor
vid:      +0.000 V
alarms:
beep_enable:
           Sound alarm disabled

This looks like real results.  The -12V is a bit worrying.  I'll compare 
with BIOS and tweak or whatever.

Thanks a lot,
   Nicolai

lmsensors on Abit IC7-G

[Jean Delvare]

> The CVS version worked better:
> 
> # sensors-detect
> (...)
> Next adapter: SMBus I801 adapter at 0500 (Non-I2C SMBus adapter)
> Do you want to scan it? (YES/no/selectively): yes
> 
>   Some chips are also accessible through the ISA bus. ISA probes are
>   typically a bit more dangerous, as we have to write to I/O ports to
>   do this.  Do you want to scan the ISA bus? (YES/no): yes

Hm, did it really happen that way, or have you been cutting a part? (I
hope so.)

> Driver `w83781d' (may not be inserted):
>    Misdetects:
>    * ISA bus address 0x0290 (Busdriver `i2c-isa')
>      Chip `Winbond W83627HF' (confidence: 8)
> 
> Driver `w83627hf' (should be inserted):
>    Detects correctly:
>    * ISA bus address 0x0290 (Busdriver `i2c-isa')
>      Chip `Winbond W83627HF Super IO Sensors' (confidence: 9)

Exactly what I had expected.

> # /usr/local/bin/sensors
> w83627hf-isa-0290
> Adapter: ISA adapter
> Algorithm: ISA algorithm
> VCore 1:   +1.50 V  (min =  +0.00 V, max =  +0.00 V)
> VCore 2:   +2.59 V  (min =  +0.00 V, max =  +0.00 V)
> +3.3V:     +3.24 V  (min =  +3.13 V, max =  +3.45 V)
> +5V:       +4.97 V  (min =  +4.72 V, max =  +5.24 V)
> +12V:     +11.97 V  (min = +10.79 V, max = +13.19 V)
> -12V:      -8.33 V  (min = -13.21 V, max = -10.90 V)
> -5V:       -2.94 V  (min =  -5.26 V, max =  -4.76 V)
> V5SB:      +5.53 V  (min =  +4.72 V, max =  +5.24 V)
> VBat:      +3.29 V  (min =  +2.40 V, max =  +3.60 V)
> fan1:     2008 RPM  (min =  166 RPM, div = 32)
> fan2:     5273 RPM  (min =  166 RPM, div = 32)
> fan3:        0 RPM  (min =  332 RPM, div = 16)              ALARM
> temp1:       +31?C  (high =    +0?C, hyst =    +0?C)
> temp2:     +44.0?C  (high =   +85?C, hyst =   +80?C)
> temp3:     +33.0?C  (high =   +85?C, hyst =   +80?C)
> vid:      +0.000 V
> (...)
> This looks like real results.  The -12V is a bit worrying.  I'll
> compare with BIOS and tweak or whatever.

Most chips don't monitor negative voltages anymore. I would bet that
your BIOS won't show these values either, so you can safely ignore them
(add "ignore" statements in your configuration file).

VCore 1/2 limits are wrong because of your bad vid reading (last line).
Try changing the vrm to 9.0 (uncomment one line in the configuration
file) and run "sensors -s", see if it helps. If it doesn't, set these
limits using real values instead of references to vid.

Fan values look OK, limits are way too low. Try changing divisors
(typical value is 2), it might help. Don't forget to run "sensors -s" as
root afterwards.

Temperatures look OK too, except the missing limits for temp1. Tweak
your config file to set the limits as you want them.

After that, you should have a fine-tuned hardware monitoring
configuration :)

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/