Hi,

 I am new to IPMI and platform management s/w. I need information
related to porting of ipmi driver as well make use of ipmitool to talk
to new BMC over I2C.

 In breif , i am using freescale processor with I2C controller which
is connected to customized BMC/ShMC  over I2C bus 1.
 Using/inserting the modules  ipmi_msghandler.ko,  ipmi_devintf.ko,
and  ipmi_smb.ko addr=1 slave_addrs=0x61 dbg=1  from monta  vista
kernel.

After making the  mknod   /dev/ipmi0  c  252 0  ( reading from
/proc/devinfo),  using   " ipmitool   -I open -d /dev/ipmi0 " command
to send the command to BMC.

  But i am getting the below error.
Could not open device at  /dev/ipmi0 or /dev/ipmi/0

Please suggest me to communicate to BMC over I2C from from host
processor.  I tried to load i2c-stub.ko driver also by enabling algo
modules and other freaacale I2C chip drivers also.

It is looking like ipmi_open is failing in  ipmi_devintf.c  when
ipmitool tries to open the /dev/ipmi0

Thanks in advance.
krish



On Mon, Aug 1, 2011 at 1:59 PM,
<[email protected]> wrote:
> Send Openipmi-developer mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        https://lists.sourceforge.net/lists/listinfo/openipmi-developer
> or, via email, send a message with subject or body 'help' to
>        [email protected]
>
> You can reach the person managing the list at
>        [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Openipmi-developer digest..."
>
>
> Today's Topics:
>
>   1. Re: OpenIPMI and RedHat 6 (Corey Minyard)
>   2. Re: OpenIPMI and RedHat 6 (Bob Sauvage)
>   3. Re: OpenIPMI and RedHat 6 (Bob Sauvage)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 29 Jul 2011 08:57:01 -0500
> From: Corey Minyard <[email protected]>
> Subject: Re: [Openipmi-developer] OpenIPMI and RedHat 6
> To: [email protected]
> Cc: [email protected], [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On 07/29/2011 03:50 AM, Bob Sauvage wrote:
>> Hello Jan and Corey,
>>
>> First of all, thanks for the provided information.
>>
>> The ipmi service is started :
>>
>> *service ipmi status*
>>
>> ipmi_msghandler module loaded.
>> ipmi_si module loaded.
>> ipmi_devintf module loaded.
>> /dev/ipmi0 does not exist.
>>
>> *Modules are loaded : *
>>
>> Module                  Size  Used by
>> ipmi_devintf            7983  0
>> ipmi_si                42399  0
>> ipmi_msghandler        35958  2 ipmi_devintf,ipmi_si
>>
>> *dmidecode :*
>>
>> System Information
>>         Manufacturer: Supermicro
>>         Product Name: X8SIL
>>
>> IPMI Device Information
>>         Interface Type: KCS (Keyboard Control Style)
>>         Specification Version: 2.0
>>         I2C Slave Address: 0x00
>>         NV Storage Device: Not Present
>>         Base Address: 0x0000000000000CA2 (Memory-mapped)
>>         Register Spacing: Successive Byte Boundaries
>>
>> *Kernel log : *
>>
>> jul 29 10:39:32  kernel: ipmi message handler version 39.2
>> Jul 29 10:39:32  kernel: IPMI System Interface driver.
>> Jul 29 10:39:32  kernel: ipmi_si: Adding SMBIOS-specified kcs state
>> machine
>> Jul 29 10:39:32  kernel: ipmi_si: Trying SMBIOS-specified kcs state
>> machine at mem address 0xca2, slave address 0x0, irq 0
>> Jul 29 10:39:32  kernel: Could not set up I/O space
> This is the issue.  It looks like a bug in your DMI information.  Notice
> that it say the address is 0xca2 and it is memory mapped.  That is
> almost certainly wrong, as you would never have a memory mapped device
> at that address.  It's almost certainly I/O mapped.
>
> You can attempt to work around this by specifying "type=kcs ports=0xca2"
> when modprob-ing ipmi_si:
>
>    rmmod ipmi_si
>    modprobe ipmi_si type=kcs ports=0xca2
>
> Alternately, you can hot-add the device to the running driver using:
>
>    echo "add,kcs,i/o,0xca2" >/sys/module/ipmi_si/parameters/hotmod
>
> And of course, you can complain to your motherboard vendor.
>
> -corey
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Mon, 01 Aug 2011 10:16:38 +0200
> From: Bob Sauvage <[email protected]>
> Subject: Re: [Openipmi-developer] OpenIPMI and RedHat 6
> To: Corey Minyard <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> Hi Corey,
>
> Thanks again for your help.
>
> When I try to hot-add the device, I have the following error in the
> kernel log :
>
> Aug  1 10:13:13  kernel: ipmi_si: Adding hotmod-specified kcs state machine
> Aug  1 10:13:13  kernel: ipmi_si: Trying hotmod-specified kcs state
> machine at i/o address 0xca2, slave address 0x20, irq 0
> Aug  1 10:13:13  kernel: ipmi_si: Interface detection failed
>
> When I try the other solution, it does not work.
>
> Any other ideas ?
>
>
> On 07/29/2011 03:57 PM, Corey Minyard wrote:
>> On 07/29/2011 03:50 AM, Bob Sauvage wrote:
>>> Hello Jan and Corey,
>>>
>>> First of all, thanks for the provided information.
>>>
>>> The ipmi service is started :
>>>
>>> *service ipmi status*
>>>
>>> ipmi_msghandler module loaded.
>>> ipmi_si module loaded.
>>> ipmi_devintf module loaded.
>>> /dev/ipmi0 does not exist.
>>>
>>> *Modules are loaded : *
>>>
>>> Module                  Size  Used by
>>> ipmi_devintf            7983  0
>>> ipmi_si                42399  0
>>> ipmi_msghandler        35958  2 ipmi_devintf,ipmi_si
>>>
>>> *dmidecode :*
>>>
>>> System Information
>>>         Manufacturer: Supermicro
>>>         Product Name: X8SIL
>>>
>>> IPMI Device Information
>>>         Interface Type: KCS (Keyboard Control Style)
>>>         Specification Version: 2.0
>>>         I2C Slave Address: 0x00
>>>         NV Storage Device: Not Present
>>>         Base Address: 0x0000000000000CA2 (Memory-mapped)
>>>         Register Spacing: Successive Byte Boundaries
>>>
>>> *Kernel log : *
>>>
>>> jul 29 10:39:32  kernel: ipmi message handler version 39.2
>>> Jul 29 10:39:32  kernel: IPMI System Interface driver.
>>> Jul 29 10:39:32  kernel: ipmi_si: Adding SMBIOS-specified kcs state
>>> machine
>>> Jul 29 10:39:32  kernel: ipmi_si: Trying SMBIOS-specified kcs state
>>> machine at mem address 0xca2, slave address 0x0, irq 0
>>> Jul 29 10:39:32  kernel: Could not set up I/O space
>> This is the issue.  It looks like a bug in your DMI information.
>> Notice that it say the address is 0xca2 and it is memory mapped.  That
>> is almost certainly wrong, as you would never have a memory mapped
>> device at that address.  It's almost certainly I/O mapped.
>>
>> You can attempt to work around this by specifying "type=kcs
>> ports=0xca2" when modprob-ing ipmi_si:
>>
>>     rmmod ipmi_si
>>     modprobe ipmi_si type=kcs ports=0xca2
>>
>> Alternately, you can hot-add the device to the running driver using:
>>
>>     echo "add,kcs,i/o,0xca2" >/sys/module/ipmi_si/parameters/hotmod
>>
>> And of course, you can complain to your motherboard vendor.
>>
>> -corey
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Mon, 01 Aug 2011 10:28:56 +0200
> From: Bob Sauvage <[email protected]>
> Subject: Re: [Openipmi-developer] OpenIPMI and RedHat 6
> To: Corey Minyard <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
>
> I found this information in OpenIPMI website :
>
> The SI driver allows up to 4 KCS or SMIC interfaces to be configured
> in the system.  By default, scan the ACPI tables for interfaces, and
> if it doesn't find any the driver will attempt to register one KCS
> interface at the spec-specified I/O port 0xca2 without interrupts.
>
>
> What does it mean ? Why did it not find any interface ?
>
> On 08/01/2011 10:16 AM, Bob Sauvage wrote:
>>
>> Hi Corey,
>>
>> Thanks again for your help.
>>
>> When I try to hot-add the device, I have the following error in the
>> kernel log :
>>
>> Aug  1 10:13:13  kernel: ipmi_si: Adding hotmod-specified kcs state
>> machine
>> Aug  1 10:13:13  kernel: ipmi_si: Trying hotmod-specified kcs state
>> machine at i/o address 0xca2, slave address 0x20, irq 0
>> Aug  1 10:13:13  kernel: ipmi_si: Interface detection failed
>>
>> When I try the other solution, it does not work.
>>
>> Any other ideas ?
>>
>>
>> On 07/29/2011 03:57 PM, Corey Minyard wrote:
>>> On 07/29/2011 03:50 AM, Bob Sauvage wrote:
>>>> Hello Jan and Corey,
>>>>
>>>> First of all, thanks for the provided information.
>>>>
>>>> The ipmi service is started :
>>>>
>>>> *service ipmi status*
>>>>
>>>> ipmi_msghandler module loaded.
>>>> ipmi_si module loaded.
>>>> ipmi_devintf module loaded.
>>>> /dev/ipmi0 does not exist.
>>>>
>>>> *Modules are loaded : *
>>>>
>>>> Module                  Size  Used by
>>>> ipmi_devintf            7983  0
>>>> ipmi_si                42399  0
>>>> ipmi_msghandler        35958  2 ipmi_devintf,ipmi_si
>>>>
>>>> *dmidecode :*
>>>>
>>>> System Information
>>>>         Manufacturer: Supermicro
>>>>         Product Name: X8SIL
>>>>
>>>> IPMI Device Information
>>>>         Interface Type: KCS (Keyboard Control Style)
>>>>         Specification Version: 2.0
>>>>         I2C Slave Address: 0x00
>>>>         NV Storage Device: Not Present
>>>>         Base Address: 0x0000000000000CA2 (Memory-mapped)
>>>>         Register Spacing: Successive Byte Boundaries
>>>>
>>>> *Kernel log : *
>>>>
>>>> jul 29 10:39:32  kernel: ipmi message handler version 39.2
>>>> Jul 29 10:39:32  kernel: IPMI System Interface driver.
>>>> Jul 29 10:39:32  kernel: ipmi_si: Adding SMBIOS-specified kcs state
>>>> machine
>>>> Jul 29 10:39:32  kernel: ipmi_si: Trying SMBIOS-specified kcs state
>>>> machine at mem address 0xca2, slave address 0x0, irq 0
>>>> Jul 29 10:39:32  kernel: Could not set up I/O space
>>> This is the issue.  It looks like a bug in your DMI information.
>>> Notice that it say the address is 0xca2 and it is memory mapped.
>>> That is almost certainly wrong, as you would never have a memory
>>> mapped device at that address.  It's almost certainly I/O mapped.
>>>
>>> You can attempt to work around this by specifying "type=kcs
>>> ports=0xca2" when modprob-ing ipmi_si:
>>>
>>>     rmmod ipmi_si
>>>     modprobe ipmi_si type=kcs ports=0xca2
>>>
>>> Alternately, you can hot-add the device to the running driver using:
>>>
>>>     echo "add,kcs,i/o,0xca2" >/sys/module/ipmi_si/parameters/hotmod
>>>
>>> And of course, you can complain to your motherboard vendor.
>>>
>>> -corey
>>
>>
>> ------------------------------------------------------------------------------
>> Got Input?   Slashdot Needs You.
>> Take our quick survey online.  Come on, we don't ask for help often.
>> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
>> http://p.sf.net/sfu/slashdot-survey
>>
>>
>> _______________________________________________
>> Openipmi-developer mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Got Input?   Slashdot Needs You.
> Take our quick survey online.  Come on, we don't ask for help often.
> Plus, you'll get a chance to win $100 to spend on ThinkGeek.
> http://p.sf.net/sfu/slashdot-survey
>
>
> ------------------------------
>
> _______________________________________________
> Openipmi-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
>
>
> End of Openipmi-developer Digest, Vol 58, Issue 1
> *************************************************
>

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts. 
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer

Reply via email to