<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16674" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=572265816-04092008><FONT face=Arial color=#0000ff size=2>Thanks
- a few questions below.</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Deepak Gupta [mailto:deepak@gslab.com]
<BR><B>Sent:</B> Thursday, September 04, 2008 9:36 AM<BR><B>To:</B> Smith,
Stan<BR><B>Cc:</B> ofw@lists.openfabrics.org<BR><B>Subject:</B> Re: [ofw] Some
doubts on WinOF2.0-rc0 package<BR></FONT><BR></DIV>
<DIV></DIV>Please see in <FONT color=#ff0000>red<BR><BR></FONT>Smith, Stan
wrote:
<BLOCKQUOTE
cite=mid:3F6F638B8D880340AB536D29CD4C1E192283071F@orsmsx501.amr.corp.intel.com
type="cite">
<META content="MSHTML 6.00.6000.16674" name=GENERATOR>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> <A class=moz-txt-link-abbreviated
href="mailto:ofw-bounces@lists.openfabrics.org">ofw-bounces@lists.openfabrics.org</A>
[<A class=moz-txt-link-freetext
href="mailto:ofw-bounces@lists.openfabrics.org">mailto:ofw-bounces@lists.openfabrics.org</A>]
<B>On Behalf Of </B>Deepak Gupta<BR><B>Sent:</B> Thursday, September 04, 2008
3:05 AM<BR><B>To:</B> <A class=moz-txt-link-abbreviated
href="mailto:ofw@lists.openfabrics.org">ofw@lists.openfabrics.org</A><BR><B>Subject:</B>
[ofw] Some doubts on WinOF2.0-rc0 package<BR></FONT><BR></DIV>
<DIV>Hi,<BR><BR>I have some doubts/queries regarding WinOF2.0-rc0
release.<BR>I tried installing it on Win Server 2008 with ConnectX on box and
have following questions:--<BR><BR>1) If I select Mellanox InfiniHost package,
then installation ends prematurely (It gives error "mthca not installed"
and installation ends)<BR> Are Mellanox
InfiniHost and Mellanox ConnectX packages mutually exclusive?<SPAN
class=800215315-04092008><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=800215315-04092008></SPAN> </DIV>
<DIV><SPAN class=800215315-04092008><FONT face=Arial color=#0000ff size=2>Yes!
Different hardware devices and totally different hardware drivers.</FONT>
</SPAN><BR></DIV></BLOCKQUOTE>
<DIV><FONT color=#ff0000>After I installed packages for ConnectX and other ULPs,
I re ran the installer and went for "change" option and included Mellanox
InfiniHost and surprisingly it didn't complain and it got installed.</FONT><SPAN
class=572265816-04092008><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=572265816-04092008></SPAN> </DIV>
<DIV><SPAN class=572265816-04092008><FONT color=#0000ff>What were you attempting
to accomplish using the 'change' option?</FONT></SPAN></DIV>
<DIV><SPAN class=572265816-04092008><FONT color=#0000ff>If you only have
ConnectX hardware, then why install mthca hardware
driver?</FONT></SPAN></DIV>
<DIV><SPAN class=572265816-04092008></SPAN><SPAN
class=572265816-04092008></SPAN><FONT color=#0000ff>I<SPAN
class=572265816-04092008><FONT face=Arial size=2> <FONT
face="Times New Roman" size=3> would uninstall everything and start
over, installing only the ConnectX
driver.</FONT> </FONT></SPAN><BR><SPAN class=572265816-04092008><FONT
face=Arial size=2> </FONT></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff><SPAN class=572265816-04092008><FONT face=Arial
size=2>stan.</FONT> </SPAN></FONT></DIV>
<BLOCKQUOTE
cite=mid:3F6F638B8D880340AB536D29CD4C1E192283071F@orsmsx501.amr.corp.intel.com
type="cite">
<DIV><FONT face=Arial color=#0000ff size=2></FONT><BR>2) I am getting 5
devices being created (as shown in device manager) under following device
types (Please see the attached screen shot)<BR>
<B>InfiniBand Channel Adapters</B> and
<B>Mellanox ConnectX Adapters<BR> </B>Only one device in
each device type is working fine while others are not functions properly
(giving Dev mgr error code 10)<BR> Why do we get 5 different
device creations of each of above device types and why all devices are not
working properly.<SPAN class=800215315-04092008><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=800215315-04092008></SPAN> </DIV>
<DIV><SPAN class=800215315-04092008><FONT face=Arial color=#0000ff
size=2>Server 2008 has some curious install side effects after failed
installations. These side effects are not fully understood at this point
in time.</FONT> <FONT face=Arial color=#0000ff size=2>If you would kindly
cut-paste the last entries in %windir%\inf\setupapi.dev.log which reference
mlx4 and/or WinOF this would assist in understanding the
problems.</FONT></SPAN><B><BR></B></DIV></BLOCKQUOTE><FONT
color=#ff0000>Following is the log logged in <SPAN
class=800215315-04092008><FONT face=Arial size=2>setupapi.dev.log between two
boots</FONT></SPAN></FONT><BR><BR><FONT color=#ff0000>>>> [Device
Install (Hardware initiated) -
PCI\VEN_8086&DEV_1A38&SUBSYS_978015D9&REV_31\3&18d45aa6&0&40]<BR>>>>
Section start 2008/09/04 21:52:18.953<BR> ump: Creating
Install Process: DrvInst.exe 21:52:18.984<BR> ndv:
Retrieving device info...<BR> ndv: Setting device
parameters...<BR> ndv: Building driver
list...<BR> dvi: {Build Driver List}
21:52:19.328<BR> dvi:
Searching for hardware ID(s):<BR>
dvi:
pci\ven_8086&dev_1a38&subsys_978015d9&rev_31<BR>
dvi:
pci\ven_8086&dev_1a38&subsys_978015d9<BR>
dvi:
pci\ven_8086&dev_1a38&cc_088000<BR>
dvi:
pci\ven_8086&dev_1a38&cc_0880<BR>
dvi: Searching for compatible
ID(s):<BR>
dvi:
pci\ven_8086&dev_1a38&rev_31<BR>
dvi:
pci\ven_8086&dev_1a38<BR>
dvi:
pci\ven_8086&cc_088000<BR>
dvi:
pci\ven_8086&cc_0880<BR>
dvi:
pci\ven_8086<BR>
dvi:
pci\cc_088000<BR>
dvi:
pci\cc_0880<BR> dvi:
Enumerating INFs from path list 'C:\Windows\INF'<BR>
inf: Searched 0 potential matches in published INF
directory<BR> inf:
Searched 32 INFs in directory: 'C:\Windows\INF'<BR> dvi:
{Build Driver List - exit(0x00000000)} 21:52:21.031<BR>
ndv: Selecting best match...<BR> dvi:
{DIF_SELECTBESTCOMPATDRV} 21:52:21.031<BR>
dvi: No class installer for 'Base System
Device'<BR> dvi: No
CoInstallers found<BR>
dvi: Default installer: Enter
21:52:21.156<BR>
dvi: {Select Best
Driver}<BR>!
dvi:
Selecting driver failed(0xe0000228)<BR>
dvi: {Select Best
Driver - exit(0xe0000228)}<BR>!
dvi: Default installer:
failed!<BR>! dvi: Error
0xe0000228: There are no compatible drivers for this
device.<BR> dvi: {DIF_SELECTBESTCOMPATDRV -
exit(0xe0000228)} 21:52:21.156<BR> ndv: {Core Device
Install}<BR> ndv: Device
install status=0xe0000203<BR>
ndv: Performing device install final
cleanup...<BR>! ndv: Queueing up
error report since device installation failed...<BR>
ndv: {Core Device Install - exit(0xe0000203)}<BR> ump:
Server install process exited with code 0xe0000203
21:52:21.218<BR><<< Section end 2008/09/04
21:52:21.234<BR><<< [Exit status:
FAILURE(0xe0000203)]<BR></FONT><BR><BR>
<BLOCKQUOTE
cite=mid:3F6F638B8D880340AB536D29CD4C1E192283071F@orsmsx501.amr.corp.intel.com
type="cite">
<DIV><BR>3) Similarly InfiniBand I/O Unit Device (created under System devices
type in dev manager) is not working properly (Please see the attached screen
shot)<SPAN class=800215315-04092008><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=800215315-04092008></SPAN> </DIV>
<DIV><SPAN class=800215315-04092008><FONT face=Arial color=#0000ff
size=2>What does the device manager view properties for the IB I/O
Unit Device have to say about an error code?</FONT></SPAN></DIV><SPAN
class=800215315-04092008></SPAN>
<DIV><BR><FONT color=#ff0000>Windows cannot load the device driver for this
hardware. The driver may be corrupted or missing. (Code 39)</FONT><BR><SPAN
class=572265816-04092008><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN><SPAN
class=572265816-04092008> </SPAN></DIV></BLOCKQUOTE><BR>
<BLOCKQUOTE
cite=mid:3F6F638B8D880340AB536D29CD4C1E192283071F@orsmsx501.amr.corp.intel.com
type="cite">
<DIV>Cheers<BR>Deepak<BR></DIV><BR>-- <BR>This message has been scanned for
viruses and <BR>dangerous content by <A href="http://www.mailscanner.info/"
moz-do-not-send="true"><B>MailScanner</B></A>, and is <BR>believed to be
clean. </BLOCKQUOTE><BR></BODY></HTML>