<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16414" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=397055715-01062007><FONT face=Arial color=#0000ff size=2>The
WinOF 1.0 install package addresses your cluster requirements in execution and
documentation (Release Notes).</FONT></SPAN></DIV>
<DIV><SPAN class=397055715-01062007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=397055715-01062007><FONT face=Arial color=#0000ff
size=2>stan.</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> ofw-bounces@lists.openfabrics.org
[mailto:ofw-bounces@lists.openfabrics.org] <B>On Behalf Of </B>Jeremy
Enos<BR><B>Sent:</B> Thursday, May 31, 2007 1:00 PM<BR><B>To:</B> Jan
Bottorff<BR><B>Cc:</B> ofw@lists.openfabrics.org<BR><B>Subject:</B> Re: [ofw]
Windows v .614 doesn't detect IPoIB devices<BR></FONT><BR></DIV>
<DIV></DIV>Offline, I was just making a similar point. I didn't mention
it, but I was doing this upgrade interactively (and of course expected
everything to just work). I was only doing this upgrade
interactively because I haven't built my cluster yet from this 'golden
client'. Future upgrades will need to be non-interactive, which really
needs to be an option for any installer utility as well. Particularly with
respect to the nature of IB users... I estimate convenient,
non-interactive needs to be very typical. I look forward to the day that
there is a reliable installer/updater with both interactive and non-interactive
modes made available.<BR><BR> Jeremy<BR><BR>Jan Bottorff
wrote:
<BLOCKQUOTE cite=mid:9146E3EBBFBCC94D95F95A1C4065348A018DCB3A@exch01.xsigo.com
type="cite"><PRE wrap="">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: <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>] On Behalf Of Jeremy Enos
Sent: Wednesday, May 30, 2007 2:43 PM
To: <A class=moz-txt-link-abbreviated href="mailto:ofw@lists.openfabrics.org">ofw@lists.openfabrics.org</A>
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:
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">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
</PRE></BLOCKQUOTE><PRE wrap=""><!---->
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">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
</PRE></BLOCKQUOTE><PRE wrap=""><!---->614.
</PRE>
<BLOCKQUOTE type="cite"><PRE wrap="">So what should I do next to solve this issue?
thx-
Jeremy Enos
NCSA
_______________________________________________
ofw mailing list
<A class=moz-txt-link-abbreviated href="mailto:ofw@lists.openfabrics.org">ofw@lists.openfabrics.org</A>
<A class=moz-txt-link-freetext href="http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw">http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw</A>
</PRE></BLOCKQUOTE><PRE wrap=""><!---->_______________________________________________
ofw mailing list
<A class=moz-txt-link-abbreviated href="mailto:ofw@lists.openfabrics.org">ofw@lists.openfabrics.org</A>
<A class=moz-txt-link-freetext href="http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw">http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw</A>
</PRE></BLOCKQUOTE></BODY></HTML>