[lm-sensors] Reading LM96000 on an Intel SE7221BK1 server board

[lm-sensors] Reading LM96000 on an Intel SE7221BK1 server board

[Richard Hirst]

(I'm new to lm-sensors stuff, so I might just be doing something stupid)

I'm trying to read the LM96000 device on an Intel SE7221BK1-E Server
Board.  sensors-detect doesn't see it.  From the datasheet it seems I
should find it at i2c address 0x2c, 0x2d, or 0x2e.  The board has an ICH6
SMbus interface.  I'm assuming the LM96000 should appear on the i2c bus
that provides, and that i2cdetect should at least see that there is
something at that address.  It doesn't though:

Modules loaded:  i2c_dev i2c_sensor i2c_i801 i2c_core

[root@localhost lm_sensors-2.9.1]# ./prog/detect/i2cdetect -l
i2c-0   unknown         SMBus I801 adapter at 0400       Algorithm unavailable

[root@localhost lm_sensors-2.9.1]# ./prog/detect/i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          XX XX XX XX XX 08 XX XX XX XX XX XX XX 
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX 
40: XX XX 42 XX 44 XX XX XX XX XX XX XX XX XX XX XX 
50: 50 XX 52 XX XX XX XX XX XX XX XX XX XX XX XX XX 
60: 60 XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX 
70: XX XX XX XX XX XX XX XX                         
[root@localhost lm_sensors-2.9.1]# 


Should I expect to see a 2c, 2d, or 2e in that output?  As I don't, what
does that mean?  Might it mean the chip is connected to some other i2c
bus I havn't found yet, or I need to do something else to enable it, or
what?  Might I have done something that made the chip invisible?

I assume I'm correct in thinking that as it doesn't show up in i2cdetect
output, there is no chance of the lm85 driver detecting it.

I also don't know what the i2c devices at 08, 42, 44, 60 and 69 are.
50 and 52 get picked up by the eeprom driver.

I'm running an FC3 2.6.10-1.766_FCsmp kernel atm, but I'm guessing
that wouldn't have an impact on i2cdetect output.

Any suggestions on how to access the LM96000 welcome.  The board
has a PC87427 too, and the motherboard doc suggests that has an "i2c
interface to LM96000 sensors", but I'm not sure I believe that;
the PC87427 has a SensorPath interface for talking to LMxx sensors, but
I don't think the LM96000 talks SensorPath.  The PC87427 has an SMbus
slave interface too, and I didn't see anything that looked like that in
the i2cdetect or i2cdump output either.

Thanks,
  Richard

[lm-sensors] Reading LM96000 on an Intel SE7221BK1 server board

[Jean Delvare]

Hi Richard,

> Should I expect to see a 2c, 2d, or 2e in that output?

Yup, if the LM96000 was connected to that bus.

> As I don't, what does that mean?

That the LM96000 isn't there.

> Might it mean the chip is connected to some other i2c bus I
> havn't found yet,

Either that, or the ICH6 SMBus is multiplexed. This is common on Asus
boards, but I don't think we ever saw an Intel board do that.

> or I need to do something else to enable it, or what?

If you do, it has to be board specific so only Intel can tell you.

> Might I have done something that made the chip invisible?

I don't think so.

> I assume I'm correct in thinking that as it doesn't show up in
> i2cdetect output, there is no chance of the lm85 driver detecting it.

Absolutely.

> I also don't know what the i2c devices at 08, 42, 44, 60 and 69 are.
> 50 and 52 get picked up by the eeprom driver.

08 and 44 are special addresses for SMBus 2.0 stuff, 69 is most probably
a clock chip you so not want to play with. Remains 42 and 60, I have no
idea for these (except that these are not typical addresses for hardware
monitoring chips).

> I'm running an FC3 2.6.10-1.766_FCsmp kernel atm, but I'm guessing
> that wouldn't have an impact on i2cdetect output.

No impact, true.

> Any suggestions on how to access the LM96000 welcome.  The board
> has a PC87427 too, and the motherboard doc suggests that has an "i2c
> interface to LM96000 sensors", but I'm not sure I believe that;
> the PC87427 has a SensorPath interface for talking to LMxx sensors,
> but I don't think the LM96000 talks SensorPath.

Correct again.

> The PC87427 has an SMbus slave interface too, and I didn't see
> anything that looked like that in the i2cdetect or i2cdump output
> either.

True again, it would show at 30 or 6c if I trust the preliminary
datasheet I have, and these addresses did not work in i2cdetect.

So your analysis is correct, I wouldn't have come up with a different
conclusion. Your best chance now is probably to ask Intel themselves for
help and details on the wiring.

Good luck,
-- 
Jean Delvare

[lm-sensors] Reading LM96000 on an Intel SE7221BK1 server board

[Richard Hirst]

Hi Jean,
  Thanks for the response.  I've made some progress...

The board has an E7221 chipset that includes a PC87431M mBMC chip.
By applying the various patches to support ipmi-smb and bmcsensors
I can now read voltages and temperatures from the mBMC via both
lm_sensors and ipmitool.

I still can't read fan speeds, as the mBMC doesn't report any
fan speed sensors.  The PC87431M datasheet claims it has a slave
i2c interface to talk to the host, and two master i2c interfaces
to talk to LMxx chips.  So maybe the LM96000 is hung off that.
The PC87431M also claims to have integral fan monitoring and control,
so I've really no idea whether the LM96000 does anything useful at
all.

Anyway, this is what I now get:

[root@localhost ~]# sensors
bmc-i2c-1-00
Adapter: IPMI adapter
1.8V:      +1.81 V  (min =  +1.61 V, max =  +1.96 V)   
5.0V:      +5.05 V  (min =  +4.55 V, max =  +5.58 V)
12V:      +12.45 V  (min = +10.78 V, max = +13.20 V)
BoardTemp: +32.0?C  (high =   +78?C, hyst =    +2?C)
CoreTemp:  +43.0?C  (high =   +88?C, hyst =    +2?C)

eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 0400
Unknown EEPROM type (8)

eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 0400
Unknown EEPROM type (8)

IPMI-i2c-0-42
Adapter: SMBus I801 adapter at 0400

[root@localhost ~]# ipmitool sdr
Baseboard 1.8V   | 1.81 Volts        | ok
Baseboard 5.0V   | 5.05 Volts        | ok
Baseboard 12V    | 12.45 Volts       | ok
Serverboard temp | 32 degrees C      | ok
Proc1 Core temp  | 42 degrees C      | ok
Proc IERR        | 0x00              | ok
P1 Thermal Trip  | 0x00              | ok
Interrupt Button | 0x00              | ok
ID Button        | 0x00              | ok
[root@localhost ~]# 


Device 42 on i2c bus 0 is the mBMC itself:

Jun 26 00:36:55 localhost kernel: IPMI SMB Interface driver version v33
Jun 26 00:36:55 localhost kernel: ipmi_smb: DMI specifies SSIF @ 0x42
Jun 26 00:36:55 localhost kernel: ipmi_smb: DMI specifies slave address at 0x84


which I think is good enough for now.  Would be nice to read fan
speeds, though.

Thanks,
  Richard


On Sun, Jun 26, 2005 at 11:22:42AM +0200, Jean Delvare wrote:
> Hi Richard,
> 
> > Should I expect to see a 2c, 2d, or 2e in that output?
> 
> Yup, if the LM96000 was connected to that bus.
> 
> > As I don't, what does that mean?
> 
> That the LM96000 isn't there.
> 
> > Might it mean the chip is connected to some other i2c bus I
> > havn't found yet,
> 
> Either that, or the ICH6 SMBus is multiplexed. This is common on Asus
> boards, but I don't think we ever saw an Intel board do that.
> 
> > or I need to do something else to enable it, or what?
> 
> If you do, it has to be board specific so only Intel can tell you.
> 
> > Might I have done something that made the chip invisible?
> 
> I don't think so.
> 
> > I assume I'm correct in thinking that as it doesn't show up in
> > i2cdetect output, there is no chance of the lm85 driver detecting it.
> 
> Absolutely.
> 
> > I also don't know what the i2c devices at 08, 42, 44, 60 and 69 are.
> > 50 and 52 get picked up by the eeprom driver.
> 
> 08 and 44 are special addresses for SMBus 2.0 stuff, 69 is most probably
> a clock chip you so not want to play with. Remains 42 and 60, I have no
> idea for these (except that these are not typical addresses for hardware
> monitoring chips).
> 
> > I'm running an FC3 2.6.10-1.766_FCsmp kernel atm, but I'm guessing
> > that wouldn't have an impact on i2cdetect output.
> 
> No impact, true.
> 
> > Any suggestions on how to access the LM96000 welcome.  The board
> > has a PC87427 too, and the motherboard doc suggests that has an "i2c
> > interface to LM96000 sensors", but I'm not sure I believe that;
> > the PC87427 has a SensorPath interface for talking to LMxx sensors,
> > but I don't think the LM96000 talks SensorPath.
> 
> Correct again.
> 
> > The PC87427 has an SMbus slave interface too, and I didn't see
> > anything that looked like that in the i2cdetect or i2cdump output
> > either.
> 
> True again, it would show at 30 or 6c if I trust the preliminary
> datasheet I have, and these addresses did not work in i2cdetect.
> 
> So your analysis is correct, I wouldn't have come up with a different
> conclusion. Your best chance now is probably to ask Intel themselves for
> help and details on the wiring.
> 
> Good luck,
> -- 
> Jean Delvare

[lm-sensors] Reading LM96000 on an Intel SE7221BK1 server board

[Arturas]

Hello Richard,

I have found Your messages in the list have simmilar hardware and same
problems:

http://lists.lm-sensors.org/pipermail/lm-sensors/2005-June/012847.html

I want to read IPMI sensors data and no success :(

Could you describe witch patches have applied to kernel, to get sensor
data? As I understod Intel provides ISM with closed drivers (IPMI also)
only for RedHat and Suse. I have Debian...
Maybe You have found intresting links about that.
My MB is Intel E7221BK, not sure about PC87431M (maybe PC87427), but
LM96000 is mentioned.

Thank You and sorry for my english.

Arturas Gudas

[lm-sensors] Reading LM96000 on an Intel SE7221BK1 server board

[Richard Hirst]

On Tue, Nov 22, 2005 at 07:13:14PM +0200, Arturas wrote:
> Hello Richard,
> 
> I have found Your messages in the list have simmilar hardware and same
> problems:
> 
> http://lists.lm-sensors.org/pipermail/lm-sensors/2005-June/012847.html
> 
> I want to read IPMI sensors data and no success :(
> 
> Could you describe witch patches have applied to kernel, to get sensor
> data? As I understod Intel provides ISM with closed drivers (IPMI also)
> only for RedHat and Suse. I have Debian...
> Maybe You have found intresting links about that.
> My MB is Intel E7221BK, not sure about PC87431M (maybe PC87427), but
> LM96000 is mentioned.

We are using Fedora Core 3, starting with kernel-2.6.10-1.766.FC3.src.rpm
and applying these additional patches:

linux-ipmi-2.6.10-base.diff
linux-i2c-2.6.10-nonblock.diff
linux-i2c-2.6.10-i801_nonblock.diff
linux-ipmi-2.6.10-smb.diff
patch-linux-2.6.11.5-bmcsensors.diff

We are using

lm_sensors-2.8.7-2.i386.rpm
ipmitool-1.8.2-1.i386.rpm

We have a patch in ipmitool which is just a fix to the rc script it
includes to load the ipmi_smb module.  You are probably more interested
in the modules we load, and the order we load them in.  I included the
full list below, and marked what I think are the relevant ones (>>):

   [root@localhost ~]# lsmod
   Module                  Size  Used by
   nfsd                  185697  9
   exportfs                9921  1 nfsd
   lockd                  59625  2 nfsd
>> bmcsensors             53861  0 
>> i2c_ipmi                8397  0 
>> i2c_dev                13249  0 
>> ipmi_smb               18601  1 
>> ipmi_devintf           11077  0 
>> ipmi_msghandler        41509  3 i2c_ipmi,ipmi_smb,ipmi_devintf
   sunrpc                135077  19 nfsd,lockd
   md5                     8001  1
   ipv6                  236897  20
   ip_conntrack_ftp       76145  0
   ip_conntrack_tftp       7921  0
   iptable_nat            27493  1
   ipt_state               5825  3
   ip_conntrack           45317  4 ip_conntrack_ftp,ip_conntrack_tftp,iptable_nat,ipt_state
   iptable_filter          7489  1
   ip_tables              20929  3 iptable_nat,ipt_state,iptable_filter
   video                  19653  0
   button                 10577  0
   battery                13253  0
   ac                      8773  0
   uhci_hcd               33497  0
   ehci_hcd               33737  0
   hw_random               9429  0
>> i2c_i801               13053  0 
>> i2c_core               29889  5 bmcsensors,i2c_ipmi,i2c_dev,ipmi_smb,i2c_i801
   e1000                  84373  0
   floppy                 56913  0
   raid1                  19393  2
   dm_snapshot            20709  0
   dm_zero                 6465  0
   dm_mirror              24861  2
   ext3                  117961  28
   jbd                    57177  1 ext3
   dm_mod                 57925  32 dm_snapshot,dm_zero,dm_mirror
   ata_piix               12485  4
   libata                 44101  1 ata_piix
   3w_9xxx                35013  1
   sd_mod                 20545  8
   scsi_mod              115649  3 libata,3w_9xxx,sd_mod
   [root@localhost ~]#


Having done this, I can read the sensors via ipmitool, or via lm_sensors:



[root@localhost ~]# sensors
bmc-i2c-1-00
Adapter: IPMI adapter
1.8V:      +1.81 V  (min =  +1.61 V, max =  +1.96 V)
5.0V:      +5.05 V  (min =  +4.55 V, max =  +5.58 V)
12V:      +12.45 V  (min = +10.78 V, max = +13.20 V)
BoardTemp: +29.0?C  (high =   +78?C, hyst =    +2?C)
CoreTemp:  +39.0?C  (high =   +88?C, hyst =    +2?C)

IPMI-i2c-0-42
Adapter: SMBus I801 adapter at 0400

[root@localhost ~]#


ot@localhost ~]# ipmitool sensor
Baseboard 1.8V   | 1.808      | Volts      | ok    | na        | 1.613     | 1.665     | 1.912     | 1.964     | na
Baseboard 5.0V   | 5.055      | Volts      | ok    | na        | 4.555     | 4.705     | 5.430     | 5.580     | na
Baseboard 12V    | 12.454     | Volts      | ok    | na        | 10.780    | 11.152    | 12.826    | 13.198    | na
Serverboard temp | 29.000     | degrees C  | ok    | na        | 0.000     | 5.000     | 65.000    | 78.000    | na
Proc1 Core temp  | 39.000     | degrees C  | ok    | na        | 5.000     | 10.000    | 81.000    | 88.000    | na
Proc IERR        | 0x0        | discrete   | 0x0000| na        | na        | na        | na        | na        | na
P1 Thermal Trip  | 0x0        | discrete   | 0x0000| na        | na        | na        | na        | na        | na
Interrupt Button | 0x0        | discrete   | 0x0000| na        | na        | na        | na        | na        | na
ID Button        | 0x0        | discrete   | 0x0000| na        | na        | na        | na        | na        | na
[root@localhost ~]#



The bmc sensors patch was from <http://bmcsensors-26.sourceforge.net>,
and the others were from <http://openipmi.sourceforge.net/>

It took me quite a while to get this working too; I started by trying
to talk to the sensor chips directly, but eventually I worked out that
they are probably only visible through the mBMC chip.  The mBMC chip
sits on the visible i2c bus, and then has the actual sensor chip on
a secondary i2c bus behind that, I believe.

I did manage to read one of the fan speeds via a driver I wrote, but
couldn't get at the sensor for the cpu fan speed, so didn't persue
that.

I don't think you'll have any joy with kernels newer than 2.6.12
because the bmcsensors code wont work.  It is being rewritten, I
believe, but I don't know the status.

Richard