Discussion:
[Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?
Kurt Yoder
2008-02-20 21:21:28 UTC
Permalink
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
David A. Ranch
2008-02-20 21:47:34 UTC
Permalink
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
Post by Kurt Yoder
Hiya, list!
# ls /dev/ipmi*
/dev/ipmi0
# ipmitool -I open sdr
No such file or directory
Get Device ID command failed
Unable to open SDR for reading
# 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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Kurt Yoder
2008-02-21 15:08:11 UTC
Permalink
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.
Post by David A. Ranch
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
crw-rw-rw- 1 root root 253, 0 Dec 10 15:38 /dev/ipmi0
--David
Post by Kurt Yoder
Hiya, list!
I installed openipmi successfully (I think), and now have a /dev/
# ls /dev/ipmi*
/dev/ipmi0
# 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
# 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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
David Ranch
2008-02-21 15:29:41 UTC
Permalink
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 <***@yoderhome.com>
To: David Ranch
Cc: ipmitool-***@lists.sourceforge.net <ipmitool-***@lists.sourceforge.net>
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.
Post by David A. Ranch
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
crw-rw-rw- 1 root root 253, 0 Dec 10 15:38 /dev/ipmi0
--David
Post by Kurt Yoder
Hiya, list!
I installed openipmi successfully (I think), and now have a /dev/
# ls /dev/ipmi*
/dev/ipmi0
# 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
# 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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Corey Minyard
2008-02-21 15:45:58 UTC
Permalink
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
Post by David Ranch
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 -----
To: David Ranch
Sent: Thu Feb 21 07:08:11 2008
Subject: Re: [Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?
# ls -l /dev/ipmi*
crw-r--r-- 1 root root 254, 0 2008-02-19 11:59 /dev/ipmi0
# cat /proc/devices | grep ipmi
254 ipmidev
# 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
init_ipmi_si: Unable to register driver: -17
I'll have to check on the BIOS and BMC firmware.
Post by David A. Ranch
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
crw-rw-rw- 1 root root 253, 0 Dec 10 15:38 /dev/ipmi0
--David
Post by Kurt Yoder
Hiya, list!
I installed openipmi successfully (I think), and now have a /dev/
# ls /dev/ipmi*
/dev/ipmi0
# 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
# 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
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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Kurt Yoder
2008-02-21 17:57:38 UTC
Permalink
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.
Post by Corey Minyard
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
Post by David Ranch
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 -----
To: David Ranch
Sent: Thu Feb 21 07:08:11 2008
Subject: Re: [Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?
# ls -l /dev/ipmi*
crw-r--r-- 1 root root 254, 0 2008-02-19 11:59 /dev/ipmi0
# cat /proc/devices | grep ipmi
254 ipmidev
# 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
init_ipmi_si: Unable to register driver: -17
I'll have to check on the BIOS and BMC firmware.
Post by David A. Ranch
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
crw-rw-rw- 1 root root 253, 0 Dec 10 15:38 /dev/ipmi0
--David
Post by Kurt Yoder
Hiya, list!
I installed openipmi successfully (I think), and now have a /
# ls /dev/ipmi*
/dev/ipmi0
# 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
# 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
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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
David A. Ranch
2008-02-21 18:18:55 UTC
Permalink
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
This might be an issue with needing to specify specific memory
locations for your specific BMC.&nbsp; Try unloading ALL IPMI kernel modules
and then run this script but you'll need to research and specify the
right memory regions:<br>
<br>
ipmimod.sh<br>
--<br>
#!/bin/bash<br>
<br>
#IPMI kernel module installer for Redhat-style machines<br>
#***@juniper.net<br>
<br>
#07/26/06 - use absolute paths for modprobe<br>
#05/01/06 - orig version<br>
<br>
/sbin/modprobe ipmi_devintf<br>
<br>
maj=`cat /proc/devices | awk '/ipmidev/{print $1}'`<br>
echo $maj<br>
if [ -c /dev/ipmi0 ]<br>
then<br>
&nbsp;&nbsp; rm -f /dev/ipmi0<br>
&nbsp;&nbsp; /bin/mknod /dev/ipmi0 c $maj 0<br>
else<br>
&nbsp;&nbsp; /bin/mknod /dev/ipmi0 c $maj 0<br>
fi<br>
<br>
IPMI_DRIVERS="ipmi_si ipmi_si_drv ipmi_kcs_drv"<br>
for driver in $IPMI_DRIVERS; do<br>
&nbsp; find /lib/modules/`uname -r`/kernel/drivers/char/ipmi | grep $driver
&gt; /dev/null<br>
&nbsp; RETURN_VALUE=$?<br>
&nbsp; if [ $RETURN_VALUE -eq 0 ] ; then<br>
&nbsp;&nbsp;&nbsp; #Here are specific memory locations for Supermicro AOC-type IPMI
cards<br>
&nbsp;&nbsp;&nbsp; /sbin/modprobe $driver type=kcs ports=0xca8 regspacings=4<br>
&nbsp;&nbsp;&nbsp; break<br>
&nbsp; fi<br>
done<br>
--<br>
<br>
<br>
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:<br>
--<br>
IPMI_SI=yes<br>
IPMI_SI_MODULE_OPTIONS="type=kcs ports=0xca8 regspacings=4"<br>
--<br>
<br>
<br>
Ps. I have other IPMI issues and solutions here though this doc really
needs to be updated:<br>
<br>
&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext" href="http://www.ecst.csuchico.edu/~dranch/LINUX/index-linux.html#ipmi">http://www.ecst.csuchico.edu/~dranch/LINUX/index-linux.html#ipmi</a><br>
<br>
--David<br>
<br>
<br>
<blockquote
cite="mid:4DB92108-760B-4E8D-8801-***@yoderhome.com"
type="cite">
<pre wrap="">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:

</pre>
<blockquote type="cite">
<pre wrap="">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:
</pre>
<blockquote type="cite">
<pre wrap="">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 <a class="moz-txt-link-rfc2396E" href="mailto:***@yoderhome.com">&lt;***@yoderhome.com&gt;</a>
To: David Ranch
Cc: <a class="moz-txt-link-abbreviated" href="mailto:ipmitool-***@lists.sourceforge.net">ipmitool-***@lists.sourceforge.net</a> &lt;ipmitool- <a class="moz-txt-link-abbreviated" href="mailto:***@lists.sourceforge.net">***@lists.sourceforge.net</a>&gt;
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:


</pre>
<blockquote type="cite">
<pre wrap="">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


</pre>
<blockquote type="cite">
<pre wrap="">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

-------------------------------------------------------------------
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">-- ---
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
<a class="moz-txt-link-freetext" href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a>
_______________________________________________
Ipmitool-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ipmitool-***@lists.sourceforge.net">Ipmitool-***@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ipmitool-devel">https://lists.sourceforge.net/lists/listinfo/ipmitool-devel</a>


</pre>
</blockquote>
</blockquote>
<pre wrap="">---------------------------------------------------------------------
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">----
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
<a class="moz-txt-link-freetext" href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a>
_______________________________________________
Ipmitool-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ipmitool-***@lists.sourceforge.net">Ipmitool-***@lists.sourceforge.net</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ipmitool-devel">https://lists.sourceforge.net/lists/listinfo/ipmitool-devel</a>

</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>
Kurt Yoder
2008-02-21 20:06:46 UTC
Permalink
OK, thanks. How do I find the right memory regions? Is there an RTFM
for this?
Post by David A. Ranch
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
ipmimod.sh
--
#!/bin/bash
#IPMI kernel module installer for Redhat-style machines
#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/
--
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
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
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
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
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
Post by David A. Ranch
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
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
lists.sourceforge.net/lists/listinfo/ipmitool-devel
David A. Ranch
2008-02-21 21:25:23 UTC
Permalink
That's an excellent question and I really don't know if there is a way
to figure it out from Linux, etc. I would recommend to take this up
with Hp and report back to the list with your findings.

--David
Cress, Andrew R
2008-02-21 21:57:23 UTC
Permalink
Check dmidecode to see if it puts out a type 38 (IPMI) record.
If so, the Base Address should be listed there.

Andy

-----Original Message-----
From: ipmitool-devel-***@lists.sourceforge.net
[mailto:ipmitool-devel-***@lists.sourceforge.net] On Behalf Of David
A. Ranch
Sent: Thursday, February 21, 2008 4:25 PM
To: Kurt Yoder
Cc: ipmitool-***@lists.sourceforge.net
Subject: Re: [Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?


That's an excellent question and I really don't know if there is a way
to figure it out from Linux, etc. I would recommend to take this up
with Hp and report back to the list with your findings.

--David




------------------------------------------------------------------------
-
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/
David A. Ranch
2008-02-21 22:04:35 UTC
Permalink
Hmm.. that doesn't work for me. dmidecode shows:

/usr/sbin/dmidecode | grep 38
Handle 0x0030, DMI type 38, 12 bytes.

but I have to use:

IPMI_SI_MODULE_OPTIONS="type=kcs ports=0xca8 regspacings=4"

--David
Post by Cress, Andrew R
Check dmidecode to see if it puts out a type 38 (IPMI) record.
If so, the Base Address should be listed there.
Andy
-----Original Message-----
A. Ranch
Sent: Thursday, February 21, 2008 4:25 PM
To: Kurt Yoder
Subject: Re: [Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?
That's an excellent question and I really don't know if there is a way
to figure it out from Linux, etc. I would recommend to take this up
with Hp and report back to the list with your findings.
--David
------------------------------------------------------------------------
-
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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Garrick Staples
2008-02-21 22:20:59 UTC
Permalink
This post might be inappropriate. Click to display it.
David A. Ranch
2008-02-21 23:54:23 UTC
Permalink
This post might be inappropriate. Click to display it.
Corey Minyard
2008-02-21 21:58:35 UTC
Permalink
Post by Kurt Yoder
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
FATAL: Error inserting ipmi_si
No such device
ipmi_si: Unable to find any System Interface(s)
That means it's not finding anything.

Can you send the output of dmidecode, the section labelled: "IPMI
Device Information". If you don't have it, you likely don't have an
IPMI device in your system.
Post by Kurt Yoder
As usual, the rest of the ipmi modules are installed, and /dev/ipmi0
has been created.
You are using udev? It's very strange that /dev/ipmi0 was created. Can
you send:

The contents of /proc/ipmi/0

The syslog output when the module is loaded

That should help debug this.

-corey
Post by Kurt Yoder
Post by Corey Minyard
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
Post by David Ranch
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 -----
To: David Ranch
Sent: Thu Feb 21 07:08:11 2008
Subject: Re: [Ipmitool-devel] /dev/ipmi0 not seen by ipmitool?
# ls -l /dev/ipmi*
crw-r--r-- 1 root root 254, 0 2008-02-19 11:59 /dev/ipmi0
# cat /proc/devices | grep ipmi
254 ipmidev
# 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
init_ipmi_si: Unable to register driver: -17
I'll have to check on the BIOS and BMC firmware.
Post by David A. Ranch
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
crw-rw-rw- 1 root root 253, 0 Dec 10 15:38 /dev/ipmi0
--David
Post by Kurt Yoder
Hiya, list!
I installed openipmi successfully (I think), and now have a /dev/
# ls /dev/ipmi*
/dev/ipmi0
# 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
# 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
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
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
Kurt Yoder
2008-02-21 23:14:16 UTC
Permalink
Post by Corey Minyard
Post by Kurt Yoder
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
FATAL: Error inserting ipmi_si (/lib/modules/2.6.22-14-server/
kernel/drivers/char/ipmi/ipmi_si.ko): No such device
ipmi_si: Unable to find any System Interface(s)
That means it's not finding anything.
Can you send the output of dmidecode, the section labelled: "IPMI
Device Information". If you don't have it, you likely don't have
an IPMI device in your system.
I ran dmidecode and didn't see an IPMI section, so maybe it's a
simple matter of not having IPMI hardware installed. If this is the
case, I will kick myself...
Post by Corey Minyard
Post by Kurt Yoder
As usual, the rest of the ipmi modules are installed, and /dev/
ipmi0 has been created.
You are using udev? It's very strange that /dev/ipmi0 was
The contents of /proc/ipmi/0
The syslog output when the module is loaded
That should help debug this.
-corey
Yes, I'm using udev. However, I manually created the device using the
ipmi.init.basic script.


<snipped>
Corey Minyard
2008-02-22 03:13:40 UTC
Permalink
Post by Corey Minyard
Post by Kurt Yoder
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
FATAL: Error inserting ipmi_si
No such device
ipmi_si: Unable to find any System Interface(s)
That means it's not finding anything.
Can you send the output of dmidecode, the section labelled: "IPMI
Device Information". If you don't have it, you likely don't have an
IPMI device in your system.
I ran dmidecode and didn't see an IPMI section, so maybe it's a simple
matter of not having IPMI hardware installed. If this is the case, I
will kick myself...
Yeah, you probably don't have an IPMI device in that system. It's
possible you do and there is no DMI information, but then you will have
to get the information somehow.
Post by Corey Minyard
Post by Kurt Yoder
As usual, the rest of the ipmi modules are installed, and /dev/ipmi0
has been created.
You are using udev? It's very strange that /dev/ipmi0 was created.
The contents of /proc/ipmi/0
The syslog output when the module is loaded
That should help debug this.
-corey
Yes, I'm using udev. However, I manually created the device using the
ipmi.init.basic script.
Ah, that explains it.

-corey
David A. Ranch
2008-02-21 23:57:27 UTC
Permalink
Post by Corey Minyard
You are using udev? It's very strange that /dev/ipmi0 was created. Can
The contents of /proc/ipmi/0
That's interesting. I have various reliability and performance issues
with these Supermicro BMCs and I see the following:

# cat /proc/ipmi/0/si_stats
interrupts_enabled: 0
short_timeouts: 306793
long_timeouts: 631210735
timeout_restarts: 0
idles: -1665942245
interrupts: 0
attentions: 0
flag_fetches: 0
hosed_count: 0
complete_transactions: 6312687
events: 0
watchdog_pretimeouts: 0
incoming_messages: 0


Do you know if there is a way to enable interrupts?

--David
Corey Minyard
2008-02-22 03:14:52 UTC
Permalink
Post by David A. Ranch
Post by Corey Minyard
You are using udev? It's very strange that /dev/ipmi0 was created.
The contents of /proc/ipmi/0
That's interesting. I have various reliability and performance issues
# cat /proc/ipmi/0/si_stats
interrupts_enabled: 0
short_timeouts: 306793
long_timeouts: 631210735
timeout_restarts: 0
idles: -1665942245
interrupts: 0
attentions: 0
flag_fetches: 0
hosed_count: 0
complete_transactions: 6312687
events: 0
watchdog_pretimeouts: 0
incoming_messages: 0
Do you know if there is a way to enable interrupts?
Not on that system, I don't believe. It doesn't support them.

Newer kernels should perform much better due to some work by Dell. I
don't know about reliability problems, though.

-corey

Loading...