Intel XL710-Q2 User Manual page 78

The following speed and duplex configurations can be selected:
Autonegotiate (recommended)
l
100 Mbps, full duplex
l
100 Mbps, half duplex
l
10 Mbps, full duplex
l
10 Mbps, half duplex
l
The speed and duplex setting selected must match the speed and duplex setting of the connecting network
port. A speed and duplex mismatch between ports will result in dropped packets and poor network
performance. It is recommended to set all ports on a network to autonegotiate. Connected ports must be set
to autonegotiate in order to establish a 1 gigabit per second connection.
Fiber-optic and 10 gigabit ethernet adapters do not support forced speed and duplex.
Diagnostic Capability
The UEFI network driver features built in hardware diagnostic tests. The diagnostic tests are called with the
UEFI shell drvdiag command.
drvdiag -s -Performs a basic hardware register test.
drvdiag -e -Performs an internal loopback transmit and receive test.
UEFI Known Issues
Long Initialization Times
Long initialization times observed with Intel's UEFI driver are caused when the UNDI.Initialize command is
called with the PXE_OPFLAGS_INITIALIZE_CABLE_DETECT flag set. In this case, UNDI.Initialize will try
to detect the link state.
If the port is connected and link is up, initialize will generally finish in about 3.5 seconds (the time needed to
establish link, dependent on link conditions, link speed and controller type) and returns PXE_STATFLAGS_
COMMAND_COMPLETE. If the port is disconnected (link is down), initialize will complete in about 5
seconds and return PXE_STATFLAGS_INIIALIZED_NO_MEDIA (driver initializes hardware then waits for
link and timeouts when link is not establish in 5 seconds).
When UNDI.Initialize is called with PXE_OPFLAGS_INITIALIZE_DO_NOT_DETECT_CABLE the function
will not try to detect link status and will take less than 1 second to complete.
The behavior of UNDI.Initialize is described in UEFI specs 2.3.1: Initializing the network device will take up to
four seconds for most network devices and in some extreme cases (usually poor cables) up to twenty
seconds. Control will not be returned to the caller and the COMMAND_COMPLETE status flag will not be set
until the adapter is ready to transmit.
Intel® Boot Agent Configuration
Boot Agent Client Configuration
The Intel® Boot Agent software provides configuration options that allow you to customize the behavior of the
Intel Boot Agent software. You can configure the Intel Boot Agent in any of the following environments:
A Microsoft* Windows* Environment
l
A Microsoft* MS-DOS* environment
l
A pre-boot environment (before operating system is loaded)
l