Kurt Yoder wrote:
>
> On Feb 21, 2008, at 4:58 PM, Corey Minyard wrote:
>
>> Kurt Yoder wrote:
>>> 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)
>> 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.

>
>
>
>
>>>
>>> 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
>>
>
>
> Yes, I'm using udev. However, I manually created the device using the 
> ipmi.init.basic script.
Ah, that explains it.

-corey

-------------------------------------------------------------------------
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

Reply via email to