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.

    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

    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

     

Currently Viewing:

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?
What are the Linux tg3, bnx2, bnx2x and b44 drivers?
Will a 32-bit desktop adapter work on a 64-bit PCI slot?
Will a 64-bit server adapter work on a 32-bit PCI slot?
What if there is an IRQ/IO conflict on my system?
After I install my network card, I cannot browse the network. What should I do?
How can I force the speed on the adapter?
What is 802.1p QOS?
How can I configure 802.1p QOS?
What is Checksum Offload?
How can I configure Checksum Offload?
What is Ethernet@WireSpeed?
How can I enable or disable Ethernet@WireSpeed?
What is Flow Control?
How can I configure Flow Control?
What is Jumbo MTU?
How can I configure Jumbo MTU?
What is Large Send Offload?
How can I configure Large Send Offload?
What is Network Address?
How can I define my own MAC address on my adapter?
What is the "Wake Up Capabilities" parameter?
How can I set the Wake Up capabilities?
What is the WOL (Wake-On-LAN) Speed?
How can I set the speed on WOL (Wake-On-LAN)?
What is PXE?
How do I force speed and duplex under Linux?
Why is there no option to force the speed and duplex to 1000Mb/s - Full Duplex?
Large Send Offload (LSO) stopped working since updating the 32-bit Windows XP operating system to Service Pack 2.
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."
What is iSCSI Boot?
What operating systems are supported with iSCSI Boot?
What are the steps required for iSCSI Boot setup?
Why does the Xen hypervisor not start when booting from an iSCSI Boot image created with RHEL 5.4 Xen kernel and later?

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 1Gbps and 10Gbps 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 1Gbps and 10Gbps devices) and FCoE storage driver ("bxfcoe" for both 1Gbps and 10Gbps devices) all stacked on top of the virtual bus driver ("bxvbd" for 1Gbps devices and "evbd" for 10Gbps 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 1Gbps devices and "evnd" for 10Gbps 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 1Gbps and 10Gbps 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 1Gbps and 10Gbps 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 1Gbps and 10Gbps devices on the host system will use the same common NDIS/iSCSI/FCoE drivers. All 1Gbps devices will use the same "bxvbd" driver and all 10Gbps devices will use the same "evbd" driver. You should not have the 1Gbps devices use the previous NDIS driver when changing the 10Gbps devices to a new set of drivers. All NetXtreme II devices should be updated to the same/compatible driver versions at the same time. In the above example, if a BCM57711 10Gbps devices was also installed on the same host system as the BCM5709 1Gbps device, it's VBD driver would need to be changed right after changing the BCM5709's in step 12, and it's applicable NDIS/iSCSI/FCoE drivers would need to also be changed in steps 22 and 23. This is because the NDIS, iSCSI and FCoE are common to all NetXtreme II devices on the host system, and one device should not use an "incompatible" common driver with a specific VBD driver.

NOTE: In some cases, the previous drivers may need to be totally removed from the host system before installing a debug driver. See the previous steps for manually removing a driver.

How do I install NDIS2 drivers to connect my DOS client to Microsoft Windows servers?

Requirements:

  1. Microsoft Network Client version 3.0 for MS-DOS from Windows NT Server 4.0 installation CD.
  2. Blank MS-DOS bootable 3.5" High Density floppy disk.
  3. Broadcom NDIS2 driver. (B57.dos or B44.dos)

Windows NT 3.51/4.0 Server users:

  1. When using the "Network Client Administrator" tool available in Windows NT, simply choose
    any other network card from the list (NE2000 Compatible for example) to create the diskette.
  2. After creating the diskette, follow the instructions below under "Modifying boot diskette for Broadcom network card".

Windows 2000/XP users:

Method 1: Running "Network Client Administrator" tool from Windows 2000/XP:

  1. Create a folder called "NCADMIN" in the root of the C: drive.
  2. Copy NCADMIN.CN_, NCADMIN.EX_, and NCADMIN.HL_ from the I386 folder on the Windows NT Server 4.0 cd.
  3. Open a command prompt window and change directory to C:\NCADMIN.
  4. Type expand -r ncadmin.* and press enter.
  5. Close the command prompt window.
  6. Start Windows Explorer
  7. Open the NCADMIN folder and double-click NCADMIN.EXE.
  8. Follow the instructions to make the network startup disk. (Choose "NE2000 Compatible" when selecting the network adapter.)
  9. After creating the diskette/USB flash drive, follow the instructions below under "Modifying boot diskette/USB flash drive for Broadcom network card".

Method 2: Running Microsoft Network Client version 3.0 for MS-DOS setup from a DOS prompt:

  1. Copy the NETSETUP directory from the Windows NT Server 4.0 CD located under <cd-rom drive letter>:\clients
  2. Open a command prompt window.
  3. From the "C:" prompt type cd \NETSETUP and press the ENTER key.
  4. Type setup and press the ENTER key.
  5. Press the ENTER key to continue.
  6. Accept the default installation path of "C:\NET" by pressing the ENTER key.
  7. Use the down arrow to scroll down the network adapter list and highlight "NE2000 Compatible". Press ENTER.
  8. Accept "Network Buffer" defaults by pressing ENTER.
  9. Enter a user name that is valid on the Windows system to which you will be attaching. Press ENTER.
  10. On the next screen arrow up to "Change Setup Options" and press ENTER.
  11. Arrow up to "Change Redir Options" and press ENTER.
  12. Arrow up to "Use the Basic Redirector" and press ENTER.
  13. Press ENTER on the next screen. ("The listed options are correct" will be highlighted.)
  14. Arrow up to "Change Network Configuration" and press ENTER.
  15. Choose and configure the desired protocols from this screen.
  16. Once the protocols are configured, select "Network configuration is correct" and press ENTER.
  17. Press ENTER again. ("The listed options are correct" should be highlighted.)
  18. The configuration files will then be copied to C:\NET. Press ENTER to exit setup.
  19. Start "Windows Explorer" and view the contents of the C:\NET directory.
  20. Delete any of the following files that exist to insure the directory will fit on the floppy disk/USB flash drive: ADDNAME.EXE, EXPAND.EXE, IPCONFIG.EXE, NE2000.DOS, PING.EXE, WIN_SOCK.DLL, WINSOCK.DLL, WSOCKETS.DLL, VSOCKETS.386, VBAPI.386, SETUP.EXE, SOCKETS.EXE
  21. Copy C:\NET to a bootable floppy/USB flash drive.

Modifying boot diskette/USB flash drive for Broadcom network card:

Note: for BCM4401 use "B44" in place of "B57" in the following examples.

  1. Edit A:\NET\PROTOCOL.INI with Notepad or similar text editor.
    • Change "DriverName=<current value>$" to "DriverName=B57$"
    • Remove all other parameter entries under the [MS$NE2CLONE] or equivalent section such as "IOBASE=0x300" or "INTERRUPT=3", etc.

    Example Protocol.ini for IP:

    [network.setup] version=0x3110 netcard=ms$ne2clone,1,MS$NE2CLONE,1 transport=tcpip,TCPIP lana0=ms$ne2clone,1,tcpip [MS$NE2CLONE] DriverName=B57$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [tcpip] NBSessions=6 DefaultGateway=0 ; SubNetMask=255 0 0 0 ; IPAddress=192 168 0 1 DisableDHCP=0 DriverName=TCPIP$ BINDINGS=MS$NE2CLONE LANABASE=0
    Example Protocol.ini for IPX:
    [network.setup] version=0x3110 netcard=ms$ne2clone,1,MS$NE2CLONE,1 transport=ms$ndishlp,MS$NDISHLP transport=ms$nwlink,MS$NWLINK lana0=ms$ne2clone,1,ms$nwlink lana1=ms$ne2clone,1,ms$ndishlp [MS$NE2CLONE] DriverName=B57$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=ms$ne2clone [ms$nwlink] DriverName=nwlink$ FRAME=Ethernet_802.2 BINDINGS=MS$NE2CLONE LANABASE=0
    Example Protocol.ini for NetBEUI:
    [network.setup] version=0x3110 netcard=ms$ne2clone,1,MS$NE2CLONE,1 transport=ms$ndishlp,MS$NDISHLP transport=ms$netbeui,MS$NETBEUI lana0=ms$ne2clone,1,ms$ndishlp lana1=ms$ne2clone,1,ms$netbeui [MS$NE2CLONE] DriverName=B57$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=MS$NE2CLONE [MS$NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=12 BINDINGS=MS$NE2CLONE LANABASE=0
  2. Edit A:\NET\SYSTEM.INI.
    • Change "netcard=<current value>" to "netcard=b57.dos"
    • Check for references to "C:\NET" and change "C:\NET" to "A:\NET" if necessary.
    Example SYSTEM.INI
    [network] sizworkbuf=1498 filesharing=no printsharing=no autologon=yes computername=MYPC lanroot=A:\NET username=USER1 workgroup=WORKGROUP reconnect=yes dospophotkey=N lmlogon=0 logondomain= preferredredir=basic autostart=basic maxconnections=8 [network drivers] netcard=B57.dos transport=ndishlp.sys,*netbeui devdir=A:\NET LoadRMDrivers=yes
  3. Copy B57.dos to A:\NET.
  4. Create the appropriate AUTOEXEC.BAT file in A:\ for the chosen protocol as shown below.
    • For TCP/IP: path=a:\net
      a:\net\net initialize
      a:\net\netbind.com
      a:\net\umb.com
      a:\net\tcptsr.exe
      a:\net\tinyrfc.exe
      a:\net\nmtsr.exe
      a:\net\emsbfr.exe
      a:\net\net start basic
      net use z: \\SERVERNAME\SHARENAME
    • For IPX: SET PATH=A:\NET
      A:\net\net initialize
      A:\net\nwlink
      A:\net\net START BASIC
      net use z: \\SERVERNAME\SHARENAME
    • For NetBEUI: SET PATH=A:\NET
      A:\net\net START BASIC
      net use z: \\SERVERNAME\SHARENAME
    • Create a CONFIG.SYS file in A:\ as shown below.
      files=30 device=a:\net\ifshlp.sys lastdrive=z
How do I install SCO UnixWare drivers?
  1. Run pkgadd to install the drivers. E.g., pkgadd -d <install_path>.
  2. Please follow the UnixWare user manual to configure the NIC.
How do I install SCO OpenServer 5 drivers?
  1. Copy the drivers to a temporary directory.
  2. Run custom to install the drivers.
  3. To configure the NIC, please follow the directions in the SCO OpenServer manual or the readme.txt.
How do I obtain (download) the latest driver for my device?

Determine the family and device to download the correct driver:

  1. At a command prompt Execute: sudo lspci | grep -I "broadcom"
  2. Look for "NetXtreme II" or "NetXtreme I" and "BCMXXXXX:"
    • e.g., "Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)
    • Family is: "NetXtreme II" Device is "5709"
  3. Download the driver for the matching device from the download support page
How do I install Linux driver from source?
  1. See section "How do I obtain (download) the latest driver for my device?" and after the steps have been completed and the driver has been downloaded, return to this section.
  2. Copy the driver (.linux-x.x.x.zip) into a temporary directory that the user has write permissions to.
    • e.g., cp linux-7.0.36 zip /home/usr/tmp
  3. Extract the contents of the ZIP archive
    • Execute: unzip linux-x.x.36.zip (e.g., unzip linux-7.0.36.zip)
  4. Change the working directory to where the driver source is located:
    • e.g., cd Server/Linux/Driver
  5. Untar the driver source
    • tar -xzvpf netxtremex-x.x.x.tar.gz (e.g., tar -xzvpf netxtreme2-7.0.36.tar.gz)
  6. Change the working directory to the driver source
    • e.g., cd netextreme2-7.0.36
  7. Build the new driver from source
    • Execute: make clean (if this command fails, make sure the build environment is installed)
  8. Install the driver source
    • EX:: sudo make install
  9. Remove the previously installed driver from memory (WARNING: This command will remove the driver for the network interfaces; only execute if your physically at the system)
    • EX: sudo rmmod bnx2 or bnx2x
  10. Load the newly compiled and installed driver from disk into memory
    • EX: sudo modprobe bnx2 or bnx2x
How do I install the Linux driver from RPM Source?
  1. See section "How do I obtain (download) the latest driver for my device?" and after steps have been completed and driver has been downloaded, return to this section.
  2. Refer to section "Installing Source RPM Package" in INSTALL.TXT.
How do I know which driver version was installed on a DOS 16-bit ODI client connecting to a Novell Netware server?

Type: B57.COM /s

How do I know which driver version was installed on a DOS ODI client connecting to a Novell Netware server?

Type: config

How do I know which driver version was installed in UnixWare?

Type: custom

How do I know which driver version was installed in SCO OpenServer 5?

Type: custom

How do I know which driver version is installed in Linux?

By using the module information utility (modinfo). Execute: modinfo <driver> EX: modinfo bnx2

Linux: How can I determine the driver and version a device is currently using?

By using device information option of the "ethtool" utility to display the driver version . Execute: ethtool -I <port> EX: ethtool -i eth0 driver: bnx2
version: 2.1.11

Linux: How can I determine the firmware currently programmed onto the device?

By using device information option of the "ethtool" utility to display the firmware version . Execute: ethtool -I <port> EX: ethtool -i eth0 firmware-version: 5.0.12 bc 5.0.11 NCSI 2.0.5

Linux: How can I determine the physical port of the interface?

By using port identify option of the "ethtool" utility to blink the LEDs on the specific ethernet port. Execute: fconfig <port> up && ethtool -p 20 <interface> EX: ifconfig eth0 up && ethtool -p eth0

Which utility can I use to run DOS diagnostic for my adapter?

For an NX1 device, run B57UDIAG.EXE from a machine booted to DOS. This program will not function properly in Windows.

For an NX2 device, run UEDIAG.EXE from a machine booted to DOS. This program will not function properly in Windows.

My adapter is disabled in Device Manager, how do I resolve the problem?

Try uninstalling the driver using the Broadcom installer and re-installing upon reboot. If it is still disabled, the driver being used may not support the adapter. Only drivers that were provided on the CD that shipped with the adapter should be used.

How can I create a driver disk from the CD?

There is a folder labeled "MakeDisk" on the CD (provided) where a driver disk can be created for the adapter. Run the setup.exe and follow the directions to create the driver disk.

How can I identify what chipset I am using?

: Go to the Vital Signs tab of BACS (Broadcom Advanced Control Suite) and look for the ASIC/Firmware Version field to identify the chipset.

: There is no simple way to determine a chipset, but PRODID.NLM will output the device ID that can be used to determine a chipset.

: Use the List PCI utility and look for "Ethernet controller: Broadcom Corporation NetXtreme X BCMXXXXX"

EX: lspci | grep -i Ethernet 01:00.0
Ethernet controller: Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet (rev 20)

: Install the respective driver per documentation. At the shell prompt, type grep BCM /var/adm/messages. The chipset information will be displayed at chip=BCM57xxS for fiber or chip=BCM57xx for copper.

: Install the respective driver package per documentation. At the command prompt, type: kstat -m bcme | grep macDeviceType. The chipset information will display on the screen.

: Execute b57udiag -cmd at the DOS prompt. The first column will display the chipset information.

How do I enable PXE?
  • Use b57udiag utility with the commands below:
    b57udiag -mba [ 0-disable | 1-enable ] -c <devnum>
  • Or:
    b57diag -mba [ 0-disable | 1-enable ] -c <devnum>
How do I upgrade PXE?

 

  • B57diag -c 0 -pxe a:b57mmba.nic

 

How do I configure the speed of PXE?

 

  • Use b57udiag utility with the commands below:
    b57udiag -mbas [ 0-Auto | 1-10HD | 2-10FD | 3-100H | 4-100F ]
  • Or: B57diag -c 0 -pxes [ 0-Auto | 1-10HD | 2-10FD | 3-100H | 4-100F

 

What should I do if the Broadcom PXE banner does not appear when I boot up the system?

In b57diag, check if PXE is enabled, and the Multiple Boot Agent (MBA) Delay Time should not be set to 15.

What should I do if the Broadcom network option is not available in the boot sequence of the BIOS?

In b57diag, check if PXE is enabled.

How do I troubleshoot when I am not getting an IP address for my PXE connection?

Check the DHCP server to see if it is functioning properly.

How do I compile a driver for Zenworks?

Simply follow the steps outlined in the Zenworks Readme file.

How do I use PowerQuest "Boot Disk Builder" to create a "PowerCast" disk for Broadcom 570x?
LINK SUPPORT BUFFERS 6 1600 PROTOCOL BIND B57 LINK DRIVER B57 FRAME ETHERNET_802.2 FRAME ETHERNET_II
  1. Download the latest "Netware (ODI16)" driver for 570x.
  2. Run PowerQuest "Boot Disk Builder".
  3. During the process of creating the "PowerCast Boot Disk" you will be asked to select a network adapter. Choose any Ethernet adapter listed. The 3Com 3C509 will be used in this example.
  4. Once "Boot Disk Builder" is finished creating the diskette, open Windows Explorer and view the contents of A: drive.
  5. Delete 3C5X9.COM or other existing ODI driver
  6. Copy the file B57.COM that was downloaded in step 1 to A:\.
  7. Use Notepad or another text editor to edit NET.CFG.
  8. In NET.CFG replace references to 3C5X9 with B57
    Example NET.CFG:
  9. Save the changes to NET.CFG.
  10. Use Notepad or other text editor to edit AUTOEXEC.BAT
  11. In AUTOEXEC.BAT replace 3C5X9.COM with B57.COM.
    Example AUTOEXEC.BAT:
    @ECHO OFF @PROMPT $P$G kicknic lsl b57.com REM mouse ECHO. ECHO. ECHO ImageCenter 5.0 ECHO Copyright 1994-2001 PowerQuest Corporation. ECHO All rights reserved. U.S. Patents 5,675,769; 5,706,472; 5,930,831, 6,088,778, and 6,108,759. Other patents pending. ECHO. ECHO Loading. Please wait... pqpcast /msn="session1" /dsk=1
  12. Save changes to AUTOEXEC.BAT.
How do I install Broadcom NDIS2 drivers with LAN Manager?
  1. Run the LAN Manager installation.
  2. When prompted to select the Network Adapter Driver, choose "Novell NE2000 Adapter (And Compatibles)"
  3. Complete the installation.
  4. Copy the Broadcom NDIS2 driver (B57.DOS or B44.DOS) to "C:\LANMAN.DOS\DRIVERS\ETHERNET\NE2000\"
  5. Edit "C:\LANMAN.DOS\PROTOCOL.INI" and make the following changes to the [NE2000_NIF] section located at the bottom of the file:
    • Change "DRIVERNAME = NE2000$" to "DRIVERNAME = B57$"
    • Remove "IOBASE = 0x300" and "INTERRUPT = 3" entries.
  6. Save PROTOCOL.INI
  7. Edit "C:\LANMAN.DOS\SETUP.INI" and make the following changes to the [ConfigSys] section:
    • Change the line: "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\NE2000.DOS" to "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\B57.DOS"
  8. Save SETUP.INI
  9. Edit "C:\CONFIG.SYS" and make the following changes:
    • Change the line: "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\NE2000.DOS" to "DEVICE = C:\LANMAN.DOS\DRIVERS\ ETHERNET\NE2000\B57.DOS"
  10. Save CONFIG.SYS
How do I use Sysprep with Windows 2000 and Windows XP?

The System Preparation tool, Sysprep.exe, is a disk-image-based deployment tool that you can use to install identical configurations on multiple computers. The information pertaining to how to use this tool is supplied with the Sysprep software or can be located through various sections of Microsoft's website (i.e. Knowledge Base, Technet, etc.). Therefore, our intent is not to instruct on how this tool is used but how to include the driver for our adapter to work in conjunction with this utility.

On the sysprep.inf file, the following will need to be added to the "Unattend" header:

[Unattend] OemPnPDriversPath=Drivers\Net

The driver files for our adapter depending on the operating system must reside in this directory that will be located in the System Drive (where the operating system resides). If other drivers are to be loaded, then Drivers\Net can be appended to the paths listed and separated by a semicolon (e.g. OemPnpDriversPath=Drivers\Video;Drivers\Net)

For Windows XP, the driver files to be included will be b57win32.inf, b57win32.cat, and b57xp32.sys.

For Windows 2000, the driver files to be included will be b57win32.inf, b57win32.cat, and b57w2k.sys.

The Sysprep utility must run with the -pnp switch in order to rescan for new devices which can be added during the mini-setup. Although there are differences between the Sysprep utility for Windows 2000 and Windows XP, the instructions outlined above should cover the only difference needed to set it up for the different operating systems.

A Sample Sysprep.inf for Windows XP is shown below:

------------------------------------------------------------------------ ;SetupMgrTag [Unattended] OemSkipEula=Yes OemPreinstall=Yes TargetPath=\Windows UnattendedInstall=Yes OemPnpDriversPath=Drivers\Net [GuiUnattended] AdminPassword="password" EncryptedAdminPassword=NO AutoLogon=Yes AutoLogonCount=99 OEMSkipRegional=1 OEMDuplicatorstring="XP System" TimeZone=4 OemSkipWelcome=1 [UserData] FullName="User" OrgName="Organization" ComputerName=* [SetupMgr] DistFolder=C:\sysprep\i386 DistShare=whistlerdist [Identification] JoinDomain=workgroup [Networking] InstallDefaultComponents=Yes
How can I run the BCM57xx or BCM4401 User Diagnostic applications?

Download the BCM57xx or BCM4401 user diagnostic from our website and follow these instructions:

  1. Create a DOS bootable floppy and unzip the respective diagnostic package into it
  2. Boot to Dos and run b57udiag or b44udiag, respectively
Under Linux, why does the uptime command show 1 when BASP is active?

The reason is that the BASP process is periodically waking up to check for events whereas most other processes will be sleeping indefinitely until woken up by external events. Because we are constantly running and sleeping even when the system is idle, it is showing up in the load average. But the important thing is that the CPU utilization remains at almost 100% idle even when the load average is non-zero.

Why does the Wake On LAN feature not work properly on my system containing a Broadcom network adapter when running in Vista or Windows 2008?

The Broadcom network devices are only supported in Vista and Windows Server 2008 using drivers originally intended for Windows XP and/or Windows Server 2003. Although Windows Vista and Windows Server 2008 are backward compatible to use drivers from the previous operating systems, Microsoft's NDIS 5.1 to NDIS 6 translation layer used to do so inhibits the feature from working properly.

Why doesn't my system wake up from an IPv6 interesting packet?

An IPv6 interesting packet can wake up Vista/Windows 2008. But, it wakes too often by frequent Address Resolution Protocol (ARP) requests and directed packet. In Windows 7 or later, there is a new feature "PM offload" (ARP offload + NS offload) added. Only magic packet can wake the system up if the PM offloads are enabled in your system.

To wake your system up via an IPv6 neighbor solicitation packet, go to driver's advanced tab and change NS offload to disable. Push the machine to sleep state. Delete IPv6 neighbors on the remote host and then send an IPv6 neighbor solicitation packet or telnet IPv6addressOfSUT

Note: Neighbor Solicitation: Similar to ARP for IPV6. Used for neighbor reach ability and address resolution.

Why do I see a yellow bang for an iSCSI client for Broadcom GigE device with my NetXtreme II 1Gb device in Windows Server 2008 R2?

The in-box driver supplied in Windows Server 2008 R2 for the NetXtreme II 1Gb device does not contain support for iSCSI devices. Updated drivers from your manufacturer or through our website should contain the necessary drivers for this device.

How do I update the inbox driver of Citrix XenServer 6.0.X?

Download the latest certified driver from Citrix.

Why doesn't my system recognize a LUN on the iSCSI Target during iSCSI Boot installation?
  1. Make sure your iSCSI Target is setup correctly.
  2. Make sure you are using the latest Broadcom driver for your Broadcom Network Adapter. Your in-box driver or your driver CD may be old and is not compatible with your network device.
How do I create a driver CD for my iSCSI Boot installation?
  1. For a Linux system, obtain the netxtreme2_sup-x.x.xx-x.ISO.tar.gz.file from the CD that came with the Broadcom Network Adapter or download it from the Broadcom website. Untar the file and burn the corresponding Linux kernel ISO on a CD. This CD will be provided during the iSCSI Boot installation process. For detailed instruction on installation, consult the iSCSI Boot user's guide.
  2. For a Windows system, obtain the corresponding Windows drivers (eVBD, VBD and NDIS) from the CD that came with Broadcom Network Adapter or download it from the Broadcom website. Place the drivers on a USB drive. Provide this USB drive as a source of drivers during Windows iSCSI Boot installation. For detailed instruction on installation, consult the iSCSI Boot user's guide.
How do I find Broadcom NetXtreme1 drivers on the VMware Driver Download web site?
  1. Go to the VMware Compatibility Guide: I/O Device Search
  2. Select the desired Product Release Version or leave at ALL.
  3. Select Brand Name: Broadcom or leave at ALL.
  4. Select I/O Device Type: All or as desired (such as Network, iSCSI, FCoE CNAs).
  5. In Keyword enter part of the device's name in quotes. For example "BCM5719" or "BCM57810".
  6. In the Search Results click on the desired Broadcom adapter name in the Model column.
  7. In the Model Release Details scroll through the list of compatible device drivers.
  8. Click on the expand "+" symbol to see details of the desired driver and to show the link to the VMware driver download web site. You normally want the highest version number selectable.
  9. Copy the desired Device Driver(s) information before following the link to the VMware driver downloads web site. You can paste this information into the downloads search box to find the correct driver to download.
  10. You can also type "tg3" (for NetXtreme1 devices - such as the 5700/01/02/03/04/05/14/15/18/19/20/21/22/23/50/51/52/53/54/55/56/64/80/81/82/84/88/89/etc) or "bnx2x" (for NetXtreme2 devices - 5706/08/09/16 and 57710/1/2 and 57800/10/etc) to display all available drivers packages. Normally choose the highest version number - i.e. tg3 version 3.123b.vXX.X verses 3.120h.vXX.X and bnx2x version 1.72.54.vXX.X verses 1.72.18.vXX.X.
  11. You may need to fine tune the driver search text since sometimes not all of the most current selections will be displayed when typing just the driver name (tg3 or bnx2x) - i.e. in the case of the NetXtreme2 driver package, the 1.72.54.v50.2 will not show up unless you additionally type in "bnx2x version 1.72" in the search window.
  12. To download the selected driver, click the desired Download method in the lower right hand side of the window. NOTE that ESX/ESXi 4.x is an ISO file while ESXi 5.x is a ZIP file.
  13. In the downloaded driver file, follow the README.TXT instructions to load the driver.
What is BACS (Broadcom Advanced Control Suite)?

Broadcom Advanced Control Suite (BACS) is an integrated graphical user interface application that provides the following functions:

  • : At-a-glance status reports of all LAN adapters/controllers in your systems.
  • : The Network Test will confirm network connectivity to a remote station.
  • : A comprehensive diagnostic for Broadcom NetXtreme Gigabit Ethernet controllers.
  • : An in depth analysis on CAT5 cable characterization performed by the Broadcom NetXtreme Gigabit Ethernet controller.
  • : An easy way to configure the load balance and failover by grouping multiple adapters/controllers.
  • : A detailed performance statistics on each selected adapter/controller.
Which operating systems support BACS?

Vista, Windows 2008, Windows 7, Windows 2008 R2.

How can I install BACS (Broadcom Advanced Control Suite)?

Broadcom Advanced Control Suite (BACS) can be installed from the Management Applications Installer provided on the OEM's CD or from the Broadcom's website.

How can I uninstall BACS (Broadcom Advanced Control Suite)?
  1. From the Windows Control Panel, double-click Programs and Features.
  2. At the Programs and Features window, select "Broadcom Management Programs" and click Uninstall . The InstallShield Wizard screen appears.
  3. The Confirm File Deletion screen appears.
  4. Click OK. An information screen will appear confirming update.
  5. Reboot your system to complete the BACS removal.
How do I start BACS?
  1. Click Start button, click Settings, then click Control Panel.
  2. Double-click the Broadcom Control Suite 4 icon.
What is BASP (Broadcom Advanced Server Program)?

BASP is a Broadcom intermediate software driver for Windows Operating System, that provides load-balancing, fault-tolerance, and VLAN features. These features are provided by creating teams (virtual adapters) that consist of multiple NIC interfaces. A team can consist of one to eight NIC interfaces, and each interface can be designated as primary or standby. All primary interfaces in a team will participate in load-balancing operations by sending and receiving a portion of the total traffic. Standby interfaces will take over in the event that all primary interfaces have lost their links. VLANs can be added to a team to allow multiple VLANs with different VLAN IDs. A virtual adapter is created for each VLAN added. Load-balancing and fault-tolerance features will work with any third party's NIC adapters. VLANs only work with Broadcom NIC adapters.

Which operating systems support BASP?

Windows 2008, Windows 2008 R2.

Which protocols support BASP?

TCP/IP and IPX protocols. NetBeui is supported in some operating systems. Please refer to the Broadcom NetXtreme Gigabit Ethernet Adapter user manual for details.

How can I identify which driver version is installed?

: Go to Hosts > Adapter > Port > Broadcom NetXtreme Gigabit Ethernet tab of BACS (Broadcon Control Suite 4) and look for the Driver Name/Version field to identify the driver version.

How can I do a quick Network Test to see if my adapter is working properly?

In Microsoft Windows, a quick network test can be done by going to the NDIS node in BACS, click on the Diagnostics tab and click on Test. Please note, if a default gateway is not specified for the adapter, BACS will prompt for an IP address.

Is there a diagnostic utility in Windows to determine if my adapter is functioning properly?

In Microsoft Windows, there is a diagnostics feature in BACS (Broadcom Control Suite 4). For a NetXtreme I device, go to the Port number under Device Management, click on the Diagnostics tab. Click on the "Select Tests to run:" pull down menu, select Diagnostics Tests. For NetXtreme II devices, go to the Port Number, click on the Diagnostics tab, Select "Diagnostics Tests" from the pull down menu. Then click on Run test(s) to perform the tests. The test includes Control Registers Test, MII Registers Test, EEPROM Test, Internal Memory Test, On-Chip CPU Test, Interrupt Test, Loopback Test, and LED Test.

How can I perform cable analysis on the cable that is connected to my adapter?

In Microsoft Windows, there is a Cable Analysis feature in BACS (Broadcon Control Suite 4). For a NetXtreme I device, go to the Port number under Device Management, click on the Diagnostics tab. Click on the "Select a Tests to run:" pull down menu, select Cable Analysis. For NetXtreme II devices, go to the Port number, click on the Diagnostics tab, Select "Cable Analysis" from the pull down menu. Then click on Analyze to perform the test.

How can I view traffic statistics on my adapter?

In Microsoft Windows, go to the Statistics tab of BACS (Broadcom Advanced Control Suite).

Why does BACS 4 and Service Control Manager lock up on Windows Server 2003 SP2 (x86 and x64) when is using the TCP/IPv6 protocol?

The IPv6 Helper Service within the OS may take too long to start or not start correctly. This may occur when multiple VNICs/VLANs have been created on a system where the IPv6 driver has been installed. When the IPv6 driver, which is not native to Windows Server 2003 SP2, binds to many network adapters, it stops responding to all TCP/IPv6 requests.

Applying Microsoft hotfix KB 968597 (http://support.microsoft.com/kb/968597) will resolve the issue.

How do I configure two or more adapters to a team?

In Microsoft Windows Control Panel, click Broadcom Advanced Control Suite, or click the BACS icon in the taskbar located at the bottom of the Windows desktop, select Teams from the menu, and select "Go to Team View". To create a new team, select Create Team from the Team menu or right-click one of the devices in the "Unassigned Adapters" section and select Create Team. A teaming wizard will display. Follow the instructions in the wizard, and then click Finish to create the desired teaming configuration.

How do I remove adapters from a team?
How many adapters can be in a team?
What is VLAN?
How can I configure VLAN (Virtual Local Area Network)?
What is the maximum number of VLANs that can be configured?
How can I save my teaming configuration?
How can I restore my teaming configuration?
A system containing an 802.3ad team causes a Netlogon service failure in the system event log and prevents it from communicating with the domain controller during boot up. How do I resolve this issue?
When I try to create a team under Window 2008 Server, I receive an error message.
Can a BASP teamed virtual adapter function as a Hyper-V virtual switch?
Can you PXE boot a Virtual Machine (VM) on Windows 2008 R2 Hyper-V over Broadcom BASP-created teamed ports?
Does BASP Teaming support VMQs?
How are MS Windows 2008 R2 Hyper-V BASP Teams deleted?
Does BASP support MS Windows 2008 R2 Hyper-V VLANs?

BASP only supports Hyper-V configured VLANs over a BASP untagged VLAN team. If VLANs are configured using the Hyper-V manager for a BASP tagged VLAN team, the BASP tagged VLAN setting will override the Hyper-V VLAN setting.

How do I add virtual switches and assign virtual NICs for VMware ESX 4.x or ESXi 5.0?

To add a vSwitch and assign a virtual NIC as an uplink network:

  1. esxcfg-vswitch -a <vSwitch1> (add virtual switch)
  2. esxcfg-vswitch -L <vmnicX> <vSwitch1> (assign virtual NIC to the virtual switch)
  3. esxcfg-vswitch --add-pg="Console1" vSwitch1 (assign a new portgroup)
How do I assign an IP to a virtual NIC for VMware ESX 4.x or ESXi 5.0?
How do I assign an IPv6 to a virtual NIC for VMware ESX 4.x or ESXi 5.0?
How can I change the speed on the adapter for VMware ESX 4.x or ESXi 5.0?
How do I disable firewall for VMware ESX 4.x or ESXi 5.0?
How do I configure jumbo frames for VMware ESX 4.x or ESXi 5.0?
How do I configure VMDirectPath for NICs for VMware ESX 4.x or ESXi 5.0?
How do I configure the number of Netqueues for VMware ESX 4.x/ESXi 5.0?
How do I update the inbox driver of Citrix XenServer 6.0.X?