[ewg] Installation problems of OFED-1.5.2

Tanin fanqielee at gmail.com
Wed Feb 23 11:24:41 PST 2011


I think I also need iw_nes driver for my RNIC card, right?

[litan at tera05 init.d]$ /sbin/lspci
Ethernet controller: NetEffect NE020 10Gb Accelerated Ethernet Adapter
(iWARP RNIC) (rev 05)


On Wed, Feb 23, 2011 at 2:02 PM, Tanin <fanqielee at gmail.com> wrote:

> Oh, yes. Thanks so much! After uninstall all libibverbs packages, the
> OFED-1.5.3-rc5 successfully passed all building process:
>
>
> Install iscsi-initiator-utils RPM:
> Running rpm -iv
> /atlas/data18a/litan/OFED-1.5.3-rc5/RPMS/sl-release-5.5-1/x86_64/iscsi-initiator-utils-2.0-869.2.x86_64.rpm
>
> The default IPoIB interface configuration is based on DHCP.
> Note that a special patch for DHCP is required for supporting IPoIB.
> The patch is available under docs/dhcp
> If you do not have DHCP, you must change this configuration in the
> following steps.
> IPoIB interfaces configured successfully
> Press any key to continue ...
> Installation finished successfully.
> Press any key to continue...
>
> It seems that the IPoIB is not configured due to DHCP issues.
>
> And the OFED tools did not work also:
>
> [litan at tera05 OFED-1.5.3-rc5]$ sudo ibv_devinfo
> Failed to get IB devices list: Function not implemented
> [litan at tera05 OFED-1.5.3-rc5]$ sudo ibstat
> sudo: ibstat: command not found
>
>
>
>
>
>
> On Wed, Feb 23, 2011 at 4:14 AM, Vladimir Sokolovsky <
> vlad at dev.mellanox.co.il> wrote:
>
>> On 02/23/2011 05:12 AM, Tanin wrote:
>>
>>>  Dear all,
>>>
>>> I have recompiled the kernel to 2.6.18, and try to install  OFED-1.5.2
>>> instead.
>>>
>>> Now the kernel version is
>>>
>>> [litan at tera04 OFED-1.5.2]$ uname -a
>>> Linux tera04.ultralight.org 2.6.18-prep #1 SMP Tue Feb 22 18:51:00 EST
>>> 2011
>>> x86_64 x86_64 x86_64 GNU/Linux
>>>
>>>
>>> I have the full log file in the attachment. Dose it related to that I try
>>> many times to install different version of OFED? Thanks a million!
>>>
>>>
>> OFED's backport system is rely on kernel version.
>> So, changing kernel version changes the set of patches and headers to be
>> used for the compilation.
>> You should keep the kernel version as close as possible to the original
>> version.
>> E.g.:
>> If you compile 2.6.18 from kernel.org then you can name it 2.6.18-prep
>> But, if you recompile 2.6.18-164.el5, then you should name it
>>  2.6.18-164.<any extension>.el5
>>
>> Regards,
>> Vladimir
>>
>
>
>
>  --
> Best regards,
>
>
> -----------------------------------------------------------------------------------------------
> Li, Tan
> PhD Candidate & Research Assistant,
> Electrical Engineering,
> Stony Brook University, NY
>
> Personal Web Site: https://sites.google.com/site/homepagelitan/Home
>
> Email: fanqielee at gmail.com
>
>


-- 
Best regards,

-----------------------------------------------------------------------------------------------
Li, Tan
PhD Candidate & Research Assistant,
Electrical Engineering,
Stony Brook University, NY

Personal Web Site: https://sites.google.com/site/homepagelitan/Home

Email: fanqielee at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ewg/attachments/20110223/b1835b7b/attachment.html>


More information about the ewg mailing list