EFI/DOCS 0000755 0000000 0000000 00000000000 11761422155 007024 5 ustar EFI/DOCS/boot_util.htm 0000755 0000000 0000000 00000076075 11636052002 011626 0 ustar
The Intel® Ethernet Flash Firmware Utility (BootUtil) is a utility that can be used to program the PCI option ROM on the flash memory of supported Intel PCI and PCI-Express-based network adapters, and to update configurations. BootUtil replaces existing utilities and provides the functionality of the older IBAUTIL, ISCSIUTL, LANUTIL, and FLAUTIL. BootUtil supports all the adapters supported by the previous utilities.
NOTE: Updating the adapter's flash memory using BootUtil will erase any existing firmware image from the flash memory. |
Intel provides the following flash firmware in FLB file format for programming to the flash memory:
Intel® Boot Agent as PXE Option ROM for legacy BIOS
http://www.intel.com/support/network/adapter/pro100/bootagent/
Intel® iSCSI Remote Boot as iSCSI Option ROM for legacy BIOS
http://www.intel.com/support/network/iscsi/remoteboot/
Network Connectivity, UEFI network driver
http://www.intel.com/support/network/sb/cs-006120.htm
OEMs may provide custom flash firmware images for OEM network adapters. Please refer to the instructions given by OEMs.
BootUtil allows the user to flash supported firmware to the adapter from the included master FLB file. This option ROM includes PXE, iSCSI, FCoE and UEFI drivers, and the image is programmed to the flash memory at once. BootUtil will also build the required combo images for supported adapters and program those images to the flash, as well. Since both discrete and combo images are supported, the -BOOTENABLE command ONLY works on combo images.
PXE+EFI and iSCSI+EFI image combinations are supported for all OEM generic adapters, however support is limited to devices which support both technologies as discrete images. However, flash size is a limiting factor, as the image size can change without notice.
The Master FLB file (BOOTIMG.FLB) is the new container for all the Intel® Boot Option ROMs. This file replaces the existing FLB files for FCoE, iSCSI, PXE, and EFI.
NOTE: BootUtil supports older flb files to maintain backwards compatibility with the previous utilities. |
BootUtil without command-line options will display a list of all supported
Intel network ports in the system. BootUtil will also allow the user to enable
or disable the flash memory on specific ports by using -FLASHENABLE or
-FLASHDISABLE options in order to control access to the firmware from the
system.
BootUtil allows the user to individually set iSCSI, FCoE, UEFI and PXE boot configurations
by -NIC=xx -[OPTION]=[VALUE] options. The -I option is iSCSI specific and will
not work for PXE configurations.
NOTES:
|
BootUtil is located on the software installation CD in the \APPS\BootUtil\
directory. Check the Intel Customer Support (http://support.intel.com) website
for the latest information and component updates.
The syntax for issuing BootUtil command-line options is:
BOOTUTIL -[OPTION] or -[OPTION]=[VALUE]
BootUtil accepts one executable option and its associated non-executable options in an execution. If conflicting executable options (such as -FLASHENABLE and -UPDATE used together) are supplied, BOOTUTIL exits with an error.
The options, where applicable, are listed in logical groups.
NOTE: If you run BootUtil without any command-line options, the utility displays a list of all supported Intel network ports found in the system. |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The CHAP Authentication feature of this product requires the following
acknowledgements: ExamplesThe following examples show how to enter some typical BootUtil command lines: Example 1:To enable the flash firmware on the first network adapter for the system to
be capable of executing the flash firmware. BootUtil -NIC=1 -FLASHENABLE Example 2:To disable the flash firmware on all the network adapters. BootUtil -ALL -FD Example 3:To display BootUtil FLB flash firmware types and versions.
Example 4:To update all ports of a supported NIC with PXE.
Example 5:To update a combo image on supported adapter (eg, pxe+iscsi). Bootutil -UP=Combo -NIC=2 -FILE=BOOTIMG.FLB The above command will succeed if the PXE+ISCSI combination is supported on NIC #2. If not an error is displayed to the user.
Example 6:To enable PXE firmware on the third network port in the system.
Example 7:To disable the firmware on the second network port in the system.
Example 8:To get help descriptions.
Example 9:To enable DHCP for the iSCSI initiator on all the network ports in the system.
Example 10:To load the iSCSI boot configurations from a text script file to the first network port.
Exit CodesBootUtil returns exit codes to the OS environment. Possible exit codes are listed below:
EFI/DOCS/efi.htm 0000755 0000000 0000000 00000043022 11725412506 010363 0 ustar UEFI Network Device Driver for Intel® Ethernet Network ConnectionsSupported UEFI Implementations Intel UEFI Network Driver Naming Convention Installing the UEFI Network Driver Option ROM Using PROset Installing the UEFI Network Driver Option ROM From the UEFI Shell Configuring UEFI Network Stack for PXE Configuring UEFI Network Stack for TCP/UDP/MTFTP Unloading the UEFI Network Driver OverviewThe UEFI network driver for Intel® Ethernet Network Connection enables network connectivity under UEFI. It can be used in conjunction with UEFI software components available from other sources to perform network functions in the UEFI environment. Intel's UEFI network driver supports Intel's FLB3 file format. This format extends the header information in the FLB file, enabling more than 16 image types, including a combined Option ROM and NVM image.
Supported UEFI ImplementationsThe UEFI network driver supports UEFI platforms based on the following UEFI/EFI specifications:
UEFI driver binaries are provided for 64-bit (x86-64), and Itanium processor family platforms. Intel UEFI Network Driver Naming ConventionThe network driver version, UEFI platform type, and the network hardware
support can be determined by the file naming convention. The format of the
driver filename is listed below: where:
Examples:
Loading the UEFI Network DriverThe network driver can be loaded using the UEFI shell "load" command:
Installing the UEFI Network Driver Option ROM Using PROSetIntel® PROSet for Windows Device Manager can install the UEFI network driver on an Intel network adapter's option ROM. The UEFI network driver will load automatically during system UEFI boot When installed in the option ROM. UEFI specific*.FLB images are included on the CD release media. The "Boot Options" tab in Intel® PROSet for Windows Device Manager will allow the UEFI*.FLB image to be installed on the network adapter. The following FLB files are included on the release media:
Intel® PROSet for Windows Device Manager can only be used to program add-in Intel PCI, PCI-X, and PCI-E network adapters. LOM (LAN On Motherboard) network connections cannot be programmed with the UEFI network driver option ROM. Refer to the PROSet documentation for detailed instructions. Installing the UEFI Network Driver Option ROM from the UEFI ShellThe BootUtil command line utility can install the UEFI network driver on an Intel network adapter's option ROM. The UEFI network driver will load automatically during system UEFI boot When installed into the option ROM. Run BootUtil with the following command line options to install the UEFI network driver on all supported Intel network adapters: For x64 systems:
For ia64 systems:
BootUtil can only be used to program add-in Intel PCI, PCI-X, and PCI-E network adapters. LOM (LAN On Motherboard) network connections cannot be programmed with the UEFI network driver option ROM. UEFI Network StackAs of UEFI 2.1 there are two network stack configurations under UEFI. The most common configuration is the PXE based network stack. The alternate network stack provides IPv4 TCP, UDP, and MTFTP network protocol support. As of UEFI 2.1 the PXE and IP-based network stacks cannot be loaded or operate simultaneously. The following two sections describe each UEFI network stack configuration. Reference implementations of the PXE and IP based network stack source code are available for download at www.tianocore.org. Configuring UEFI Network Stack for PXEThe PXE (Preboot eXecution Environment) based UEFI network stack provides support for UEFI network boot loaders downloaded from a WFM compliant PXE server. Services which can be enabled include Windows 2008 Deployment Services (WDS), Windows 2003 Server Remote Installation Service (Itanium only), Linux network installation (Elilo), and TFTP file transfers. To enable UEFI PXE services the following network protocol drivers must be loaded with: snp.efi, bc.efi, and pxedhcp4.efi. These drivers can be loaded from the UEFI "load" shell command, but are often included as part of the UEFI system firmware. The UEFI shell command "drivers" can be used to determine if the UEFI PXE drivers are included in the UEFI implementation. The drivers command will output a table listing drivers loaded in the system. The following entries must be present in order to network boot a UEFI system over PXE:
A network boot option will appear in the boot options menu when the UEFI PXE
network stack and Intel UEFI network driver have been loaded. Selecting this Configuring UEFI Network Stack for TCP/UDP/MTFTPAn IP-based network stack is available to applications requiring IP-based network protocols such as TCP, UDP, or MTFTP. The following UEFI network drivers must be built into the UEFI platform implementation to enable this stack: SNP (Simple Network Protocol), MNP (Managed Network Protocol), ARP, DHCP4, IPv4, ip4config, TCPv4, UDPv4, and MTFTPv4. These drivers will show up in the UEFI "drivers" command output if they are included in the platform UEFI implementation:
The ifconfig UEFI shell command must be used to configure each network interface. Running "ifconfig -?" from the UEFI shell will display usage instructions for ifconfig. Unloading the UEFI Network DriverTo unload a network driver from memory the UEFI "unload" command is used. The syntax for using the unload command is as follows: "unload [driver handle]", where driver handle is the number assigned to the driver in the far left column of the "drivers" output screen. Force Speed and DuplexThe UEFI network driver supports forced speed and duplex capability. The force speed and duplex menu can be accessed with UEFI shell command "drvcfg":
The following speed and duplex configurations can be selected:
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 CapabilityThe UEFI network driver features built in hardware diagnostic tests. The diagnotic tests are called with the UEFI shell drvdiag command.
|