[ofw] Windows v .614 doesn't detect IPoIB devices

Jan Bottorff jbottorff at xsigo.com
Thu May 31 03:10:57 PDT 2007


That sounds a lot like the symptoms of the IB coinstaller DLL not
getting updated with the new build. My experience has been, coinstallers
don't get updated with the latest version automatically by an INF file.
You need to get an install application to handle this. It only shows up
when you are upgrading a system with an older incompatible coinstaller.
Putting something in the release notes might be good. My general policy
is: there is no assurance than an upgrade between periodic builds will
work correctly. Upgrades between official releases will need to be
tested as working.

- Jan

-----Original Message-----
From: ofw-bounces at lists.openfabrics.org
[mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Jeremy Enos
Sent: Wednesday, May 30, 2007 2:43 PM
To: ofw at lists.openfabrics.org
Subject: Re: [ofw] Windows v .614 doesn't detect IPoIB devices

I think I may have cured this on my own... checked the driver version 
for the Infiniband Fabric device, and it did not get updated with the 
HCA (was still at 432, which apparently worked fine w/ HCA driver 
version 459).  Once I forced the Infiniband Fabric device to update to 
.614, the IPoIB devices appeared.

    Jeremy

Jeremy Enos wrote:
> So I'm putting together a windows image using version 614 of openib 
> drivers.  Last time I did this, I was using version 459, and when the 
> HCA driver was loaded, two IPoIB devices popped up and needed drivers 
> loaded too.  The HCA driver for v 614 detects and loads fine, as well 
> as the "Infiniband Fabric" found under System devices.  However, no 
> new devices are detected for IPoIB.  The event log is pretty clean 
> too... just 2 informational (blue flag) entries for the mthca driver 
> loading.
> My operating system is Windows Compute Cluster x64, using a Dell 1855 
> blade with a daughter card HCA (Infinihost III pci-e based, using DLGL

> 4.7.600 fw).
> I have read in some list threads that this behavior can be due to an 
> out of date firmware, and I should check w/ my vendor for an updated 
> version.  However, I think I've got the latest fw offered by my 
> vendor, and as well I've heard reports that this fw version and same 
> daughter card have worked fine for someone else with driver version
614.
> So what should I do next to solve this issue?
> thx-
>
>    Jeremy Enos
>    NCSA
>
> _______________________________________________
> ofw mailing list
> ofw at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
_______________________________________________
ofw mailing list
ofw at lists.openfabrics.org
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw



More information about the ofw mailing list