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]> wrote:
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]> 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
