This might be an issue with needing to specify specific memory
locations for your specific BMC. Try unloading ALL IPMI kernel modules
and then run this script but you'll need to research and specify the
right memory regions:
ipmimod.sh
--
#!/bin/bash
#IPMI kernel module installer for Redhat-style machines
[EMAIL PROTECTED]
#07/26/06 - use absolute paths for modprobe
#05/01/06 - orig version
/sbin/modprobe ipmi_devintf
maj=`cat /proc/devices | awk '/ipmidev/{print $1}'`
echo $maj
if [ -c /dev/ipmi0 ]
then
rm -f /dev/ipmi0
/bin/mknod /dev/ipmi0 c $maj 0
else
/bin/mknod /dev/ipmi0 c $maj 0
fi
IPMI_DRIVERS="ipmi_si ipmi_si_drv ipmi_kcs_drv"
for driver in $IPMI_DRIVERS; do
find /lib/modules/`uname -r`/kernel/drivers/char/ipmi | grep $driver
> /dev/null
RETURN_VALUE=$?
if [ $RETURN_VALUE -eq 0 ] ; then
#Here are specific memory locations for Supermicro AOC-type IPMI
cards
/sbin/modprobe $driver type=kcs ports=0xca8 regspacings=4
break
fi
done
--
For a cleaner solution on Centos5, I modified the /etc/rc.d/init.d/ipmi
script to read additional startup options and in /etc/sysconfig/ipmi, I
added the line:
--
IPMI_SI=yes
IPMI_SI_MODULE_OPTIONS="type=kcs ports=0xca8 regspacings=4"
--
Ps. I have other IPMI issues and solutions here though this doc really
needs to be updated:
http://www.ecst.csuchico.edu/~dranch/LINUX/index-linux.html#ipmi
--David
I'm using varying versions of Ubuntu stock kernels:
2.6.17-10
2.6.22-14
2.6.20-15
I just tried installing the modules and device on a different machine
with 2.6.20-15, and got a different error than the -17. On the
command line:
FATAL: Error inserting ipmi_si (/lib/modules/2.6.22-14-server/kernel/
drivers/char/ipmi/ipmi_si.ko): No such device
In kern.log:
ipmi_si: Unable to find any System Interface(s)
As usual, the rest of the ipmi modules are installed, and /dev/ipmi0
has been created.
On Feb 21, 2008, at 10:45 AM, Corey Minyard wrote:
What Linux version are you running?
That error means that the driver was unable to register with the I/
O subsystem because the name was already registered. Which is very
strange, because this is the only thing that is using that name.
So you are trying to load a module and the function is already
compiled into the kernel (not sure if that is even possible) or
something very weird is going on.
-corey
David Ranch wrote:
You DO need the 'si' driver (as least I do).
The SI driver should give a better error report than '17'. Look
at the src code and see if there are any better descriptions there.
--david
----- Original Message -----
From: Kurt Yoder <[EMAIL PROTECTED]>
To: David Ranch
Cc: ipmitool-devel@lists.sourceforge.net <ipmitool-
[EMAIL PROTECTED]>
Sent: Thu Feb 21 07:08:11 2008
Subject: Re: [Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?
The device looks correct:
# ls -l /dev/ipmi*
crw-r--r-- 1 root root 254, 0 2008-02-19 11:59 /dev/ipmi0
the major node looks correct as well:
# cat /proc/devices | grep ipmi
254 ipmidev
the kernel modules appear to be loaded:
# lsmod | grep ipmi
ipmi_watchdog 20156 0
ipmi_devintf 10248 0
ipmi_msghandler 37952 2 ipmi_watchdog,ipmi_devintf
I don't need to have the ipmi_si module loaded, correct? If I try
to load it, I get an error in the kern.log:
init_ipmi_si: Unable to register driver: -17
I'll have to check on the BIOS and BMC firmware.
On Feb 20, 2008, at 4:47 PM, David A. Ranch wrote:
Do you have the right BMC firmware loaded on the DL360 as well
as the most up to date BIOS and BMC firmware.
Also, what's the output of "ls -la /dev/ipmi*"? It should be
something like:
crw-rw-rw- 1 root root 253, 0 Dec 10 15:38 /dev/ipmi0
--David
Hiya, list!
I installed openipmi successfully (I think), and now have a /
dev/ ipmi0:
# ls /dev/ipmi*
/dev/ipmi0
However ipmitool doesn't like my device if I use -I open:
# ipmitool -I open sdr
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/
ipmidev/ 0: No such file or directory
Get Device ID command failed
Unable to open SDR for reading
If I use -I imb, I get weird errors:
# ipmitool -I imb sdr
Error sending IMB request, status=1 ccode=0
Error sending IMB request, status=1 ccode=0
Error sending IMB request, status=1 ccode=0
Error sending IMB request, status=1 ccode=0
Error sending IMB request, status=1 ccode=0
Error sending IMB request, status=1 ccode=0
WARNING: Unknown SDR repository version 0x00
Error sending IMB request, status=1 ccode=bf
Error sending IMB request, status=1 ccode=bf
Error sending IMB request, status=1 ccode=bf
Unable to obtain SDR reservation
Unable to open SDR for reading
This is a local query, so AFAIK -I lan/-I lanplus would not be
approriate for me, correct?
Some notes: this works fine on all my ProLiant DL145 machines.
However, I get the above-mentioned problem on all of my
ProLiant DL360 machines. So it seems to be something hardware-
dependent.
Suggestions? Comments? RTFM locations?
Thanks,
-Kurt
-------------------------------------------------------------------
-- ---
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
---------------------------------------------------------------------
----
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
|
