Installing the Driver Software
Configuring the Driver Software
The Open Data-Link Interface (ODI) driver software allows LAN drivers to work together irrespective of differences between the hardware and/or the protocol stacks of communicating computers. An intervening layer, called the link support layer (LSL), is responsible for routing different packet types between LAN drivers and protocol stacks.
Installing the ODI driver software involves the following steps:
Verify that the Broadcom NetXtreme Gigabit Ethernet adapter driver software has been installed on your system. If it has not, install it (see Installing the Driver Software). Otherwise, you cannot use a Broadcom NetXtreme Gigabit Ethernet adapter in the MS-DOS environment.
Note: To successfully install the adapter driver for MS-DOS, the adapter must be installed before you install the adapter driver.
Note: Do not change the default settings for any of the other items in the Installation Configuration Summary.
Note: The driver loads during system configuration, and the Broadcom banner, the adapter name, the MAC address, the IRQ number, the detected line speed, and the bus number (BusNum) and device number (DevNum) of the adapter are displayed. If the driver fails to load, an initialization fail message appears.
Note: The driver loads during system configuration, and the Broadcom banner, the adapter name, the MAC address, the IRQ number, the detected line speed, and the bus number (BusNum) and device number (DevNum) assigned to the adapter are displayed. If the driver fails to load, an initialization fail message is displayed.
The ODI driver software can be configured by adding specific optional keywords to the Net.cfg file.
If multiple (or multiport) Broadcom NetXtreme Gigabit Ethernet adapters are installed in a system, the ODI driver software loads by default on the adapter/port that has a good link. If 2 or more adapters have a good link, the ODI 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 ODI driver software loads on the adapter that is located in the slot having the lowest bus number. If it is necessary to have the ODI 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 hexadecimal number ranging from 0 to 255.
The FuncNum keyword value, which represents the function (port) number of a multiport adapter, is a hexadecimal 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 hexadecimal number ranging from 0 to 31.
Notes:
For example, BusNum, DevNum, and FuncNum keyword entries for loading the ODI driver on multiple adapters in a certain order are shown below:
PROTOCOL <protocol name>
BIND B57
BIND B57
LINK DRIVER B57
BUSNUM 1
DEVNUM 9
FRAME <frame #1 name>
LINK DRIVER B57
BUSNUM 1
DEVNUM A
FRAME <frame #2 name>
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.
Example keyword entries for the LineSpeed, and Duplex keywords are shown below:
LINK DRIVER B57
LINESPEED 100
DUPLEX FULL