On the SE7520JR2 running AMIBIOS8, the National Semiconductor/Winbond
87431 (mBMC) is located at I2C slave address 0x42.
AMIBIOS8 is SMBIOS compatible. To determine the IPMI BMC I2C slave
address, examine the SMBIOS table. The algorithm is:
1) Read a DWORD at every 16-byte boundary from 0xF0000 to 0xFFFF0
searching for the value 0x5F4D535F ("_SM_" in little-endian). The
address where you find this value is called the SMBIOS entry point.
2) You will find the pointer to the SMBIOS structure table in the DWORD
at offset 0x18 past the SMBIOS entry point. You can get the length of
the SMBIOS structure table in the WORD at offset 0x16 past the SMBIOS
entry point. A count of the number of SMBIOS structures is in the WORD
at offset 0x1C past the SMBIOS entry point.
3) The SMBIOS structures are contiguous in memory, starting at the
SMBIOS structure table pointer. Every SMBIOS structure begins with a
"type" BYTE at offset 0 and a "length" BYTE at offset 1. Look for table
type 0x26, which contains the IPMI device information. When you
encounter the incorrect table type, add the length to the address of the
beginning of the current table to find the start of the next table.
4) The BYTE at offset 0x6 within the SMBIOS type 0x26 table is the I2C
read address. It usually contains the value 0x84. As is typical for I2C
slave addresses, it is shifted left one bit to accommodate the
read/write flag at bit 0. The I2C drivers shift this bit out, which is
how we arrive at slave address 0x42.
Legend
------
DWORD=32 bits
WORD=16 bits
BYTE=8 bits
I've considered submitting a patch to ipmi_smb_intf.c to implement this
algorithm, or perhaps provide a configuration keyword to enable scanning
the SMBIOS tables to find the BMC I2C slave address. Unfortunately, I've
become preoccupied with other matters and haven't had time to work on
this.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Robert Tran
Sent: Monday, December 05, 2005 7:04 PM
To: Roy Chan
Cc: [email protected]
Subject: Re: [Openipmi-developer] OpenIPMI and SE7520JR2 Question
Thanks for the quick response, Roy! I've also tried the
i2c-2.9.2/lmsensors-2.9.2/i2c-ipmi/bmcsensors to no avail.
I'll try the ISM route. Just curious, what was the address the 87431
device located at?
Also if I went the ISM route, would I still be able to use ipmitool (or
may be Intel CLI utility) to get the sensors data?
-Robert.
On 12/4/05, Roy Chan <[EMAIL PROTECTED]> wrote:
Hello Robert,
You need the i2c patch in order for the ipmi_smb to work. But I
don't think there are available i2c patches for the 2.4 kernel.
I also encountered the same problem before. Having exhausted all
solutions, I ended up using the Intel Server Management software.
You might want to try the working kernel 2.6 drivers.
- Roy -
Robert Tran < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> > wrote:
Hello,
I'm having problems trying to use OpenIPMI on a
SE7520JR2 baseboard. The problem is very similar to what
John Fusco had (See email thread "Ipmi_si and Intel
SE7520JR235"). The difference is that I'm running
kernel 2.4.20-8(!!). I don't have an IMM either.
I loaded ipmi_msghandler.o, ipmi_devintf.o and
ipmi_sbm_intf.o (I understand that I don't want to use
ipmi_si_drv.o). lsmod showed i2c_core was also loaded.
But when I used ipmitool, it doesn't work. I've applied
the patches from sourceforge for Linux 2.4.
Following the email threads here, it seems that I need
the i2c patch also, but I couldn't find it in
the patches for
2.4. Also I understand that there is some problems in
getting the OpenIPMI patches
to work with kernel 2.4.x.
So my questions are:
1) Is it possible at all to use OpenIPMI in
2.4.20-8 on the SE7520JR2 board with the mBMC device?
Where could I get the correct i2c drivers or
patches?
2) If I get the IMM module, would I be able to use
the ipmi_si_drv.o?
Please help!
Best Regards,
Robert.
--------------------------------------------------------
Info:
dmidecode shows the following:
IPMI Device Information
Interface Type: <OUT OF SPEC>
Specification Version: 1.5
I2C Slave Address: 0x10
NV Storage Device: Not Present
Base Address: 0x0000000000000084 (Memory-mapped)
Register Spacing: Successive Byte Boundaries
The following dmesg info is before I found out I don't
want to use ipmi_si_drv.o.
ipmi message handler version v37
ipmi device interface version v37
IPMI System Interface driver version v37, KCS version
v37, SMIC version v37, BT version v37
ipmi_si: Unknown SMBIOS SI type.
ipmi_si: Trying "kcs" at I/O port 0xca2
ipmi_si: Trying "smic" at I/O port 0xca9
ipmi_si: Trying "bt" at I/O port 0xe4
ipmi_si: Unknown SMBIOS SI type.
ipmi_si: Unknown SMBIOS SI type.
ipmi_si: Unknown SMBIOS SI type.
ipmi_si: Unable to find any System Interface(s)
________________________________
Yahoo! Personals
Let fate take it's course directly to your email.
See who's waiting for you Yahoo! Personals
<http://us.rd.yahoo.com/evt=36106/*http://personals.yahoo.com+%0D%0A>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
