Dell Broadcom NetXtreme Family of Adapters - Manual (Page 38)

NDIS2 Driver Software: Broadcom NetXtreme BCM57XX User Guide
file:///C|/Users/Nalina_N_S/Documents/NetXtreme/English/ndis2.htm[9/5/2014 3:32:09 PM]
address, IRQ number, detected line speed, and the controller BusNum and DevNum. If the driver fails to load, an
initialization fail message is displayed.
Configuring the NDIS2 Driver Software
The NDIS2 driver software can be configured by adding specific optional keywords to the Protocol.ini file. If multiple (or
multiport) Broadcom NetXtreme Gigabit Ethernet adapters are installed in a system, the NDIS2 driver software loads by
default on the adapter/port that has a good link. If 2 or more adapters have a good link, the NDIS2 driver software loads on
the adapter having the latest Device ID. If 2 or more adapters that have a good link have the same Device ID, the NDIS2
driver software loads on the adapter that is located in the slot having the lowest bus number.
NOTE: On MS-DOS platforms, it is not recommended to load the NDIS2 driver software on more than 1 adapter; the
required NDIS2 protocol manager that supports multiple binds is not available in the MS-DOS environment.
If it is necessary to have the NDIS2 driver load on certain adapters in a certain order, the BusNum, DevNum, and FuncNum
keywords can be used. Do not use these keywords unless you know how to configure PCI devices.
The BusNum keyword value, which represents the PCI bus number in which the adapter is located, is a decimal number
ranging from 0 to 255.
The FuncNum keyword value, which represents the function (port) number of a multiport adapter, is a decimal number, with
0 representing the first port, and 1 representing the second port.
The DevNum keyword value, which represents the assigned device number, is a decimal number ranging from 0 to 31.
NOTE: At the end of the NDIS2 driver software installation process, note the BusNum and DevNum values that are
displayed. Alternatively, use Broadcom Advanced Control Suite (see Broadcom Advanced Control Suite) to view the bus
number, function (port) number, and device number assigned to each adapter (Windows users only).
Example BusNum, DevNum, and FuncNum keyword entries for loading the NDIS2 driver on multiple adapters in a certain
order are shown below:
[B57]
DRIVERNAME = B57$
BUSNUM = 3
DEVNUM = 10
[B57_2]
DRIVERNAME = B572$
BUSNUM 3
DEVNUM 11
[B57_3]
DRIVERNAME = B573$
BUSNUM 3
DEVNUM 12
[B57_4]
DRIVERNAME = B574$
BUSNUM 3
DEVNUM 13
The LineSpeed keyword is used to force the speed of the network connection. The LineSpeed keyword requires a decimal
number and of either 10, 100, or 1000. Technically, a line speed of 1000 Mbit/s cannot be forced and can be achieved only
through auto-negotiation. For the sake of simplicity, the driver performs auto-negotiation when the line speed is set to a
value of 1000. Forced 1000 Mbit/s speed is not needed for copper links; auto-negotiation is the proper supported
configuration under the IEEE Ethernet specification.
The Duplex keyword is used to force the duplex mode of the adapter. The Duplex keyword requires a text string of either
HALF or FULL. When the Duplex keyword is used, the LineSpeed keyword must also be used. If neither keyword is used, the
network adapter defaults to auto-negotiation mode.
The NodeAddress keyword specifies the network address used by the adapter. If a multicast address or a broadcast address is
specified, the adapter uses the default MAC address.
The FixCheckSumOff keyword turns off the driver workaround for the TCP/IP stack to recognize the ones complement version
of the checksum.
Example entries for the LineSpeed, Duplex, and NodeAddress keywords are shown below:
[B57]
DRIVERNAME = B57$
BUSNUM = 3
DEVNUM = 10
PORTNUM = 0
LINESPEED = 100