[ofw] Some doubts on WinOF2.0-rc0 package

[Anatoly Greenblatt]

Hi Stan,
 
We have seen these phantom devices on winxp too. It has device id "PCI\VEN_15B3". It could happen when setupdi interface forcibly creates a device node.
 
Gupta, I guess you are running on x64 windows? If yes the message you see means that driver is not signed.
Also, the installer will fails when you try to install drivers for hardware that is not available.
Please send the complete setupapi.dev.log in an attachement.
 
Thanks,
Anatoly.

________________________________

From: ofw-bounces at lists.openfabrics.org on behalf of Smith, Stan
Sent: Thu 9/4/2008 8:02 PM
To: Deepak Gupta
Cc: ofw at lists.openfabrics.org
Subject: RE: [ofw] Some doubts on WinOF2.0-rc0 package


Thanks - a few questions below.

________________________________

From: Deepak Gupta [mailto:deepak at gslab.com] 
Sent: Thursday, September 04, 2008 9:36 AM
To: Smith, Stan
Cc: ofw at lists.openfabrics.org
Subject: Re: [ofw] Some doubts on WinOF2.0-rc0 package


Please see in red

Smith, Stan wrote: 

	 

________________________________

	From: ofw-bounces at lists.openfabrics.org [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Deepak Gupta
	Sent: Thursday, September 04, 2008 3:05 AM
	To: ofw at lists.openfabrics.org
	Subject: [ofw] Some doubts on WinOF2.0-rc0 package
	
	
	Hi,
	
	I have some doubts/queries regarding WinOF2.0-rc0 release.
	I tried installing it on Win Server 2008 with ConnectX on box and have following questions:--
	
	1) If I select Mellanox InfiniHost package, then installation ends prematurely (It gives error  "mthca not installed" and installation ends)
	       Are Mellanox InfiniHost and Mellanox ConnectX packages mutually exclusive? 
	 
	Yes! Different hardware devices and totally different hardware drivers. 
	

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. 
 
What were you attempting to accomplish using the 'change' option?
If you only have ConnectX hardware, then why install mthca hardware driver?
I  would uninstall everything and start over, installing only the ConnectX driver. 
 
stan. 

	
	2) I am getting 5 devices being created (as shown in device manager) under following device types (Please see the attached screen shot)
	            InfiniBand Channel Adapters and Mellanox ConnectX Adapters
	    Only one device in each device type is working fine while others are not functions properly (giving Dev mgr error code 10)
	    Why do we get 5 different device creations of each of above device types and why all devices are not working properly. 
	 
	Server 2008 has some curious install side effects after failed installations.  These side effects are not fully understood at this point in time. 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.
	

Following is the log logged in setupapi.dev.log between two boots

>>>  [Device Install (Hardware initiated) - PCI\VEN_8086&DEV_1A38&SUBSYS_978015D9&REV_31\3&18d45aa6&0&40]
>>>  Section start 2008/09/04 21:52:18.953
     ump: Creating Install Process: DrvInst.exe 21:52:18.984
     ndv: Retrieving device info...
     ndv: Setting device parameters...
     ndv: Building driver list...
     dvi: {Build Driver List} 21:52:19.328
     dvi:      Searching for hardware ID(s):
     dvi:           pci\ven_8086&dev_1a38&subsys_978015d9&rev_31
     dvi:           pci\ven_8086&dev_1a38&subsys_978015d9
     dvi:           pci\ven_8086&dev_1a38&cc_088000
     dvi:           pci\ven_8086&dev_1a38&cc_0880
     dvi:      Searching for compatible ID(s):
     dvi:           pci\ven_8086&dev_1a38&rev_31
     dvi:           pci\ven_8086&dev_1a38
     dvi:           pci\ven_8086&cc_088000
     dvi:           pci\ven_8086&cc_0880
     dvi:           pci\ven_8086
     dvi:           pci\cc_088000
     dvi:           pci\cc_0880
     dvi:      Enumerating INFs from path list 'C:\Windows\INF'
     inf:      Searched 0 potential matches in published INF directory
     inf:      Searched 32 INFs in directory: 'C:\Windows\INF'
     dvi: {Build Driver List - exit(0x00000000)} 21:52:21.031
     ndv: Selecting best match...
     dvi: {DIF_SELECTBESTCOMPATDRV} 21:52:21.031
     dvi:      No class installer for 'Base System Device'
     dvi:      No CoInstallers found
     dvi:      Default installer: Enter 21:52:21.156
     dvi:           {Select Best Driver}
!    dvi:                Selecting driver failed(0xe0000228)
     dvi:           {Select Best Driver - exit(0xe0000228)}
!    dvi:      Default installer: failed!
!    dvi:      Error 0xe0000228: There are no compatible drivers for this device.
     dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 21:52:21.156
     ndv: {Core Device Install}
     ndv:      Device install status=0xe0000203
     ndv:      Performing device install final cleanup...
!    ndv:      Queueing up error report since device installation failed...
     ndv: {Core Device Install - exit(0xe0000203)}
     ump: Server install process exited with code 0xe0000203 21:52:21.218
<<<  Section end 2008/09/04 21:52:21.234
<<<  [Exit status: FAILURE(0xe0000203)]





	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) 
	 
	What does the device manager view properties for the IB I/O Unit Device have to say about an error code?
	

	Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
	  


	Cheers
	Deepak
	

	-- 
	This message has been scanned for viruses and 
	dangerous content by MailScanner <http://www.mailscanner.info/> , and is 
	believed to be clean.