Installing the Driver Software
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
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:
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
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"
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
- or -
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:
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.
copype.cmd <arch> <destination>
For example: copype x86 c:\VistaPEx86
NOTE: The directory structure c:\VistaPEx86 is used throughout this procedure.
imagex /mountrw c:\VistaPEx86\winpe.wim 1 c:\VistaPEx86\mount
peimg /inf=c:\Drivers\x32\b06nd.inf c:\VistaPEx86\mount\windows
AIK inserts the driver into the WinPE 2.0 image.
peimg /prep c:\VistaPEx86\mount\windows
yes
imagex /unmount c:\VistaPEx86\mount /commit
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.
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.
Dism /image:<path_to_image> /Add-Driver /Driver:c:\winpe_x86\mount\Windows\driver.inf
dism /unmount-wim /Mountdir:c:\winpe_x86\mount /commit
To create a bootable CD-ROM
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
[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).
Options for copper interfaces:
Options for fiber interfaces:
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"
To view or change the properties of the Broadcom network adapter
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:
CAUTION! Do not select Allow the computer to turn off the device to save power for any adapter that is a member of a team.