Peter Kjellstrom wrote:
On Wednesday 10 March 2010, m.roth@5-cent.us wrote: ...
$ insmod /lib/modules/2.6.18-164.11.1.el5/kernel/drivers/char/ipmi/ipmi_si.ko ports=0xca2 slave_addrs=0x10 insmod: error inserting '/lib/modules/2.6.18-164.11.1.el5/kernel/drivers/char/ipmi/ipmi_si.ko': -1 No such device
and in the log Mar 10 11:24:36 south kernel: IPMI System Interface driver. Mar 10 11:24:36 south kernel: ipmi_si: Trying hardcoded-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0 Mar 10 11:26:28 south kernel: ipmi_si: There appears to be no BMC at this location Mar 10 11:26:28 south kernel: ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca2, slave address 0x20, irq 0 Mar 10 11:28:20 south kernel: ipmi_si: There appears to be no BMC at this location Mar 10 11:30:12 south kernel: ipmi_si: Unable to find any System Interface(s)
Seems to me that the IPMI driver can't find the IPMI hardware. What kind of server are you trying this on? Is it known to work with the IPMI-driver in vanilla CentOS-5.4?
<snip> You seem to have missed the beginning of my original post, where I said that it had been running fine for 10 days, then *stopped* working. The server's still up, though I haven't been into the data center to see if the idiot red led "fault light" is blinking on (and that has no blink code, just "there's a problem" is what the docs say).
mark
mark