[lm-sensors] No temperature/fan values with 83627THF chip

[lm-sensors] No temperature/fan values with 83627THF chip

[Jon Still]

Hi,

I've been having problems with h/w sensors on a Supermicro P8SCi that 
came as a barebones 1U server (Supermicro 5014C-T).

See http://www.supermicro.com/products/system/1U/5014/SYS-5014C-T.cfm
which claims the board has a 83627THF chip.  I can now detect and load the 
module for this chip, but my temperatures and fan speeds are reported 
erroneously.

This is using: sensors version 2.9.0 with libsensors version 2.9.0
on: Linux 2.6.11-gentoo-r8 #1 SMP Thu May 19 19:00:00 BST 2005 i686 

'sensors' gives this output:
w83627thf-isa-0290
Adapter: ISA adapter
VCore:     +1.94 V  (min =  +1.94 V, max =  +1.94 V)       ALARM  (beep)
+12V:     +15.50 V  (min = +15.50 V, max = +15.50 V)       ALARM  (beep)
+3.3V:     +4.08 V  (min =  +4.08 V, max =  +4.08 V)       ALARM  (beep)
+5V:       +6.80 V  (min =  +6.80 V, max =  +6.80 V)       ALARM  (beep)
-12V:     -14.91 V  (min = -10.80 V, max = -13.18 V)       ALARM  (beep)
V5SB:      +6.85 V  (min =  +6.85 V, max =  +6.85 V)       ALARM  (beep)
VBat:      +4.08 V  (min =  +4.08 V, max =  +4.08 V)       ALARM  (beep)
fan1:        0 RPM  (min =    0 RPM, div = 128)              ALARM  (beep)
CPU Fan:     0 RPM  (min =    0 RPM, div = 128)              ALARM  (beep)
fan3:        0 RPM  (min =    0 RPM, div = 128)              ALARM  (beep)
M/B Temp:     -1 C  (high =    -1 C, hyst =    -1 C)   sensor = diode   
ALARM   (beep)
CPU Temp:   +0.0 C  (high =    +0 C, hyst =    +0 C)   sensor = diode   
ALARM   (beep)
vid:      +0.275 V  (VRM Version 9.0)
alarms:   Chassis intrusion detection                      ALARM
beep_enable:
          Sound alarm enabled

eeprom-i2c-0-51
Adapter: SMBus I801 adapter at 0500
Memory type:            DDR2 SDRAM DIMM
Memory size (MB):       1024

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0500
Memory type:            DDR2 SDRAM DIMM
Memory size (MB):       1024

'lsmod' reports:
w83627hf               29480  0 
eeprom                  6800  0 
i2c_sensor              3968  2 w83627hf,eeprom
i2c_isa                 2816  0 
i2c_i801                8716  0 
i2c_core               19200  5 w83627hf,eeprom,i2c_sensor,i2c_isa,i2c_i801

The output of 'sensors-detect' is attached.  The sensor hardware is 
definitely working correctly as I get both fan and CPU readings in the 
BIOS.  Also, when I start lm_sensors using Gentoo's init script, it fails 
trying to load smbus-arp, as the module does not exist.  However from 
googling, I'm unsure if this is important or not!

If anyone can help, I'd be most grateful as I'm drawing blanks at the 
moment!

Thanks,
Jon.

-- 
Jon Still                               E-mail: jon@tertial.org
tertial.org                             Web:    http://www.tertial.org/
GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B

[lm-sensors] No temperature/fan values with 83627THF chip

[Rudolf Marek]

Hi,

The page says it support IPMI. Unfortunately I do not know much about IPMI too.
Basicaly it is some platform for idependent management including sensors.
Maybe you should take a look to openipmi.sf.net Also to i2c-ipmi and bmcsensors.
(they are part of lm_sensors package if I recall corectly)
I think they are currently ported to 2.6. So I suggest to try 2.4 kernel version first.

I hope others on the list will add missing info :)

As for the rest:

> 'sensors' gives this output:
> w83627thf-isa-0290
> Adapter: ISA adapter
> VCore:     +1.94 V  (min =  +1.94 V, max =  +1.94 V)       ALARM  (beep)
> +12V:     +15.50 V  (min = +15.50 V, max = +15.50 V)       ALARM  (beep)
> +3.3V:     +4.08 V  (min =  +4.08 V, max =  +4.08 V)       ALARM  (beep)
> +5V:       +6.80 V  (min =  +6.80 V, max =  +6.80 V)       ALARM  (beep)
> -12V:     -14.91 V  (min = -10.80 V, max = -13.18 V)       ALARM  (beep)
> V5SB:      +6.85 V  (min =  +6.85 V, max =  +6.85 V)       ALARM  (beep)
> VBat:      +4.08 V  (min =  +4.08 V, max =  +4.08 V)       ALARM  (beep)

Voltage conversion formulas are known by manufacturer only. Or they may be even left floating.

> fan1:        0 RPM  (min =    0 RPM, div = 128)              ALARM  (beep)
> CPU Fan:     0 RPM  (min =    0 RPM, div = 128)              ALARM  (beep)
> fan3:        0 RPM  (min =    0 RPM, div = 128)              ALARM  (beep)

Try setting fan divisor to 2 or 4 or 8. But it is more likely not connected.

Put similar lines to correct part of sensors.conf
set fan1_div 2

dont forget to run sensors -s to "apply" changes.

> M/B Temp:     -1 C  (high =    -1 C, hyst =    -1 C)   sensor = diode   
> ALARM   (beep)
> CPU Temp:   +0.0 C  (high =    +0 C, hyst =    +0 C)   sensor = diode   
> ALARM   (beep)

Again if there is smth connected it is not connected in "recomended" way so again we do not know the formulas.

> vid:      +0.275 V  (VRM Version 9.0)
Hmm this is strange. Anyone some ideas?

Recomended steps:
Try above and pay attention to IPMI.

I hope this helps a bit.

Regards

Rudolf

[lm-sensors] No temperature/fan values with 83627THF chip

[Rudolf Marek]

Hi again

Jean noticed that most of the values corresponds to raw 0xFF.
Can you please provide sensors-detect output and output from following command:

isadump 0x295 0x296

Thanks
regards

Rudolf

[lm-sensors] No temperature/fan values with 83627THF chip

[Jon Still]

On Fri, 20 May 2005, Rudolf Marek wrote:

> Jean noticed that most of the values corresponds to raw 0xFF.
> Can you please provide sensors-detect output and output from following command:
> 
> isadump 0x295 0x296

Sensors-detect output was attached to the original post, but here it is 
again, just in case!

Isadump output:

# isadump 0x295 0x296
WARNING! Running this program can cause system crashes, data loss and 
worse!
I will probe address register 0x295 and data register 0x296.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: ff ff ff ff ff ff ff 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

I'll also take a look at the various IPMI projects you mentioned.

Many thanks,
Jon.

-- 
Jon Still                               E-mail: jon@tertial.org
tertial.org                             Web:    http://www.tertial.org/
GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B
-------------- next part --------------
'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.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 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 ICH6
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 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 (Algorithm unavailable)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!
Client found at address 0x30
Client found at address 0x31
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4b
Probing for `National Semiconductor LM75'... Success!
    (confidence 6, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Probing for `National Semiconductor LM92'... Failed!
Probing for `National Semiconductor LM76'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4f
Probing for `National Semiconductor LM75'... Success!
    (confidence 6, driver `lm75')
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x60
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
    (confidence 1, driver `smbus-arp')
Client found at address 0x69
Client found at address 0x6a

Do you want to scan the ISA bus? (YES/no): y
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... Failed!
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. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
  Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
  Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
  Failed! (0x82)

Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)

 Now follows a summary of the probes I have just done.
 Just press ENTER to continue: 
Driver `lm75' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x4b
    Chip `National Semiconductor LM75' (confidence: 6)
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x4f
    Chip `National Semiconductor LM75' (confidence: 6)

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x50
    Chip `SPD EEPROM' (confidence: 8)
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x51
    Chip `SPD EEPROM' (confidence: 8)

Driver `smbus-arp' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500' (Algorithm unavailable)
    Busdriver `i2c-i801', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627THF 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)? isa

If you want to load the modules at startup, generate a config file
below and make sure lm_sensors gets started; e.g
$ rc-update add lm_sensors default.

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
#----end 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.
To load everything that is needed, execute the commands above...

#----cut here----
# I2C adapter drivers
modprobe i2c-i801
modprobe i2c-isa
# I2C chip drivers
modprobe lm75
modprobe eeprom
modprobe smbus-arp
modprobe w83627hf
# sleep 2 # optional
/usr/bin/sensors -s # recommended

Do you want to overwrite /etc/conf.d/lm_sensors? Enter s to specify other file name?
  (yes/NO/s): y
Done.

[lm-sensors] No temperature/fan values with 83627THF chip

[Rudolf Marek]

Hi again,

> 
> Sensors-detect output was attached to the original post, but here it is 
> again, just in case!

I asked because it was not there :)

> 
> Isadump output:
> f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

Hmm that I strange. Please can you reboot without loading the module and
do: cat /proc/ioports Thanks.


> I'll also take a look at the various IPMI projects you mentioned.

> Client found at address 0x2f
> Probing for `National Semiconductor LM78'... Failed!
> Probing for `National Semiconductor LM78-J'... Failed!
> Probing for `National Semiconductor LM79'... Failed!
> Probing for `National Semiconductor LM80'... Failed!
> Probing for `Winbond W83781D'... Failed!
> Probing for `Winbond W83782D'... Failed!
> Probing for `Winbond W83791D'... Failed!
> Probing for `Winbond W83627HF'... Failed!
> Probing for `Asus AS99127F (rev.1)'... Failed!
> Probing for `Asus AS99127F (rev.2)'... Failed!
> Probing for `Asus ASB100 Bach'... Failed!
> Probing for `Analog Devices ADM9240'... Failed!
> Probing for `Dallas Semiconductor DS1780'... Failed!
> Probing for `National Semiconductor LM81'... Failed!
> Probing for `Analog Devices ADM1029'... Failed!
> Probing for `ITE IT8705F / IT8712F / SiS 950'... Failed!

See? Nothing Is detected but this address often used for HW monitoring.

> Client found at address 0x4b

Typical subclient address  #1
> Client found at address 0x4f
Typical subclient address  #2

Please can you try sensors-detect from CVS or from 2.9.1 version? We are thinking you have Winbond W83792D that is used for HW monitoring.
You can find the driver in lm_sensors 2.9.1. The driver is currently ported to 2.6 so it is only avaiable for 2.4 kernels
now.

Regards

Rudolf

[lm-sensors] No temperature/fan values with 83627THF chip

[Jon Still]

On Sat, 21 May 2005, Rudolf Marek wrote:

> Hmm that I strange. Please can you reboot without loading the module and
> do: cat /proc/ioports Thanks.

OK.  After rebooting I found that i2c_i801 and i2c_core were still being 
loaded, but that was all:

i2c_i801                8716  0
i2c_core               19200  1 i2c_i801

and ioports looks like:

0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
02f8-02ff : serial
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial
0400-0403 : PM1a_EVT_BLK
0404-0405 : PM1a_CNT_BLK
0408-040b : PM_TMR
0428-042f : GPE0_BLK
0500-051f : 0000:00:1f.3
  0500-0507 : i801-smbus
d000-dfff : PCI Bus #01
  d000-dfff : PCI Bus #02
    d000-d00f : 0000:02:01.0
      d000-d00f : 3w-xxxx
e000-e007 : 0000:00:02.0
e100-e11f : 0000:00:1d.0
  e100-e11f : uhci_hcd
e200-e21f : 0000:00:1d.1
  e200-e21f : uhci_hcd
e300-e31f : 0000:00:1d.2
  e300-e31f : uhci_hcd
e400-e41f : 0000:00:1d.3
  e400-e41f : uhci_hcd
f000-f00f : 0000:00:1f.1
  f000-f007 : ide0
  f008-f00f : ide1

> Please can you try sensors-detect from CVS or from 2.9.1 version? We are thinking you have Winbond W83792D that is used for HW monitoring.
> You can find the driver in lm_sensors 2.9.1. The driver is currently ported to 2.6 so it is only avaiable for 2.4 kernels
> now.

Will do - I'll let you know.

Thanks once again!

Cheers,
Jon.

-- 
Jon Still                               E-mail: jon@tertial.org
tertial.org                             Web:    http://www.tertial.org/
GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B

[lm-sensors] No temperature/fan values with 83627THF chip

[Jon Still]

On Sat, 21 May 2005, Rudolf Marek wrote:
> 
> Please can you try sensors-detect from CVS or from 2.9.1 version? We are thinking you have Winbond W83792D that is used for HW monitoring.
> You can find the driver in lm_sensors 2.9.1. The driver is currently ported to 2.6 so it is only avaiable for 2.4 kernels
> now.

Right, I downloaded 2.9.1 and did make user and make user_install.  This 
is still on 2.6.11 as going back to 2.4 on this box isn't desirable (the 
box is in a remote datacenter).

Output is attached, but this is probably what you're looking for:

Probing for `Winbond W83792D'... Success!
    (confidence 7, driver `to-be-written'), other addresses: 0x4b 0x4f

Looks like your guess paid off :)

So I guess my next qustion is...what's the timeline for porting this 
driver to 2.6?

Many thanks,
Jon.

-- 
Jon Still                               E-mail: jon@tertial.org
tertial.org                             Web:    http://www.tertial.org/
GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B
-------------- next part --------------
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.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

 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 82801FB ICH6
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

 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): y
 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
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Success!
    (confidence 7, driver `to-be-written'), other addresses: 0x4b 0x4f
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
Client found at address 0x30
Client found at address 0x31
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4b
Probing for `National Semiconductor LM75'... Failed!
Probing for `National Semiconductor LM77'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6650/MAX6651'... Failed!
Probing for `National Semiconductor LM92'... Failed!
Probing for `National Semiconductor LM76'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x4f
Probing for `National Semiconductor LM75'... Failed!
Probing for `Dallas Semiconductor DS1621'... Failed!
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
    (confidence 8, driver `eeprom')
Client found at address 0x60
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
    (confidence 1, driver `smbus-arp')
Client found at address 0x69
Client found at address 0x6a

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. This is usually safe though.

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... Failed!
Probing for `Winbond W83627EHF'
  Trying address 0x0290... Failed!
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 IT8712F'
  Trying address 0x0290... Failed!
Probing for `ITE IT8705F / 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. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83627HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83627THF Super IO Sensors'
  Success... found at address 0x0290
Probing for `Winbond W83637HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83697HF Super IO Sensors'
  Failed! (0x82)
Probing for `Winbond W83697SF/UF Super IO PWM'
  Failed! (0x82)
Probing for `Winbond W83L517D Super IO'
  Failed! (0x82)
Probing for `Winbond W83627EHF Super IO Sensors'
  Failed! (0x8285)

Do you want to scan for secondary Super I/O sensors? (YES/no): yes
Probing for `ITE 8702F Super IO Sensors'
  Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
  Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
  Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
  Failed! (skipping family)

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

Driver `to-be-written' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500'
    Busdriver `i2c-i801', I2C address 0x2f (and 0x4b 0x4f)
    Chip `Winbond W83792D' (confidence: 7)

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

Driver `smbus-arp' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0500'
    Busdriver `i2c-i801', I2C address 0x61
    Chip `SMBus 2.0 ARP-Capable Device' (confidence: 1)

Driver `w83627hf' (should be inserted):
  Detects correctly:
  * ISA bus address 0x0290 (Busdriver `i2c-isa')
    Chip `Winbond W83627THF 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-i801
modprobe i2c-isa
# I2C chip drivers
# no driver for Winbond W83792D yet
modprobe eeprom
# Warning: the required module smbus-arp is not currently installed on your system.
# For status of 2.6 kernel ports see http://secure.netroedge.com/~lm78/supported.html
# If driver is built-in to the kernel, or unavailable, comment out the following line.
modprobe smbus-arp
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): no

[lm-sensors] No temperature/fan values with 83627THF chip

[Rudolf Marek]

Hi all

> Probing for `Winbond W83792D'... Success!
>     (confidence 7, driver `to-be-written'), other addresses: 0x4b 0x4f
> 
> Looks like your guess paid off :)
> 
> So I guess my next qustion is...what's the timeline for porting this 
> driver to 2.6?

Chunhao please can you estimate?

Thanks

regards

Rudolf

[lm-sensors] No temperature/fan values with 83627THF chip

[Huang0]

Hi Rudolf, Jon, Jean

I think I have almost finished the 792 driver for linux-2.6, I remember that
I sent you a mail ask for your review to my codes before, but it seems that I
have not get your response yet :-(

I have tested it here on two motherboards with 792 chip, it works well.
Would you like help us to review my codes? After your review, you may send
it to the kernel group, I think.

Btw, I'd like to send the 792 driver for linux-2.6 again to you in another mail
because I did a little modification since last time sent you,
Should I send it to only three of you? Or send it to the whole lm-sensors
mailing list?



Thanks
Best Regards

Chunhao


> -----Original Message-----
> From: Rudolf Marek [mailto:r.marek@sh.cvut.cz]
> Sent: 2005爛5堎21゜ 18:20
> To: Jon Still; PI14 HUANG0
> Cc: lm-sensors@lm-sensors.org
> Subject: Re: [lm-sensors] No temperature/fan values with 83627THF chip
> 
> Hi all
> 
> > Probing for `Winbond W83792D'... Success!
> >     (confidence 7, driver `to-be-written'), other addresses: 0x4b 0x4f
> >
> > Looks like your guess paid off :)
> >
> > So I guess my next qustion is...what's the timeline for porting this
> > driver to 2.6?
> 
> Chunhao please can you estimate?
> 
> Thanks
> 
> regards
> 
> Rudolf

===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repeat the  English statement above.本信件內所含華邦電子的財產性機密性資訊, 僅授權原發信人指定之收信人取閱之用. 假使您並非被指定之收信人或因任何原因在未經授權的情形之下收到本信件, 請您告知原發信人並立即將信件從電腦與網路伺服器中予以消除. 對於您的合作, 我們先此致謝. 特此提醒, 任何未經授權擅自使用華邦電子的機密資訊的行為是被嚴格禁止的. 信件與華邦電子營業無關之內容,不得視為華邦電子之立場或意見.

[lm-sensors] No temperature/fan values with 83627THF chip

[Jon Still]

Hi,

> I have tested it here on two motherboards with 792 chip, it works well.
> Would you like help us to review my codes? After your review, you may send
> it to the kernel group, I think.

I'm quite happy to give it a test on my box, so long as the worst it will 
do is panic or freeze the system.  I'm presuming this will have to be 
compiled outside of the kernel tree so if you could provide the 
appropriate command line for that I'd be grateful.

Cheers!
Jon.

-- 
Jon Still                               E-mail: jon@tertial.org
tertial.org                             Web:    http://www.tertial.org/
GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B

[lm-sensors] No temperature/fan values with 83627THF chip

[Rudolf Marek]

Hi Chunhao

Please send it to whole group in separate thread.

With subject something like:
Subject: [PATCH2.6] Chip driver W83792 - rc1

Jean do you remember if something else is missing?

Thanks

regards

Rudolf

[lm-sensors] No temperature/fan values with 83627THF chip

[Huang0]

Hi Jon, Thomas

Quoting Jon:
> I'm quite happy to give it a test on my box, so long as the worst it will
> do is panic or freeze the system.  I'm presuming this will have to be
> compiled outside of the kernel tree so if you could provide the
> appropriate command line for that I'd be grateful.

The following information was provided by Jean:
1* Create a Makefile where the w83792d.c file is, with one line:
obj-m := w83792d.o

2* Type: make -C /usr/src/linux SUBDIRS=$PWD modules (replace
/usr/src/linux with the path to the Linux sources tree)

And you're done :) You only need to copy w83792d.ko to /lib/modules
/`uname -a`/kernel/drivers/i2c/chips before you modprobe it.
Alternatively you can do insmod ./w83792d.ko without installing it,
I think it works.


Please check it. If you still have questions, please contact him for help,
he really knows very much. :-)


Thanks
Best Regards
Chunhao



> -----Original Message-----
> From: PI14 HUANG0
> Sent: 2005爛5堎24゜ 9:35
> To: 'Jon Still'; 'Thomas J. Teixeira'
> Cc: 'lm-sensors@lm-sensors.org'
> Subject: RE: [lm-sensors] No temperature/fan values with 83627THF chip
> 
> Hi Jon, Thomas, Rudolf, Jean
> 
> This is Chunhao.
> 
> The attachment is the w83792d driver for linux-2.6, please test it for me
> if you have time.


===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repeat the  English statement above.本信件內所含華邦電子的財產性機密性資訊, 僅授權原發信人指定之收信人取閱之用. 假使您並非被指定之收信人或因任何原因在未經授權的情形之下收到本信件, 請您告知原發信人並立即將信件從電腦與網路伺服器中予以消除. 對於您的合作, 我們先此致謝. 特此提醒, 任何未經授權擅自使用華邦電子的機密資訊的行為是被嚴格禁止的. 信件與華邦電子營業無關之內容,不得視為華邦電子之立場或意見.

[lm-sensors] No temperature/fan values with 83627THF chip

[Huang0]

Hi Jon, Thomas, Rudolf, Jean

This is Chunhao.

The attachment is the w83792d driver for linux-2.6, please test it for me
if you have time.

There are some small bugs in it as following:
(1) We misunderstand the meaning of temperature low limit, this bug also
exists in the 792 driver for linux-2.4 and our 792 Windows driver.
(2) I have not implemented the 0.5 degree to temperature2 and temperature3,
while the driver for linux-2.4 implemented this.
(3) The 792 driver for linux-2.4 can adjust the fan divisor automatically,
while I have not implemented it in this 2.6 one.

These bugs are kept in my own bug-list, I will fix them when I'm a little free,
because I'm very busy in another my project, I can NOT fix them now.
If you find any other bugs, please don't hesitate to tell us. You may also
help us to fix them if you have time, but please tell us before your fix :-)


Quoting Thomas
> My company is evaluating a SuperMicro P8SCT motherboard which uses
> the Winbond W83792D chip for health monitoring. Our software runs under
> Linux using the Suse 9.1 distribution and a kernel based on Linux 2.6.6.
> From searching on the net I see you are in the process of writing a driver
> for this chip to work with the lm_sensors package. Would it be possible to
> help test this driver?

I'm sorry that I should have sent the 792 driver for linux-2.6 to you
earlier.


Thanks
Best Regards
Chunhao



> -----Original Message-----
> From: Jon Still [mailto:jon@tertial.org] On Behalf Of Jon Still
> Sent: 2005爛5堎23゜ 15:23
> To: PI14 HUANG0
> Cc: lm-sensors@lm-sensors.org
> Subject: RE: [lm-sensors] No temperature/fan values with 83627THF chip
> 
> Hi,
> 
> > I have tested it here on two motherboards with 792 chip, it works well.
> > Would you like help us to review my codes? After your review, you may send
> > it to the kernel group, I think.
> 
> I'm quite happy to give it a test on my box, so long as the worst it will
> do is panic or freeze the system.  I'm presuming this will have to be
> compiled outside of the kernel tree so if you could provide the
> appropriate command line for that I'd be grateful.
> 
> Cheers!
> Jon.



==============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.==============================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repeat the  English statement above.本信件內所含華邦電子的財產性機密性資訊, 僅授權原發信人指定之收信人取閱之用. 假使您並非被指定之收信人或因任何原因在未經授權的情形之下收到本信件, 請您告知原發信人並立即將信件從電腦與網路伺服器中予以消除. 對於您的合作, 我們先此致謝. 特此提醒, 任何未經授權擅自使用華邦電子的機密資訊的行為是被嚴格禁止的. 信件與華邦電子營業無關之內容,不得視為華邦電子之立場或意見.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: w83792d.c
Type: application/octet-stream
Size: 52005 bytes
Desc: w83792d.c
Url : http://lists.atrpms.net/pipermail/lm-sensors/attachments/20050524/a4485b9e/w83792d-0001.obj

[lm-sensors] No temperature/fan values with 83627THF chip

[Jon Still]

Hi Chunhao & Rudolf,

The w83792d 2.6 driver is working great on my box now.

w83792d-i2c-0-2f
Adapter: SMBus I801 adapter at 0500
VCoreA:    +1.33 V  (min =  +1.40 V, max =  +1.60 V)       ALARM
VCoreB:    +1.34 V  (min =  +1.40 V, max =  +1.60 V)       ALARM
VIN0:      +3.34 V  (min =  +3.20 V, max =  +3.39 V)       
VIN1:      +3.02 V  (min =  +3.09 V, max =  +3.30 V)       ALARM
VIN2:      +0.52 V  (min =  +1.39 V, max =  +1.49 V)       ALARM
VIN3:      +3.12 V  (min =  +2.59 V, max =  +2.64 V)       ALARM
5VCC:      +5.03 V  (min =  +4.73 V, max =  +5.23 V)       
5VSB:      +4.92 V  (min =  +4.73 V, max =  +5.23 V)       
VBAT:      +3.10 V  (min =  +2.85 V, max =  +3.14 V)       
Fan2:     4687 RPM  (min = 1500 RPM, div = 4)              
Fan3:     4560 RPM  (min = 1500 RPM, div = 4)              
CPU Temp:  +24.0 C  (high = +42.0 C, hyst = +37.0 C)   ALARM
M/B Temp:  +30.0 C  (high = +43.0 C, hyst = +38.0 C)   ALARM
chassis:  Chassis is normal.

The voltages seem to be a little wonky, but I've no idea what Supermicro 
are doing with them!  Also is there any convention with the w83792d as to 
which thermistor is connected to which VTIN pin, or is it purely up to the 
board's manufacturer?

Having said that, so long as I can get the information I'm not really 
worried - I just want to make sure the box is relatively OK as I can't get 
physical access so readily.

Thanks to all for your help with this one!  I'll keep the drivers loaded 
and let you know if I see anything odd over the next week or so.

Thanks again!

Jon.

-- 
Jon Still                               E-mail: jon@tertial.org
tertial.org                             Web:    http://www.tertial.org/
GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B

[lm-sensors] No temperature/fan values with 83627THF chip

[Huang0]

Hi Jon

It seems that the 792 driver for linux-2.6 can work on your motherboard,
We have three motherboards which contain 792 chip here, all of them have
been tested briefly by me, their measured value differ from each other greatly,
and I'm not very sure whether the measured value is really right or not.
I think the measured value is up to the board's manufacturer.

You may check your BIOS if there is a "Hardware Monitor" or "Hardware Health"
option there, if do, compare them with the measured value by 792 driver.
I think most of them should be very close, because I compared them here
on our two motherboards.


Best Regards
Chunhao


> -----Original Message-----
> From: Jon Still [mailto:jon@tertial.org] On Behalf Of Jon Still
> Sent: 2005爛5堎24゜ 20:07
> To: PI14 HUANG0
> Cc: tjt@intellivid.com; khali@linux-fr.org; lm-sensors@lm-sensors.org
> Subject: RE: [lm-sensors] No temperature/fan values with 83627THF chip
> 
> Hi Chunhao & Rudolf,
> 
> The w83792d 2.6 driver is working great on my box now.
> 
> w83792d-i2c-0-2f
> Adapter: SMBus I801 adapter at 0500
> VCoreA:    +1.33 V  (min =  +1.40 V, max =  +1.60 V)       ALARM
> VCoreB:    +1.34 V  (min =  +1.40 V, max =  +1.60 V)       ALARM
> VIN0:      +3.34 V  (min =  +3.20 V, max =  +3.39 V)
> VIN1:      +3.02 V  (min =  +3.09 V, max =  +3.30 V)       ALARM
> VIN2:      +0.52 V  (min =  +1.39 V, max =  +1.49 V)       ALARM
> VIN3:      +3.12 V  (min =  +2.59 V, max =  +2.64 V)       ALARM
> 5VCC:      +5.03 V  (min =  +4.73 V, max =  +5.23 V)
> 5VSB:      +4.92 V  (min =  +4.73 V, max =  +5.23 V)
> VBAT:      +3.10 V  (min =  +2.85 V, max =  +3.14 V)
> Fan2:     4687 RPM  (min = 1500 RPM, div = 4)
> Fan3:     4560 RPM  (min = 1500 RPM, div = 4)
> CPU Temp:  +24.0 C  (high = +42.0 C, hyst = +37.0 C)   ALARM
> M/B Temp:  +30.0 C  (high = +43.0 C, hyst = +38.0 C)   ALARM
> chassis:  Chassis is normal.
> 
> The voltages seem to be a little wonky, but I've no idea what Supermicro
> are doing with them!  Also is there any convention with the w83792d as to
> which thermistor is connected to which VTIN pin, or is it purely up to the
> board's manufacturer?
> 
> Having said that, so long as I can get the information I'm not really
> worried - I just want to make sure the box is relatively OK as I can't get
> physical access so readily.
> 
> Thanks to all for your help with this one!  I'll keep the drivers loaded
> and let you know if I see anything odd over the next week or so.
> 
> Thanks again!
> 
> Jon.
> 
> --
> Jon Still                               E-mail: jon@tertial.org
> tertial.org                             Web:    http://www.tertial.org/
> GPG Key: http://xanthein.net/key.asc    Key ID: 0x00493D2B

===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repeat the  English statement above.本信件內所含華邦電子的財產性機密性資訊, 僅授權原發信人指定之收信人取閱之用. 假使您並非被指定之收信人或因任何原因在未經授權的情形之下收到本信件, 請您告知原發信人並立即將信件從電腦與網路伺服器中予以消除. 對於您的合作, 我們先此致謝. 特此提醒, 任何未經授權擅自使用華邦電子的機密資訊的行為是被嚴格禁止的. 信件與華邦電子營業無關之內容,不得視為華邦電子之立場或意見.