Ethernet NIC Driver Support

Broadcom supplies Ethernet controllers to the computer industry's leading PC OEMs and add-in card manufacturers. Broadcom offers the below reference drivers as a courtesy to end users. The functionality of the reference drivers provided below may differ from the current drivers installed on the target system. Additionally, since we do not sell products directly to end-users, we do not offer comprehensive support for Broadcom's customers' products. If you are having a problem with a Broadcom-based Ethernet controller product, please contact either the PC or board manufacturer for technical support.

Driver Support Request

Broadcom offers support for Broadcom NetLink Ethernet Network adapters and Broadcom NetXtreme I Ethernet Network adapters products. Please review the FAQ's before submitting driver support request.

Determining the Correct Driver for Broadcom Ethernet Products

Device Manager provides information about how a computer'shardware is installed and configured, and how the hardwareinteracts with your computer's programs. Device Manager can beused to update the device drivers for the hardware installed onyour computer, modify hardware settings, and troubleshootproblems.

Note: To perform this task, the user may be required tobe logged on as an administrator or a member of the Administrator'sgroup.

To obtain the device ID of the Ethernet controller installed onyour computer, complete these steps:

1. Open Device Manager.
  • Click Start, and then click Control Panel
  • Double-click System
  • On the Hardware tab, click Device Manager
Ethernet NIC Driver Support Image1
2. Click Network Adapters to expand the networklist of network devices installed on your computer
3. Right-click Broadcom NetXtreme 57xxGigabitController, and then click Properties

Ethernet NIC Driver Support Image2
4. Click the Details tab

Ethernet NIC Driver Support Image4

On the details tab, a line similar to the following is displayed:

PCI\VEN_14E&DEV_1673&SUBSYS_01F91028&REV_02\4&1E93A591&0&00E5

Where: 14E4 identifies the controller as aBroadcom device. DEV_XXXX is the device ID.


Ethernet NIC Driver Support Image5
 5. After obtaining the device ID, use Table 1 toidentify the associated Broadcom part

 

BROADCOM ETHERNET CONTROLLER DEVICE IDS

Table 1 lists the device IDs for Broadcom NetXtreme, NetXtremeII, and NetLink based Ethernet products and their associatedBroadcom part numbers.

Note: To go directly to download driver support page foryour Broadcom Ethernet controller product, click on the device IDhyperlink below.

 Table 1: Broadcom Ethernet Controller Device ID
Device ID Part # Model
1600 BCM5752 NetXtreme Desktop/Mobile
1601 BCM5752M NetXtreme Desktop/Mobile
160a BCM5761E NetXtreme Desktop/Mobile
1643 BCM5725 NetXtreme Server
1644 BCM5700 NetXtreme Server
1645 BCM5701 NetXtreme Server
1645 BCM5701S NetXtreme Server
1646 BCM5702 NetXtreme Desktop/Mobile
1647 BCM5703 NetXtreme Server
1648 BCM5704 NetXtreme Server
1653 BCM5705 NetXtreme Desktop/Mobile
1654 BCM5705 NetXtreme Desktop/Mobile
1655 BCM5717 NetXtreme Server
1656 BCM5718 NetXtreme Server
1657 BCM5719 NetXtreme Server
1659 BCM5721 NetXtreme Server
165a BCM5722 NetXtreme Server
165b BCM5723 NetXtreme Server
165d BCM5705M NetXtreme Desktop/Mobile
165e BCM5705M NetXtreme Desktop/Mobile
165f BCM5720 NetXtreme Server
1665 BCM5717 NetXtreme Server
1668 BCM5714 NetXtreme Server
1669 BCM5714S NetXtreme Server
166a BCM5780 NetXtreme Server
166b BCM5780S NetXtreme Server
1672 BCM5754M NetXtreme Desktop/Mobile
1673 BCM5755M NetXtreme Desktop/Mobile
1674 BCM5756ME NetXtreme Desktop/Mobile
1677 BCM5751 NetXtreme Desktop/Mobile
1678 BCM5715 NetXtreme Server
1679 BCM5715S NetXtreme Server
167a BCM5754 NetXtreme Desktop/Mobile
167b BCM5755 NetXtreme Desktop/Mobile
167d BCM5751M NetXtreme Desktop/Mobile
167e BCM5751F NetLink
167f BCM5787F NetLink
1680 BCM5761E NetXtreme Desktop/Mobile
1681 BCM5761 NetXtreme Desktop/Mobile
1684 BCM5764 NetXtreme Desktop/Mobile
1690 BCM57760 NetXtreme Desktop/Mobile
1692 BCM57780 NetLink
1693 BCM5787M NetLink
1694 BCM57790 NetLink
1694 BCM5785 NetLink
1696 BCM5782 NetXtreme Desktop/Mobile
1698 BCM5784M NetLink
1699 BCM5785 NetLink
169a BCM5786 NetLink
169b BCM5787 NetLink
169c BCM5788 NetLink
16a7 BCM5703S NetXtreme Server
16a8 BCM5704S NetXtreme Server
16b0 BCM57761 NetXtreme Desktop/Mobile
16b1 BCM57781 NetLink
16b2 BCM57791 NetLink
16b4 BCM57765 NetXtreme Desktop/Mobile
16b5 BCM57785 NetLink
16b6 BCM57795 NetLink
16c7 BCM5703 NetXtreme Server
16dd BCM5781 NetLink
16f3 BCM5727 NetXtreme Server
16f7 BCM5753 NetXtreme Desktop/Mobile
16fd BCM5753M NetXtreme Desktop/Mobile
16fe BCM5753F NetXtreme Desktop/Mobile
16ff BCM5903M NetLink
1701 BCM4401 NetLink (10/100)
170c BCM4401 NetLink (10/100)
170d BCM5901 NetLink
170e BCM5901 NetLink
170f BCM5903F NetLink
1712 BCM5906 NetLink
1713 BCM5906M NetLink

Determing Chipset and Driver Information

 

 

Chipset Information

To determine the Ethernet controller used in your PC, please select your OS below for instructions on how to determine the type of controller used:
You can also determine your type of Ethernet controller by looking at your Network Interface Card (NIC) or LAN On-board chip to obtain the Broadcom chipset number. The chip should be marked BCM57xx or BCM44xx.

If you cannot determine the Broadcom controller being used, please select the "Unknown" option corresponding to the speed of your device.

Linux
  • At the shell prompt, type lspci >lspci.log
  • On-board 8051 processor and RAM/ROM memory
  • If the BCM44xx or BCM57xx driver is loaded, attach/proc/net/nicinfo/eth*.info file(s)
MS-DOS
  • At the command prompt, type b57udiag -cmd
  • The chipset information will be displayed in the first column
SCO
  • Install the respective driver per documentation
  • At the shell prompt, type grep BCM/var/adm/messages
  • The chipset information will be displayed as or "chip=BCM57xx"for copper or "chip=BCM57xxS" for fiber
Solaris
  • Install the respective driver package per documentation
  • At the command prompt, type kstat -m bcme | grepmacDeviceType
  • The chipset information will be displayed on the screen
Unixware
  • Install the respective driver per documentation
  • At the shell prompt, type grep BCM/var/adm/messages
  • The chipset information will be displayed as or "chip=BCM57xx"for copper or "chip=BCM57xxS" for fiber
Windows
  • Start the Broadcom Advanced Control Suite
    Note: Double-click on the "Broadcom Control Suite" icon inthe Control Panel (or Other Control Panel Options for Windows XP)
  • The chipset information (e.g., BCM5705) will be displayed in theASIC/Firmware Version field

 

Driver Information

To determine the driver version used in your PC, please select your OS belowfor instructions:

Linux
  • At the command prompt type insmod bcm5700or insmod bcm4400 depending on your chipset
  • At the command prompt enter grep -i version /proc/net/nicinfo/eth*.info
MS-DOS
  • At the command prompt, type b57udiag -cmd
  • The driver version information will be displayed
Netware
  • Install the respective driver per documentation
  • At the prompt type config
  • The driver version information will be displayed
SCO
  • Install the respective driver per documentation
  • At the shell prompt type custome
  • The driver version information will be displayed
Solaris
  • Install the respective driver package per documentation
  • At the command prompt, type modinfo | grep bcme
  • The driver version will be displayed on the screen
Unixware
  • Install the respective driver per documentation
  • At the shell prompt type pkginfo -l
  • Search for bcme software
  • The driver version information will be displayed
Windows
  • Start the Broadcom Advanced Control Suite
    Note: Double-click on the "Broadcom Control Suite" icon inthe Control Panel (or Other Control Panel Options for Windows XP)
  • The driver information (e.g., 57xp32.sys v5.30) will be displayed in the Driver Name / Version field
 

Ethernet NIC FAQs

 

 

Here you will find common questions regarding Broadcom's Ethernet NIC products and drivers.

 Where can I download drivers for the NetXtreme II product line?

Drivers and documentation for NetXtreme II can be obtained from QLogic

 Where can I find the user manual for my NIC?
 What are the differences between Broadcom NIC brands?
  • Broadcom NetXtreme II 1G Copper Adapter: Links at 10 Mb, 100 Mb, and 1000 Mb.
  • Broadcom NetXtreme Copper Adapter: Links at 10 Mb, 100 Mb, and 1000 Mb.
  • Broadcom NetXtreme Fiber-Optic Adapter: Only links at 1000 Mb.
  • Broadcom NetLink 57XX: 1G Copper Adapter: Links at 10 Mb, 100 Mb, and 1,000 Mb.
  • Broadcom NetLink 440X 10/100 Integrated Controller: Only links at 10 Mb and 100 Mb.
 What are the Linux tg3, bnx2, bnx2x and b44 drivers?

To better support users, Broadcom has been actively supporting, maintaining, and testing the in-kernel Linux drivers for the NetXtreme, NetXtreme II, NetLink and 4401 product lines. The following is list of drivers supported for each product line:

  • NetXtreme and NetLink - tg3
  • 4401 - b44

Broadcom officially releases the Linux drivers as packages. The Linux driver packages released by Broadcom are based on the latest in-kernel drivers with some added compatibility code to make it backwards compatible with most 2.6 kernels and some 2.4 kernels (generally newer than 2.4.24). If you are using the latest upstream kernel from www.kernel.org, you generally do not need to download the Linux driver packages from Broadcom as the latest upstream kernel has the latest Linux driver patches.

For the NetXtreme and NetLink product lines, the tg3 driver is now the only Linux driver that Broadcom supports. Accordingly, Broadcom has discontinued support for the bcm5700 driver and no longer provides updates.

 Will a 32-bit desktop adapter work on a 64-bit PCI slot?

Yes.

 Will a 64-bit server adapter work on a 32-bit PCI slot?

Yes.

 What if there is an IRQ/IO conflict on my system?

Go into the BIOS and assign another IRQ for your adapter. Make sure it's not sharing an IRQ with another device.

 After I install my network card, I cannot browse the network. What should I do?
  1. Check your IP address and IP Mask (please refer to documentation for respective OS).
  2. Ping your default gateway.
  3. Ping another client on the same subnet connected to the same switch or HUB.
  4. Ping the switch's management IP address if it is on the same subnet as yours.
  5. Refer to the troubleshooting section of the user manual.
 How can I force the speed on the adapter?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and click Properties.
  2. Click the Configure button and then the General tab.
  3. Set the speed to 10 Mb Full, 10 Mb Half, 100 Mb Full, 100 Mb Half, or Auto.

: Adapter speed is forced by adding "Speed=XXXX" parameter to driver load command line in the AUTOEXEC.NCF file, where XXXX are 10 HD, 10 FD, 100 HD or 100 FD.

: See heading: "How do I force speed and duplex under Linux?"

 What is 802.1p QOS?

The "802.1p QOS" parameter is a standard that enables Quality of Service (QoS). It is responsible for the QoS provisions on the local segment, and the avoidance of the "all packets are treated equally" issue, which falls onto the hub or switch servicing segment. 802.1p QOS provides prioritization of packets traversing a subnet.

 How can I configure 802.1p QOS?
  1. In Microsoft Windows, right-click the Network Adapter in "Network Connections" and click Properties.
  2. Click the Configure button and then the General tab.
  3. Set the "802.1p QOS" parameter to Enable or Disable.
 What is Checksum Offload?

Normally the TCP Checksum is computed by the protocol stack. By selecting one of the "Checksum Offload" parameters, the checksum can be computed by the Gigabit Ethernet Adapter.

 How can I configure Checksum Offload?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. For IPv4, set the TCP/UDP Checksum Offload (IPv4) parameter to Disable, Rx & TX Enabled, Rx Enabled or Tx Enabled.
  4. For IPv6, set the TCP/UDP Checksum Offload (IPv6) parameter to Disable, Rx & TX Enabled, Rx Enabled or Tx Enabled.

: Checksum Offload is configured by adding the "CHECKSUM=ON" parameter to the driver load command line in the AUTOEXEC.NCF file. To disable, change the value to OFF or do not include the parameter, since the default is set to disable.

: This can be done using the "ethtool -K <device> <parameter>" command. Run the following to view the current settings on a device: "sudo /sbin/ethtool -k <device>"

 What is Ethernet@WireSpeed?

"Ethernet@WireSpeed" is a parameter that enables a 1000BASE-T Ethernet adapter to establish a link at a lower speed when only two pairs of wires are available in the cable plant.

 How can I enable or disable Ethernet@WireSpeed?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and, then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. Set the "Ethernet@WireSpeed" parameter to Enabled or Disabled.

In Linux, SCO, Unixware and Solaris operating systems this feature is always enabled on supported Broadcom adapters.

 What is Flow Control?

"Flow Control" is a parameter that allows the user to enable or disable the receipt or transmission of PAUSE frames. PAUSE frames enable the adapter and the switch to control the transmit rate. The side that is receiving the PAUSE frame temporarily stops transmitting.

 How can I configure Flow Control?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. Set the "Flow Control" parameter to Auto, Disable, Rx & Tx Enabled, Rx Enabled, or Tx Enabled.

: Flow Control is configured by adding either the "TxFlow=ON" or "RxFlow=ON" (transmit and receive respectively) parameter to the driver load command line in the AUTOEXEC.NCF file. Both transmit and receive can be enabled concurrently. To disable, change the value to OFF or do not include the parameter, since the default is set to disable.

: The can be done using the "ethtool -A" command. Please refer to the respective man page for command syntax.

 What is Jumbo MTU?

"Jumbo MTU" is a parameter that allows the adapter to transmit and receive oversized Ethernet frames that are greater than 1514 bytes but less than 9000 bytes in length. Note that this parameter requires a switch that is able to process large frames.

 How can I configure Jumbo MTU?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections, and then click Properties.
  2. Click the Configure button and then the Advanced tab. Jumbo MTU is set at 1500 bytes by default. To increase the size of the received frames, increase the byte quantity in 500-byte increments up to 9000 bytes.

: Jumbo Frame is configured by adding the "Jumbo=XXXX" parameter to the driver load command line in the AUTOEXEC.NCF file, where XXXX is a value between 1514 and 9000 bytes.

: The MTU can be changed on the device that supports this feature using the following command: "ifconfig <device> mtu <MTU Size>". <Value> can be between 1500 and 9000, <device> is the ethernet device. You can also use "ip" to set the MTU: ex: ip link set <device> mtu <MTU Size>"

NOTE: Please note that not all Broadcom networking devices support Jumbo-Frame. Please consult the respective product documentation to confirm that your device supports this feature.

 What is Large Send Offload?

Normally the TCP segmentation is done by the protocol stack. By enabling the Large Send Offload value, the TCP segmentation can be done by the Gigabit Ethernet Adapter.

 How can I configure Large Send Offload?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. Set the "Large Send Offload" parameter to Disable or Enable.
 What is Network Address?

Network Address is a user-defined address that is used in place of the MAC address that was originally assigned to the adapter. Every adapter in the network must have its own unique MAC address. This locally administered address consists of a 12-digit hexadecimal number.

 How can I define my own MAC address on my adapter?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. Configure the "Network Address" parameter by assigning a unique node address for the adapter.

: The Mac Address is configured by the adding Node=XXXXXXXXXXXX parameter to driver load command line in the AUTOEXEC.NCF file, where XXXXXXXXXXXX is the Locally Administered address.

: Virtual MAC addresses can be set using "ifconfig" hardware Ethernet address option. ex: "sudo ifconfig <device> hw ether <xx:xx:xx:xx:xx:xx" or "sudo ip link set <device> address <xx:xx:xx:xx:xx:xx<"

 What is the "Wake Up Capabilities" parameter?

The "Wake Up Capabilities" parameter allows the user to set the adapter to wake up from a low power mode when it receives a network wake up frame. There are two wake up frames: Magic Packet and IP frame.

 How can I set the Wake Up capabilities?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. Set the "Wake Up Capabilities" parameter to Both, Magic Packet, None, or Wake Up Frame.

: Only supports DOS WOL and is configured by adding "MagicP=1" parameter to driver load command line in the AUTOEXEC.NCF file. To disable, change value to "0" or do not include parameter, since default is set to disable.

: The can be done using the "ethtool -s" command. First determine if the device supports Wake on LAN (WoL): To display WoL support and current setting:: "sudo ethtool <device> If the device supports WoL, ethtool will report "g" ex: "Supports Wake-on: g". If the device doesn't supports WoL, ethtool will report "d" flag ex: "Supports Wake-on: d". If the device supports WoL and WoL is already enabled; ethtool will report "g" flag ex:Wake-on: g" If the device supports WoL and the WoL flag is not set to "g", the user can enable WoL using the settings command; ex: ethtool -s <device> wol g

 What is the WOL (Wake-On-LAN) Speed?

"WOL Speed" is a parameter that allows the user to select the speed at which the adapter connects to the network during Wake-on-LAN mode.

 How can I set the speed on WOL (Wake-On-LAN)?
  1. In Microsoft Windows, right-click the Network Adapter in Network Connections and then click Properties.
  2. Click the Configure button and then the Advanced tab.
  3. Set the "WOL Speed" parameter to Lowest Speed Advertised, 10 Mb, 100 Mb, or Auto.

In Linux, the feature is not supported. The interface will automatically link at the lowest speed supported by your switch.

 What is PXE?

PXE (Preboot Execution Environment) is a software module that allows your networked computer to boot with the images provided by remote servers across the network.

 How do I force speed and duplex under Linux?

To set forced 100 Mb/s full duplex:

Use ethtool settings options

ethtool -s <device> speed 100 duplex full autoneg off

For the setting to be persistent across reboots edit "/etc/udev/rules.d/71-ethtool.rules"ff and add "SUBSYSTEM=="net", ACTION=="add", NAME=="<device>", RUN+="/sbin/ethtool <device> -s speed 100 duplex full autoneg off"

 Why is there no option to force the speed and duplex to 1000Mb/s - Full Duplex?

Per the IEEE standard, the only IEEE compliant way to operate at 1000Mb/s-Full duplex is through auto-negotiation. If the network switch being used is IEEE compliant, the link speed will auto-negotiate to 1000Mb/s-Full duplex when autoneg is selected.

 Large Send Offload (LSO) stopped working since updating the 32-bit Windows XP operating system to Service Pack 2.

Microsoft's implementation of the Windows Firewall feature included in Service Pack 2 appears to cause Large Send Offload (LSO) to stop working correctly. They provide the solution to this problem in Knowledge Base article 842264. If the problem persists, you may need to run the latest Windows update in order for this feature to begin working again. Specifically, the security update available at the following link should re-activate the LSO capability of our adapter: Microsoft security update.

 The following message is received when attempting to deploy a RIPREP image through Remote Installation Services (RIS): " The operating system image you selected does not contain the necessary drivers for your network adapter. Try selecting a different operating system image. If the problem persists, contact your administrator. Setup cannot continue. Press any key to exit."

This problem is not isolated to the Broadcom adapter. However, based on several inquiries, we list the following instructions based on other customers successfully working around this issue:

  1. Place the Broadcom driver files in the original image folder (the image folder created when risetup.exe was executed for the first time).
    Example: i:\RemoteInstall\Setup\English\Images\(Original Image)
  2. Place the Broadcom driver files in the i386 subfolder under the original image folder
    Example: i:\RemoteInstall\Setup\English\Images\(Original Image)\i386
  3. Place the Broadcom driver files for the network adapter in the RIPREP Image folder.
    Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)
  4. Place the Broadcom adapter drivers in the i386 subfolder where the RIPREP Image is located.
    Example: i:\RemoteInstall\Setup\English\Images\(RIPREP Image)\i386

    The Microsoft Knowledge base articles listed below were used as a reference for the following instructions:

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;254078
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;246184
     
  5. Create the following path and place all Broadcom driver files in ..\(RIPREP Image)\$oem$$1\Drivers\network
  6. Edit the riprep.sif file located in ..\(RIPREP Image)\i386\Template to include the following information under the [Unattend] section:
    OemPreinstall = yes
    OemPnPDriversPath = "Drivers\network"
    DriverSigningPolicy = Ignore
  7. Create the following path and place all Broadcom driver files in ..\(Original Image)\$oem$\$1\Drivers\nic
  8. Edit the ristndrd.sif file located in ..\(Original Image)\i386\templates to include the following information under the [Unattend] section:
    OemPreinstall = yes
    OemPnPDriversPath = "Drivers\nic"
    DriverSigningPolicy = Ignore
  9. Restart the Remote Installation service. This can be performed from a command line with the following commands:
    net stop binlsvc
    net start binlsvc
 What is iSCSI Boot?

iSCSI boot allows a Windows or Linux operating system boot from an iSCSI target machine located remotely over a standard IP network. For both Windows and Linux operating systems, iSCSI boot can be configured to boot with two distinctive paths: non-offload (also known as Microsoft initiator) and offload (Broadcom's offload iSCSI driver or HBA). Configuration of the path is set with the HBA Boot Mode option located on the General Parameters screen of the iSCSI Configuration utility.

 What operating systems are supported with iSCSI Boot?

The Broadcom NetXtreme II Gigabit Ethernet adapters support iSCSI boot on the following operating systems:

  • Windows Server 2008 32-bit and 64-bit (supports offload and non-offload paths)
  • Windows Server 2008 R2 64-bit (supports offload and non-offload paths)
  • Linux RHEL 5.5 and later, SLES 11.1 and later (supports offload and non-offload paths)
  • SLES 10.x and SLES 11 (only supports non-offload path)
 What are the steps required for iSCSI Boot setup?

The iSCSI boot setup consists of:

  • Configuring the iSCSI Target
  • Configuring iSCSI Boot Parameters
  • Preparing the iSCSI Boot Image
  • Booting

For detailed instructions on each step, see the iSCSI Boot User guide.

 Why does the Xen hypervisor not start when booting from an iSCSI Boot image created with RHEL 5.4 Xen kernel and later?

This is a known third-party issue. To work around this issue, disable the Xen hypervisor's EDD feature by editing the grub.conf file in the boot/grub folder to add the edd=off switch to the end of the kernel line. For example, kernel /xen.gz edd=off..

Broadcom OEM customers often enable unique network related feature sets that are specific to their server platforms. These features are not always supported in the generic Broadcom network drivers found at this web site. Therefore, it is highly recommended that you download the driver/install package from the OEM brand website for your LAN On Motherboard (LOM) network adapter or OEM branded Network Interface Card.

 How do I troubleshoot when my system is not detecting the adapter?
  1. Make sure the adapter is not defective either by visually inspecting it or by using an adapter diagnostic program.
  2. Check your cabling system and its connectivity; check the link LED on the adapter and/or on the switch.
  3. Ensure the adapter is placed properly into the PCI/PCIe slot.
  4. Move the adapter into a different PCI/PCIe slot.
  5. Inspect the driver configuration; please refer to the user manual for instruction.
  6. In Linux issue command lspci to check if your adapter is listed
 How can I identify the correct driver for my NIC Device?
 How do I uninstall the driver for Windows?
  1. Open Control Panel. Click on Add/Remove Programs or Programs and Features
  2. For Windows XP/2003 choose add/remove programs. Click on Broadcom Drivers and then click remove
  3. For Windows Vista/2008, Windows 7/2008R2 choose Program and Features. Click on Broadcom Drivers and then click Uninstall
  4. Uninstalling the driver from Device Manager is not recommended and may lead to incomplete removal of the device
 How do I manually remove the NetXtreme drivers from Windows?
  1. Boot to WinPE command line environment - either the startup repair or by using a Boot USB or CD or DVD
  2. Change to the drive that contains the windows directories
  3. In the root, delete all instances on that drive (the "/S") of the applicable Broadcom driver files by typing the following:
    1. "del /S bxnd*.*" for the NetXtreme II 1G/10G NDIS drivers
    2. "del /S evbd*.*" for the NetXtreme II 10G VBD drivers
    3. "del /S bxvbd*.*" for the NetXtreme II 1G VBD drivers
    4. "del /S bxfcoe*.*" for the NetXtreme II 1G/10G FCoE storage drivers
    5. "del /S bxois*.*" for the NetXtreme II 1G/10G iSCSI storage drivers
    6. "del /S b06nd*.*" for the NetXtreme II 1G WinPE Monolithic drivers
    7. "del /S evnd*.*" for the NetXtreme II 10G WinPE Monolithic drivers
    8. "del /S b57nd*.*" for the NetXtreme I 1G drivers

    Note that the b06nd and evnd driver files should not be present. These driver files are ONLY used by older WinPE's pre-boot versions (2.2 and earlier) to enable the applicable ethernet device before the OS is installed.

  4. Change to the ...\windows\inf\ directory
  5. Find all "oem*.inf" files with "14e4" devices in them by using the 'find /I /C "14e4" x:\windows\inf\oem*.inf' command
  6. Delete those OEM INF files by typing "del oemNN.*" where "NN" is the applicable file's number
  7. Reboot the host system and now you can "uninstall" or "update" the device without the OS automatically reloading a driver
 How do I upgrade the driver for Windows?
  1. Run the latest Broadcom Driver Installation Software
  2. For the NetXtreme II product line, upgrading the driver from Device Manager is not recommended since these devices use a 'split driver' model consisting of a virtual bus driver (VBD), NDIS driver, and in some cases an iSCSI HBA driver. All three of these must be installed in the proper order and the Driver Installation Software does this.
 How do I install the driver for Windows?
  1. Run the latest Broadcom Driver Installation Software
  2. Installing the driver from Device Manager is not recommended on the NetXtreme II product line, since these devices use a 'split driver' model consisting of a virtual bus driver (VBD), NDIS driver, and in some cases an iSCSI HBA driver. All three of these must be installed in the proper order and the Driver Installation Software does this.
 How do I manually change to a special Debug or Bug Fix driver for Windows?

The following are the steps to manually change a Broadcom NetXtreme II driver on Windows Server 2008 R2. This procedure should be similar on other versions of Windows and all versions of the NetXtreme II 1Gb/s and 10Gb/s devices.

In a normal MS Windows device driver installation, you should always use the NetXtreme II "Umbrella" driver installer software utility to load the correct combinations of MS WHQL signed drivers, but if installing a special bug fix build or debug check build of the drivers you would follow these procedures. The NetXtreme II "split" driver model has a network adapter NDIS driver ("bxnd" for both 1G and 10G devices), iSCSI storage driver ("bxois" for both 1Gb/s and 10Gb/s devices) and FCoE storage driver ("bxfcoe" for both 1Gb/s and 10Gb/s devices) all stacked on top of the virtual bus driver ("bxvbd" for 1Gb/s devices and "evbd" for 10Gb/s devices). These drivers need to be installed in the correct order for proper device functionality.

Note that there are single or monolithic NetXtreme II drivers ("b06nd" for 1Gb/s devices and "evnd" for 10Gb/s devices) that are used exclusively in Windows Vista/Server 2008 (pre-R2) and earlier WinPE versions - they are not used by the OS. They provide simple network functionality only for earlier versions of WinPE's pre-OS DOS like boot mode. Furthermore these single drivers are no longer needed for Windows Server 2008 R2's WinPE version which now uses the split drivers.

  1. Open Windows Device Manager go to the Systems Devices instance of the Broadcom NetXtreme II Virtual Bus Driver (VBD) you wish to change and right click and select "Update Driver Software...". If no driver is currently loaded, you will only see network devices in the Other Devices subsection, update these as if they were the VBD system device and the other devices will enumerate after the VBD driver is loaded.
  2. In the next "Update Driver Software" window, select "Browse my computer for driver software".
  3. In the next window, select "Let me pick from a list of device drivers on my computer". Do not select "Browse" at this point since that may not allow the desired driver to be loaded. This is true for all the following steps - you should use the "HAVE DISK" method when you need to install a specific driver set.
  4. In the next window, select the "Have Disk?" button.
  5. In the "Install from Disk" window, now select the "Browse..." button.
  6. Browse to the desired INF file - "bxvbd" (for 1G devices) or "evbd" (for 10G devices) - then select "Open".
  7. Back in the "Install from Disk" window select "OK".
  8. Back in the "Update Driver Software" window select "Next".
  9. You may see a "Windows Security" message if this is an unsigned driver. Normally this window should not appear, but in this example, the driver is a check build debug version. Select "Install" to continue.
  10. You should now see a "Windows has successfully updated your drive software" message, select the "Close" button.
  11. Repeat steps 1-10 for all other 1Gb/s and 10Gb/s NetXtreme II system devices on your host system, before proceeding to step 12.
  12. Back in the Windows Device Manager, right click the Network Adapter instance of the device you need to change and select "Update Driver Software...".
  13. As with the VBD, select "Browse my computer for driver software" in the "Update Driver Software" window.
  14. Again, select "Let me pick from a list of device drivers on my computer".
  15. Again, select the "Have Disk" button.
  16. Now select the "Browse" button.
  17. Browse to the desired NDIS INF file ("bxnd") then select the "Open" button.
  18. Now select the "OK" button in the next window.
  19. In the next window select the "Next" button.
  20. You may see a "Windows Security" message if this is an unsigned driver. Select "Install this driver software anyway" to continue.
  21. You should now see the "Windows has successfully updated your drive software" message, select the "Close" button.
  22. Repeat steps 12-21 for all the other 1Gb/s and 10Gb/s Network Adapter devices on this host system.
  23. Repeat steps 12-21 for any other enumerated/licensed Storage Controller devices (such as iSCSI or FCoE) you need to change that are related to the previously changed devices.
  24. You may need to reboot your system for all of these driver changes to take effect. This can be done after all driver changes have been made.

NOTE: All NetXtreme II 1Gb/s and 10Gb/s devices on the h