From 6eff2ee29242edb9e059d588bd3152edcfbeedde Mon Sep 17 00:00:00 2001 From: stansmith Date: Wed, 12 Nov 2008 23:08:02 +0000 Subject: [PATCH] [WINOF] synchronize for 2.0 release git-svn-id: svn://openib.tc.cornell.edu/gen1@1749 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86 --- branches/WOF2-0/branches/WinOF/WIX/README.txt | 4 +- .../branches/WinOF/WIX/README_checked.txt | 4 +- .../branches/WinOF/WIX/README_release.txt | 43 ++-- .../branches/WinOF/WIX/Release_notes.htm | 231 ++++++++++++++---- .../branches/WinOF/WIX/wlh/ia64/wof.wxs | 2 +- .../WOF2-0/branches/WinOF/WIX/wlh/x64/wof.wxs | 2 +- .../WOF2-0/branches/WinOF/WIX/wlh/x86/wof.wxs | 2 +- .../branches/WinOF/WIX/wnet/ia64/wof.wxs | 2 +- .../branches/WinOF/WIX/wnet/x64/wof.wxs | 2 +- .../branches/WinOF/WIX/wnet/x86/wof.wxs | 2 +- .../WOF2-0/branches/WinOF/WIX/wxp/x86/wof.wxs | 2 +- 11 files changed, 223 insertions(+), 73 deletions(-) diff --git a/branches/WOF2-0/branches/WinOF/WIX/README.txt b/branches/WOF2-0/branches/WinOF/WIX/README.txt index 97e2479a..8143ffea 100644 --- a/branches/WOF2-0/branches/WinOF/WIX/README.txt +++ b/branches/WOF2-0/branches/WinOF/WIX/README.txt @@ -1,4 +1,4 @@ -[9-10-08] +[11-13-08] How to generate a Windows OpenFabrics Release (WinOF) using the WIX 2.0 open source installer tool set ( http://sourceforge.net/projects/wix/ ). @@ -14,7 +14,7 @@ WinOF Revisions: 1.0 based on svn.614 1.0.1 svn.864 1.1 svn.1177 - 2.0 svn.xxxx + 2.0 svn.1748 diff --git a/branches/WOF2-0/branches/WinOF/WIX/README_checked.txt b/branches/WOF2-0/branches/WinOF/WIX/README_checked.txt index b00c80a1..3b8813e7 100644 --- a/branches/WOF2-0/branches/WinOF/WIX/README_checked.txt +++ b/branches/WOF2-0/branches/WinOF/WIX/README_checked.txt @@ -5,7 +5,7 @@ For Server 2003 or XP, replace the installed .sys file (%windir%\system32\drive with the checked version. -For Server 2008 or Vista, you must install with the signed .inf & .cat checked files. +For Server 2008 or Vista, install with the signed .inf & .cat checked files. 1) Make a copy of the free driver .sys and it's .cat file from the correct install folder in Winof\ {IBcore, net or storage}. @@ -15,4 +15,4 @@ For Server 2008 or Vista, you must install with the signed .inf & .cat checked f 3) Uninstall currently installed free driver; right-click uninstall. -4) Install signed debug from it's inf file using the found new hardware wizard. \ No newline at end of file +4) Install signed debug from it's inf file using the found new hardware wizard. diff --git a/branches/WOF2-0/branches/WinOF/WIX/README_release.txt b/branches/WOF2-0/branches/WinOF/WIX/README_release.txt index 459f4fdf..156f77b4 100644 --- a/branches/WOF2-0/branches/WinOF/WIX/README_release.txt +++ b/branches/WOF2-0/branches/WinOF/WIX/README_release.txt @@ -1,17 +1,23 @@ -[10-08-08] WinOF 2.0 (RC2) release +[11-13-08] WinOF 2.0 (RC5) release -Downloads available at http://www.openfabrics.org/downloads/WinOF/v2.0_rc2 +Downloads available at http://www.openfabrics.org/downloads/WinOF/v2.0 WinOF 2.0 Summary Changes ------------------------- -1) WinOF 2.0 release based on openib-windows svn source revision - (branches\WOF2-0 svn.1638). +1) The WinOF 2.0 release is based on openib-windows source svn revision + (branches\WOF2-0 svn.1748). Last WinOF release (1.1) based on svn 1177. + Revision 2.0? Because user-2-kernel and some kernel-2-kernel APIs + have changed. + + User-mode applications not included in the WinOF 2.0 release will need + to be rebuilt using WinOF 2.0 header files. + 2) Stability enhancements IB Core Nonexistent GUID in registry crash fixed. @@ -30,7 +36,8 @@ WinOF 2.0 Summary Changes Windows Server 2008 and Vista are now supported: Digitally signed Installer file (.msi). - Microsoft Network Direct (ND) supported for Windows Server 2008 & Vista + Microsoft Network Direct (ND) supported for Windows Server 2008 & Vista; + InfiniBand ND provider. WDK (Windows Driver Kit) build environment used to construct WinOF 2.0 @@ -41,22 +48,22 @@ WinOF 2.0 Summary Changes IPoIB: multicast garbage collector. - IGMP v2 support. - Partitioning support - see manual.htm 'part_man.exe' + IGMP v2 support only; no v3. + Partitioning support - see manual.htm 'part_man.exe'; requires IGMP v2. LSO (Large Segment Offload) available, enabled if HCA supported. - WinVerbs: OFED verbs API for Windows + WinVerbs: OFED verbs API for Windows (initial alpha release) -4) Drivers digitally signed by the OpenFabrics Alliance. +4) Kernel mode drivers digitally signed by the OpenFabrics Alliance. -5) WinOF symbol store available. +5) Network accessible WinOF symbol store available. Point windbg at http://www.openfabrics.org/downloads/WinOF/v2.0/{wlh,wnet,wxp}/SymStor Free build symbol files (.pdb) installed as %ProgramFiles%\WinOF\[IBcore,net,srp] -6) Checked/Debug signed drivers & symbols available as install feature. +6) Checked/Debug signed drivers & symbols available as an install feature. @@ -65,17 +72,25 @@ WinOF 2.0 Summary Changes After the WinOF.msi file has started installation execution, an errant "Welcome to the Found New Hardware Wizard" window 'may' popup. -Just 'cancel' the errant FNHW popup window in order to proceed with the installation. +Just ignore or 'cancel' the errant FNHW popup window in order to proceed with +the installation. XP requires a cancel, for WLH & WNET, the notifiers will +disappear on their own. You do need to answer 'Yes' or 'Continue' to those popup windows which refer to non-WHQL'ed drivers. If the install appears to hang, look around for popup windows requesting input -which are covered by other windows. +which are covered by other windows. Such is the case on Server 2008 initial +install - Answer 'yes' to always trust the OpenFabrics Alliance as a SW +publisher. +Vista installs require a command window with Administrator priviledges. +Execute this command from a Vista command window 'msiexec /i WinOF_xxx_xxx.msi'. Please: read the Release_notes.htm file! - make 'sure' your HCA firmware is recent; vstat.exe will display HCA firmware version. + make 'sure' your HCA firmware is recent; vstat.exe displays HCA firmware + version. thank you. + diff --git a/branches/WOF2-0/branches/WinOF/WIX/Release_notes.htm b/branches/WOF2-0/branches/WinOF/WIX/Release_notes.htm index 06733c23..33b9a0a8 100644 --- a/branches/WOF2-0/branches/WinOF/WIX/Release_notes.htm +++ b/branches/WOF2-0/branches/WinOF/WIX/Release_notes.htm @@ -92,7 +92,7 @@ src=openfabrics.gif>

2.0 Release Notes

-10/08/2008

+11/12/2008
@@ -111,7 +111,7 @@ How to Install

-Unattended Install

+Unattended Install plus Server2008/HPC

Setting the IPoIB Interface IP Address

@@ -145,7 +145,7 @@ InfiniBand fabric.

 Binary files generated from the OpenIB-windows developers subversion (svn) source tree 'svn://openib.tc.cornell.edu' -(branches\WOF2-0 svn revision 1638) +(branches\WOF2-0 svn revision 1748) are packaged into a WIX 2.0 (Windows Installer Xml) single file install package referred to as the Windows OpenFabrics (WinOF) release 2.0.
@@ -160,13 +160,28 @@ to numerous components:

Windows Server 2008 and Vista are now supported.

  • +

    Network Direct + supported on Server 2008/HPC.

    • +

  • Mellanox ConnectX(mlx4) drivers - enhanced for increased stability.

    • + enhanced for increased performance and stability.

  • QLogic has - enhanced VNIC & SRP for increased stability.

    • + enhanced VNIC & SRP for increased performance and stability.

  • Bug fixes for stability in IBcore, WSD, VNIC, SRP, IPoIB, DAT/DAPL

    +

    In WinOF 2.0 + the ABI changed and thus all user-mode applications not included in + the WinOF 2.0
    + release, need to recompile.
    + There are changes in the API,
    +    user-mode:
    +        ib_cm_listen() at ib_al.h changed.
    +
    +    kernel mode: (ibal <--> hca)
    +        ci_open_ca(),
    +        ci_create_{cq, qp, spl_qp, srq} all + changed.

    • @@ -191,7 +206,7 @@ supported devices below Infiniband Core components

  • Upper Layer Protocols: - IPoIB, WSD, VNIC, SRP Initiator and DAT/DAPL

    • + IPoIB, WSD, ND, VNIC, SRP Initiator and DAT/DAPL

    OpenFabrics utilities:

    @@ -252,13 +267,11 @@ supported devices below

    Windows Server 2008 HPC Edition

  • -

    Windows Server 2003

    -
    • -
  • -

    Windows Server 2003 Compute Cluster Edition

    +

    Windows Server 2003 + / XP64

  • -

    Windows XP (SP2)

    +

    Windows XP/32 (SP2)

    • @@ -300,7 +313,7 @@ Current HCA firmware version can be viewed from the 'vstat' command.

  • SilverStorm - - update your firmware!

    + update your firmware for correct embedded Subnet Manager operation.

  • Voltaire

    @@ -332,17 +345,18 @@ path; new command windows created after the installation will have the updated %PATH% environment variable, hence will be able to access WinOF executables.

    The ‘default’ installation installs ‘released/free’ (not -checked/debug) versions of drivers and executables.

    +checked/debug) versions of drivers and executables. Debug/Checked versions are +available as an install feature.

    A single instance of a subnet manager, opensm.exe, must be running on a fabric connected node in order for the Infiniband fabric to be -configured and useful; either Windows or Linux opensm work well.

    +configured and useful; either Windows or Linux OFED opensm work well.

    It is recommended that OpenSM be run as a Windows service.  A typical WinOF install will install OpenSM as a Windows service which is disabled; after an installation, choose your openSM node and start the openSM service.  See the WinOF Manual for details on opensm as a service.
    -By selecting the 'OpenSM_service_enabled' feature, an OpenSM subnet +By selecting the 'OpenSM_Service_Enabled' install feature, an OpenSM subnet management service will be automatically started.

    Note, the opensm.exe process must continue to run in order @@ -365,16 +379,17 @@ OpenFabrics manual.

    package. Upon reboot, cancel any attempts to install new device hardware from the "Found New Hardware Wizard".

    -

    If you have previously installed openib-windows, Windows OpenFabrics +

    If you have previously installed openib-windows, WinOF (Windows OpenFabrics) packages or vendor supplied Infiniband packages, uninstall and reboot prior to installing this version of Windows OpenFabrics (WinOF).

    -

    For an existing Windows OpenFabrics uninstall
    -    Programs-> Windows OpenFabrics-> Uninstall WinOF
    +

    For an existing Windows OpenFabrics (WinOF) uninstall
    +    Start-> Programs-> Windows OpenFabrics-> Uninstall WinOF
          -or-
        Control Panel -> Add or Remove Programs-> Windows OpenFabrics->Remove.

    -

    openib-windows uninstall:

    +

    openib-windows (IB stack before WinOF 1.0 release) uninstall: (not the normal +uninstall case, see previous discussion)

    1. Stop the openSM subnet manager if it is running on the @@ -401,9 +416,9 @@ drivers for newly discovered PCI device.

      From a login with administrator privileges, double-click the -WinOF_M-m_OSE_arch_setup.msi file to begin the Windows OpenFabrics installation. 

      -

      Where 'M-n' indicates Major release number, Minor release number (a.k.a. -point-release will increment the minor number).

      +WinOF_M-m{-p}_OSE_arch.msi file to begin the Windows OpenFabrics installation. 

      +

      Where 'M-n{-p}' indicates Major release number, Minor release number, and +optional point-release number.

       OSE - Operating System Environment:

      • wlh - (Windows LongHorn) Windows Server 2008, HPC or Vista
        • @@ -412,7 +427,8 @@ point-release will increment the minor number).

      '_arch_' will be one of

        -
      • _x64_ for  Intel EMT64 systems or amd64
        • +
      • _x64_ for  Intel EMT64 systems or amd64; see + x86-64
      • _x86_ for x86 compatible systems
      • _ia64_ for Intel IA64 systems.
        • @@ -426,7 +442,8 @@ These non-WHQL'ed driver install questions can not be disabled via 'My Computer->Properties->Hardware->Driver Signing->Ignore'.

        Bottom-line - The digitally signed WinOF drivers in this package are not WHQL'ed per se, although they are -built from driver source which has been or is in process of being WHQL'ed.

        +built from driver source which has been or is in process of being WHQL'ed by +hardware vendors which participate in the open source WinOF development process.

         

         **** WARNING ****

        @@ -462,7 +479,7 @@ built from driver source which has been or is in process of being WHQL'ed.

      • HCA driver - Mellanox: InfiniHost or ConnectX
      • IB core stack and libraries.
      • Release Notes, Manual
        • -
      • Subnet Management [opensm], Performance & Diagnostic tools
        • +
      • Subnet Management service [OpenSM] (installed & disabled), Performance & Diagnostic tools
    2. Optional:
          IPoIB - Internet Protocols over InfiniBand
          Winsock Direct (Win2008/3 only)
      @@ -487,10 +504,11 @@ built from driver source which has been or is in process of being WHQL'ed.

      Unattended Install

      -

      To perform a silent/unattended installation, invoke the following command - from a command window.

      +

      To perform a silent/unattended installation for Server 2003/XP, invoke + the following command from a command window; Server 2008/HPC see notes + below.

      -

      start/wait msiexec.exe /i WinOF_2-0_wlh_x64.msi /quiet /passive /log +

      start/wait msiexec.exe /i WinOF_2-0_wlh_x64.msi /quiet /log %TEMP%\WOF_install.log

      '/log dev:path\logFilename.log' is optional.

      msiexec.exe /? for all options.

      @@ -501,12 +519,60 @@ built from driver source which has been or is in process of being WHQL'ed.

      Documentation
    3. IPoIB - Internet Protocols over InfiniBand
    4. WSD - (Win2K8/3 only, not installed on XP) Win Sock Direct
      5. -
    5. DAT & DAPL (v1.1) runtime libraries.
      6. +
    6. ND - Network Direct, started automatically (via ndinstall.exe) only for Server + 2008/HPC and Vista.
      7. +
    7. DAT & DAPL (v1.1 & v2.0) runtime libraries + dapltest.exe + (dt-svr & dt-cli).

    • Should WSD not be a desirable unattended install option (Win2008/3 only), currently you would install unattended then execute the command 'installsp -r' on each node to remove WSD.

    +

    Server 2008/HPC notes

    +

    Device drivers in WinOF 2.0, and later releases, are Digitally +signed although they are not WHQL'ed (Windows Quality Hardware Labs) certified. The lack +of WHQL certification impacts unattended installs by requiring the user to +'accept' +installation of the non-WHQL'ed driver the first time a compute node is +installing WinOF drivers via the WinOF .msi installer.  Additionally the non-WHQL +driver notifier box has a +checkbox which allows establishing a trust for software from the publisher +'OpenFabrics Alliance'. Checking this box allows future WinOF driver installs to proceed +without user intervention as you have indicated to Windows that you trust non-WHQL +drivers from the Openfabrics Alliance software publisher.

    +

    ***** Warning *****
    +WinOF .msi installs on compute nodes the first time require human input to 'accept' +installation of non-WHQL'ed drivers along with establishing a trust for the SW +publisher 'OpenFabrics Alliance'.
    +If one attempts an unattended WinOF .msi install using 'clusrun.bat msiexec /i +WinOF.....msi /quiet', the install will +silently hang waiting for user input.
    +First time unattended WinOF .msi installs need mouse input to complete.  +Once the SW publisher trust has been established, future unattended WinOF .msi +installs procees without human input.

    +

    Be aware: if a node is reimaged (saem or different template applied) the +established trust of OpenFabric Alliance is destroyed, thus the non-WHQL driver +notifier box and ensuing human input is again required on the first WinOF .msi +install.

    +

    Windows Deployment Manager usage for HPC compute node provisioning

    +

    Microsoft has chosen the WDM to provision HPC +cluster compute nodes. WinOF 2.0 supports an administrative install mode which +is a method to extract the WinOF  files without actually installing them, +thus making WinOF driver files accessible for WDM provisioning.

    +

    msiexec /a WinOF_2-0_wlh_x64.msi TARGETDIR=dev:\path-to-extracted-files

    +

    example:  msiexec /a WinOF_2-0_wlh_x64.msi TARGETDIR=C:\windows\Temp\WOF    +(note: TARGETDIR is case sensitive)

    +

    The above command creates the following folder structure:
    + +C:\windows\Temp\WOF\PFiles\WinOF\
    +    IBcore\mthca.inf             +Mellanox InfiniHost HCA driver
    +    IBcore\mlx4_bus.inf        +Mellanox ConnectX bus driver
    +    IBcore\mlx4_hca.inf        +Mellanox ConnectX HCA driver (both ConnectX drivers required).
    +    net\netipoib.inf                +IPoIB + Network Direct IB provider + WSD (Winsock Direct) provider.

    See Unattended Installations for further references.

    <Return-to-Top>

    @@ -515,7 +581,16 @@ Installations for further references.

    The Windows command 'netsh' will assist in assigning an IP address to an IPoIB interface.
    By default, an IPoIB interface is configured to use DHCP. The following -discussion deals with setting a static IP address on an IPoIB interface.

    +discussion deals with setting a static IP address on an IPoIB interface.
    +If your system has two Ethernet ports, then IPoIB interfaces (HCA port 1, 2...) +will be assigned to 'Local Area Connection 3' and 'Local Area Connection 4'.  +If you system has a single Ethernet port, then IPoIB interface is Local Area +Connection 2'.

    +

    For Server 2008/HPC systems, the WinOF installation follows the above +discussion. In defining HPC network interfaces, the IPoIB network can be +identified as the 'Application' network. In this case, a few minutes after a +compute node is installed, the local network manager will rename the installed +IPoIB 'Local Area Connection X' network interface to the 'Application' network.

    Display all network interface configuration information
            netsh interface ip show config
            netsh interface ip show address @@ -541,10 +616,11 @@ Uninstall

    From a Command Window invoke the following command; a system reboot will occur after the uninstall.

    -

    start/wait msiexec.exe  /x {3A6A276E-A636-48E8-8624-9A0DE3F2A15E} /quiet /passive +

    start/wait msiexec.exe  /x {3A6A276E-A636-48E8-8624-9A0DE3F2A15E} + /quiet /forcerestart
      - or -
    - start/wait msiexec.exe  /x WinOF_wlh_2-0_x64.msi /quiet /passive /forcerestart        + start/wait msiexec.exe  /x WinOF_wlh_2-0_x64.msi /quiet /forcerestart        # WinOF_xxxx.msi is the file used to install WinOF.

    msiexec.exe /help for details.

    '/log dev:path\logfilename.log'  if you wish to later view the install @@ -561,8 +637,10 @@ occur after the uninstall.

    Trouble Shooting

    Vista installs can fail to install the HCA driver due to protection failures -- installing from a non-privileged Administrator window.
    -Startup a privileged Administrator window and execute: msiexec /I +- installing from a non-privileged Administrator window or double-clicking the .msi +file.
    +Startup a privileged Administrator command window (Start->Command +Prompt->Right-click->Run as Administrator) and execute: msiexec /I WinOF_xxx_yyy.msi

    To create a LOG file of your WinOF installation, execute this command: msiexec /I WinOF_xxx_yyy.msi  /Lv %TEMP%\WOF-install.log
    @@ -675,15 +753,22 @@ mso-text-indent-alt:217;mso-char-wrap:1;mso-kinsoku-overflow:1">
    At this juncture, check the Device Manager and uninstall the PCI device from 'InfiniBand Host Channel Adapters', and make sure you uninstall the system device - 'InfiniBand Fabric'.
    + 'InfiniBand Fabric' if it is present.

    - REBOOT and retry the WinOF installation again.

    <Return-to-Top>

      + REBOOT and retry the WinOF installation again.

    See + ibscan.bat and ibcleanup.bat @ + + http://www.openfabrics.org/downloads/WinOF/etc/.
    + ibscan will display WinOF files on your system.
    + ibcleanup will attempt to remove all WinOF files from your syste. + WARNING - ibcleanup is not valid as a WinOF uninstall tool!

    <Return-to-Top>

     

    Correct Installation Validation

    From the Device Manager you should find the following devices:

      -
    • InfiniBand Host Channel Adapters -> InfiniHost
      • -
    • System Devices -> InfiniBand Fabric
      • +
    • InfiniBand Host Channel Adapters -> InfiniHost or Mellanox ConnectX
      • +
    • The System Devices -> InfiniBand Fabric device is no longer present in + WinOF 2.0 and following releases.
    • Network Adapters -> OpenIB IPoIB Adapter (an Instance per HCA port).
    @@ -735,11 +820,11 @@ check for your desired adapter ordering.

  • Start->Programs->Windows OpenFabrics->Release Notes  (2nd Line)
  • Driver confirmation:
        Query My Computer-> Manage-> Device Manager-> Network -Adapters-> OpenIB IPoIB Adapter-> Properties-> Driver-> Details
        The subversion (svn) revision number will be listed under +Adapters-> OpenFabrics IPoIB Adapter-> Properties-> Driver-> Details
        The subversion (svn) revision number will be listed under 'Driver Version'. The svn revision number will match what's listed in the release notes.
  • Hold the mouse point over \Program Files(x86)\WinOF\ib_read_bw.exe to display -the file version; the 4th field is the svn revision number.
    • +the file version; [WinOF-Major.Minor.not-used.svn revision number].
    • WinOF 1.0 is based on openib-windows svn revision 614 @ @@ -750,7 +835,7 @@ the file version; the 4th field is the svn revision number.
    • WinOF 1.1 is based on openib-windows (svn revision 1177 branches\WOF1-1).
       
      • -
    • WinOF 2.0 is based on (svn.1638 branches\WOF2-0)
      • +
    • WinOF 2.0 is based on (svn.1748 branches\WOF2-0)

    <Return-to-Top>

     

    @@ -890,16 +975,66 @@ Once completed, the "New Hardware Found" Wizard pops up again.

    Known Issues

      +
    • +

      In a multi HCA + (Host Channel Adapter) system, disabling HCA devices works correctly EXCEPT + for disabling the first HCA while other HCAs are operational. Once the first + HCA is disabled, existing HCAs and user-mode applications lose the + connection to the kernel mode IB stack and will fail when attempting access + to the IB stack or hardware.
      + Problem will be addressed in the next WinOF 2.0 release.
      + 

      • +
    • +

      IPoIB partition + multicast + support requires IGMP (Internet Gateway Management Protocol) v2 Windows default is v3.
       

      +
      Partition + multicast on ipoib will only work if the machine is configured to use + IGMP V2 (and not V3 which is the default).
      +
      To + configure your machine to use IGMP v2 please do the following:
      +
       
      +
      Server + 2003 or XP:
      +
      +

      netsh routing ip igmp install

      +
      +

      netsh routing ip igmp install add + interface "interface name of IPoIB adapter"  igmpprototype=igmprtrv2

      +       + +

      If IGMP V3 is still used, please follow the instructions on + (http://support.microsoft.com/default.aspx/kb/815752)

      + +

       

       + +

      Server 2008 or + HPC or Vista:

      +
      + If the netsh command is not + available, then you will need to install via the command 'servermanagercmd.exe + -install NPAS-RRAS-Services'.
      +
      +
      +

      netsh + routing ip igmp + install

      +
      +

      netsh + routing ip igmp install + add interface "interface name of IPoIB + adapter"  igmpprototype=igmprtrv2

      +

       

       + +

      Future WinOF releases + will support IGMP V3.

      +

       

    • Sometimes an errant "Welcome to the Found New Hardware Wizard" window pops up during - InfiniBand device installation.
      - Just 'cancel' the FNHW popup window and proceed with installation.
      - An artifact of the 'Cancel' operation may cause a taskbar Information bubble + InfiniBand device installation on XP or Server 2003.
      Just 'cancel' the FNHW popup window and proceed with installation.
      An artifact of the 'Cancel' operation may cause a taskbar Information bubble to appear which incorrectly claims problems with the Infiniband device - installation; Check IB device status via the Device Manager.
      - Microsoft claims this behavior is resultant from installation of non-signed - device drivers coupled with the IB fabric coinstaller.

      • + installation; Check IB device status via the Device Manager.

    @@ -932,7 +1067,7 @@ Once completed, the "New Hardware Found" Wizard pops up again.
    bytes.

    - Set the registry entry + Setting the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ibsrp\Parameters\ModeFlags

     to 1 will diff --git a/branches/WOF2-0/branches/WinOF/WIX/wlh/ia64/wof.wxs b/branches/WOF2-0/branches/WinOF/WIX/wlh/ia64/wof.wxs index 76188589..064e2b74 100644 --- a/branches/WOF2-0/branches/WinOF/WIX/wlh/ia64/wof.wxs +++ b/branches/WOF2-0/branches/WinOF/WIX/wlh/ia64/wof.wxs @@ -3,7 +3,7 @@ WinOF (Windows OpenFabrics) for IA64/IPF Itanium on Windows Server 2008 --> - - - - - - -