Back to Contents Page

Windows Driver Software: Broadcom NetXtreme II™ Network Adapter User Guide

Installing the Driver Software

Removing the Device Drivers

Using the NetXtreme II Monolithic Driver

Inserting the NetXtreme II Monolithic Driver in a WinPE 2.0 Image

Viewing or Changing the Properties of the Adapter

Setting Power Management Options

Installing the Driver Software

NOTE: These instructions are based on the assumption that your Broadcom NetXtreme II adapter was not factory installed. If your controller was installed at the factory, the driver software has been installed for you.

When Windows first starts after a hardware device (such as a Broadcom NetXtreme II Adapter) has been installed, or after the existing device driver has been removed, the operating system automatically detects the hardware and prompts you to install the driver software for that device.

Both a graphical interactive installation mode (see Using the Installer) and a command-line silent mode for unattended installation (see Using Silent Installation) are available.

NOTES:

Using the Installer

If supported and if you will use the Broadcom iSCSI Crash Dump utility, it is important to follow the installation sequence:

To install the Broadcom NetXtreme II drivers

  1. When the Found New Hardware Wizard appears, click Cancel.
  2. Insert the installation CD into the CD or DVD drive.
  3. On the installation CD,open the folder for your operating system, open the DrvInst folder, and then double-click Setup.exe to open the InstallShield Wizard.
  4. Click Next to continue.
  5. After you review the license agreement, click I accept the terms in the license agreement and then click Next to continue.
  6. Select how you want to install the NetXtreme II drivers and then click Next.
  7. Click Install.
  8. Click Finish to close the wizard.
  9. The installer will determine if a system restart is necessary. Follow the on-screen instructions.

Using Silent Installation

NOTES:

To perform a silent install from within the installer source folder

Type the following:

setup /s /v/qn

or

msiexec /i "BDrv5706.msi" /qn

To perform a silent upgrade from within the installer source folder

Type the following:

setup /s /v/qn

To perform a silent uninstall from within the installer source folder

Type the following:

msiexec /x "BDrv5706.msi" /qn

To perform a silent uninstall from any folder

msiexec /x "{F0DA8A3F-1457-419E-96F4-235DD3EF41E1}" /qn

NOTE: The hexidecimal number above may differ from your current installer. Check the Key name corresponding with the Broadcom Advanced Control Suite 3 (BACS) application in HKLM\Software\Mictrosoft\Windows\CurrentVersion\Uninstall for the correct hexidecimal number.

To perform a silent reinstall of the same installer

Type the following:

setup /s /v"/qn REINSTALL=ALL"

NOTE: The REINSTALL switch should only be used if the same installer is already installed on the system. If upgrading an earlier version of the installer, use setup /s /v/qn as listed above.

To perform a GUI reinstall of the same installer

Type the following:

setup /V"REINSTALL=ALL"

If performing a silent upgrade or uninstall, ensure to do a manual reboot afterwards to avoid leaving the system in an inconsistent state.

During silent upgrade or uninstall, your system may reboot automatically. If you wish to suppress the reboot, please append REBOOT=ReallySuppress to the end of the corresponding upgrade or uninstall command listed above.

In some circumstances, reboot is required before uninstallation can continue. If you used REBOOT=ReallySuppress to suppress the reboot, the uninstallation may be suspended. You will need to reboot manually for the uninstallation to continue.

To perform a silent install and create a log file at (f:\1testlog.txt)

setup /s /v"/qn /L f:\1testlog.txt"

Removing the Device Drivers

NOTE: Windows Server 2008 and Windows Server 2008 R2 provide the Device Driver Rollback feature to replace a device driver with one that was previously installed. However, the complex software architecture of the NetXtreme II device may present problems if the rollback feature is used on one of the individual components. Therefore, we recommend that changes to driver versions be made only through the use of a driver installer.

To remove the device drivers

  1. In Control Panel, double-click Add or Remove Programs.
  2. Click Broadcom NetXtreme II GigE Driver Installer, and then click Remove. Follow the onscreen prompts.
  3. Click Yes to restart your system.
  4. - or -

  5. Click No to restart your system at a later time. Click OK to acknowledge that the installation has been suspended. The uninstallation of the driver is postponed until the next restart of your system.

Using the NetXtreme II Monolithic Driver

The NetXtreme II, based on its advanced functionalities, uses a software architecture that includes a Virtual Bus Device (VBD) to extend functionalities beyond basic network connectivity. Microsoft, however, does not currently support this architecture when loading an operating system through its Windows Deployment Services (WDS), which was previously known as Remote Installation Services (RIS), or for the deployment agent used in the Automated Deployment Services (ADS). Therefore, a separate driver was created to accommodate these Microsoft deficiencies. This driver is known as the NetXtreme II monolithic driver, but it is sometimes referred to as the "RIS" driver.

The NetXtreme II monolithic driver was developed to work only for the text mode portion of a WDS legacy installation and to establish connectivity with a deployment agent for ADS. It is not intended to be used as a driver loaded in the running state of an operating system. The exception to this would be when used for the Windows Preinstallation Environment (WinPE).

For WDS, this driver is used similarly to any other network adapter driver for supporting network connectivity after the PXE boot to the WDS server. When placed in the I386 or AMD64 directory (depending on the version of the operating system being deployed), the monolithic driver is called to establish that there is driver support for the NetXtreme II adapter included in the WDS legacy image.

For ADS, the driver is placed in the PreSystem directory on the server running ADS to establish connectivity with the deployment agent on remote systems with NetXtreme II adapters when booting from PXE.

While Windows PE 2005 natively supports the VBD architecture, it was found that using the "minint" switch in the startnet.cmd file does not. The minint switch performs a limited scan of the system bus to identify network devices only and, therefore, does not support the VBD architecture. Since only network connectivity is required in Windows PE, the only supported driver is the monolithic driver for the NetXtreme II adapter in this environment as well. Place the b06nd.inf file in the INF directory within the Windows PE image, and place the appropriate driver file (b06nd51a.sys for x64-based builds or b06nd51.sys for x86-based builds) in the driver's directory. If Windows PE is deployed as a flat image from a RIS or WDS server, you must also place both the b06nd.inf and the appropriate driver file in the I386 or AMD64 directory containing the image. If the RIS or WDS server is running Windows 2000 Server and deploying an x86 WinPE image, you may need to include the Windows 2000 monolithic driver file (b06nd50x.sys) in the I386 directory. In cases where adding the Windows 2000 monolithic driver still does not work, apply the following modification to the b06nd.inf file located in the I386 directory as follows:

  1. Locate [Manufacturer] header within the file.
  2. Review the line below it which reads: %brcm% = broadcom, ntx86, ntamd64, ntia64 or equivalent.
  3. Modify that line to read: %brcm% = broadcom.ntx86, ntamd64, ntia64. The change made replaces the comma and space after "broadcom" with a period.
  4. Save the file.
  5. Restart the RIS service (binlsvc) or WDS services (wdsserver).

Inserting the NetXtreme II Monolithic Driver in a WinPE 2.0 Image

The Microsoft Windows Server 2008 method of inserting the NetXtreme II monolithic driver in a WinPe 2.0 image is different from the Windows Server 2008 R2 method, as discussed below.

By default, the monolithic driver is not included in the boot.wim and install.wim files that come with the Microsoft Windows Server 2008/Vista CD. Microsoft's Windows Automated Installation Kit (AIK) allows you to modify the default boot.wim and install.wim files, and create WinPE 2.0 images to include the NetXtreme II monolithic driver in the Windows Server 2008/Vista installation.

To insert the monolithic driver into a WinPE 2.0 boot image (Windows Server 2008)

To insert Broadcom's NetXtreme II monolithic driver in a WinPE 2.0 image, download AIK from http://www.microsoft.com/downloads/en/default.aspx and install.

After installing AIK, copy the latest monolithic driver to a directory on the local hard drive of the system you installed the AIK. Follow the procedure below to insert the monolithic driver into a WinPE 2.0 boot image.

  1. From All Programs, open Windows AIK and select Windows PE Tools Command prompt.
  2. At the command prompt, run the copype.cmd script. The script requires two arguments: hardware architecture and destination location.
  3. copype.cmd <arch> <destination>
    

    For example: copype x86 c:\VistaPEx86

    NOTE: The directory structure c:\VistaPEx86 is used throughout this procedure.

  4. Mount the base image to a local directory so that you can add or remove packages by typing:
  5. imagex /mountrw c:\VistaPEx86\winpe.wim 1 c:\VistaPEx86\mount
    
  6. Place the monolithic driver and inf file in c:\drivers\x32\ by typing:
  7. peimg /inf=c:\Drivers\x32\b06nd.inf c:\VistaPEx86\mount\windows
    

    AIK inserts the driver into the WinPE 2.0 image.

  8. To complete the customization of the image, prepare the image for deployment, type:
  9. peimg /prep c:\VistaPEx86\mount\windows
    
  10. When asked to continue and have the program prepare the image for deployment, type:
  11. yes
    
  12. To commit the changes to the original image file (Winpe.wim), type:
  13. imagex /unmount c:\VistaPEx86\mount /commit
    
  14. To replace the default Boot.wim file in the \ISO directory with your new custom image, type:
  15. copy c:\VistaPex86\winpe.wim c:\VistaPEx86\ISO\sources\boot.wim
    

To add a device driver to an offline Windows PE image (Windows Server 2008 R2)

This procedure demonstrates how to use the Deployment Image Servicing and Management (DISM) tool to add a device driver (.inf) to an offline Windows PE image. Before running a DISM command, first mount the Windows PE image.

  1. Mount the base image by using the DISM tool to a local Windows PE directory. For example:
  2. Dism /Mount-WIM /WimFile:c:\winpe_x86\winpe.wim /index:1 /MountDir:c:\winpe_x86\mount
    

    NOTE: The directory structure c:\winpe_x86 is used throughout this procedure.

  3. Add the .inf file to the base image by using the dism command with the /Add-Driver option. For example Driver.inf is the Broadcom driver, evnd.inf is the driver for the 10 Gbps devices, and b06nd.inf is the driver for the 1 Gbps devices.
  4. Dism /image:<path_to_image> /Add-Driver /Driver:c:\winpe_x86\mount\Windows\driver.inf
    
  5. Repeat steps 1 and 2 for each additional device driver.
  6. Unmount the image after modifying it.
  7. dism /unmount-wim /Mountdir:c:\winpe_x86\mount /commit
    
  8. After unmounting the image, burn it to the designated media.

To create a bootable CD-ROM

  1. On your technician computer, at the command prompt, create an .iso file by typing:
  2. oscdimg -n -bc:\VistaPEx86\etfsboot.com c:\VistaPEx86\ISO C:\VistaPEx86\VistaPEx86.iso
    
  3. Burn the iso image to a CD.

Configuring the Speed/Duplex Setting for the NetXtreme II Monolithic Driver

Since the typical environment where the NetXtreme II monolithic driver is used does not provide the means to configure advanced network adapter properties, the driver file (b06nd.inf) was modified to include a section that allows it to be configured for a specific speed and/or duplex. This provides a more robust connection to the network as it allows the adapter to match the settings of its link partner (e.g., a switch, router, etc.).

To manually configure the speed and duplex

  1. Open the b06nd.inf file with a text editor like Microsoft Notepad or WordPad.
  2. Perform a search on the file for "Registry parameters" to locate the section that will allow you to configure the adapter speed/duplex.
  3. Once located, notice the following information shown.
  4. [params_utp]
    
    hkr, , req_medium,          2, "0"
    
    [params_fiber]
    
    hkr, , req_medium,          2, "65283"
    

These make up two separate sections that can be configured: one for standard RJ-45 copper interfaces (params_utp) and one for fiber devices (params_fiber).

  1. As described in the file, replace the value above in quotation marks under the correct section, depending upon the network adapter in your system. The available values are shown below.
  2. Options for copper interfaces:

    • Auto (1 Gbps is enabled when that speed is supported) = "0"
    • 10 Mbps Half Duplex = "65794"
    • 10 Mbps Full Duplex = "258"
    • 100 Mbps Half Duplex = "66050"
    • 100 Mbps Full Duplex = "514"
    • Options for fiber interfaces:

    • Auto (1 Gbps is enabled when that speed is supported) = "0"
    • 1 Gbps Full Duplex = "771"
    • Auto with 1 Gbps Fallback = "33539"
    • Hardware default = "65283"

An example is provided in the file showing how to configure a copper interface for a 10 Mbps Full Duplex connection. The example is shown below.

hkr, , req_medium,          2, "258"

Viewing or Changing the Properties of the Adapter

To view or change the properties of the Broadcom network adapter

  1. In Control Panel, click Broadcom Control Suite 4.
  2. Click the Advanced section of the Configurations tab.

Setting Power Management Options

You can set power management options to allow the operating system to turn off the controller to save power or to allow the controller to wake up the computer. If the device is busy doing something (servicing a call, for example) however, the operating system will not shut down the device. The operating system attempts to shut down every possible device only when the computer attempts to go into hibernation. To have the controller stay on at all times, do not click the Allow the computer to turn off the device to save power check box.

NOTE: Power management options are not available on blade servers.

NOTES:


Back to Contents Page