Bios extended memory copy error

Bios extended memory copy error

Platinum Member Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору

yukpxe.htm created 02-Oct-2003
Readme File for yukpxe.rom v1.11
PXE ROM Yukon
This file contains
1 Overview
2 Installation

2.1 Installation of binary
2.2 Removal of binary

3.1 PXELINUX
3.2 WINDOWS 2000/XP Remote Installation Services (RIS)

4 PXE Client Status/Error Codes

4.1 Init/Boot/Loader Codes
4.2 BIOS Codes
4.3 Base-Code/UNDI Loader Codes

1 Overview
YUKPXE is the PXE support software for the Marvell Yukon Gigabit Ethernet
Adapter.

2.1 Installation of binary

yukpxe.rom must be flashed to the network adapter using the YUKONDG
utility.

To flash the binary to the network adapter, proceed as follows:
1. Start YUKONDG.
2. Select ‘FLASH PROM . ‘ > ‘Load FLASH PROM from file».
3. Type the path and filename of the binary (yukpxe.rom).
4. Press .
5. After the process is finished, exit the utility.
PXE support is now installed on the network adapter.

2.2 Removal of binary

To disable all actions of yukpxe.rom, the network adapter FLASH PROM must
be cleared using the YUKONDG utility.

To clear the Flash PROM, proceed as follwows:
1. Start YUKONDG.
2. Select ‘FLASH PROM . ‘ > ‘Clear FLASH PROM’.
3. After the process is finished, exit the utility.
PXE support is now removed from the network adapter.

If you use LINUX as bootserver, you must include the Marvell Yukon
Gigabit Ethernet Adapter driver in the kernel of the downloadable image.
For details, please refer to the PXELINUX manual.

3.2 WINDOWS 2000/XP Remote Installation Services (RIS)

NOTE: WINDOWS 2000 Advanced Server can provide images of WINDOWS 2000
Professional and Windows XP Professional to clients.
For details on how to install and configure the WINDOWS 2000 Remote
Installation Services please refer to the WINDOWS 2000 Advanced
Server online help.

When you create an image of the WINDOWS installation CD (2000 or XP), it
does not contain a driver for the Marvell Yukon Gigabit Ethernet Adapter.
The WINDOWS setup utility that is transferred to the client, expects a
driver for the network adapter in the installation image. It stops the
installation and displays an error message if it can not find any
suitable driver.

To create an installation image that contains the Marvell Yukon Gigabit
Ethernet Adapter driver, proceed as follows:
1. Create a new image from the WINDOWS installation CD (2000 or XP).
(For details, refer to the WINDOWS 2000 Advanced Server online help.)
2. Copy the file YUKONW2K.INF (2000) or YUKONWXP.INF (XP) from the network
adapter driver CD to the directory i386 of the image directory on the
server.
3. Copy the file YUKONW2K.SYS (2000) or YUKONWXP.SYS (XP) from the network
adapter driver CD to the directory i386 of the image directory on the
server.

WINDOWS setup can now use the correct driver from the image. It copies
installation files to the client, then unloads the network adapter driver
and reboots the PC.
Be prepared to supply the Marvell Yukon Gigabit Ethernet Adapter driver
CD to install and configure the network adapter when WINDOWS setup asks
for it.

4 PXE Client Status/Error Codes

4.1 Init/Boot/Loader Codes

Error: PXE-E01
Description: PCI Vendor and Device IDs do not match!
Reason: The Vendor/Device IDs in the PXE binaries that are flashed to
ROM do not match those of the network adapter. One possible
reason is that the binaries are flashed to the wrong network
adapter.
Solution: Check if installed on a compatible adapter. See chapter
‘Overview’ for the compatible adapter family.

Error: PXE-E04
Description: Error reading PCI configuration space.
Reason: This message is displayed if any of the PCI BIOS calls made
to read the PCI configuration space return an error code.
This error must not occur with a final released BIOS and
hardware operating correctly.
Solution: Get the latest release version of your BIOS from your BIOS
manufacturer.

Error: PXE-E06
Description: Option ROM requires DDIM support.
Reason: This error must not occur with a final released BIOS.
Solution: Get the latest release version of your BIOS from your BIOS
manufacturer.

Error: PXE-E07
Description: PCI BIOS calls not supported.
Reason: This error must not occur with a final released BIOS.
Solution: Make sure the PCI BIOS has PCI BIOS services.

Error: PXE-E20
Description: BIOS extended memory copy error. AH == nn
Reason: This message is displayed if the BIOS extended memory copy
service returns an error.

4.3 Base-Code/UNDI Loader Codes

NOTE: The base-code ROM is part of yukpxe.rom.

Error: PXE-E61
Description: Media test failed, check cable.
Reason: The cable is not plugged in, or not connected.
Solution: Check the cable.

Error: PXE-EC1
Description: Base-code ROM ID structure was not found.
Reason: UNDI boot module did not find the base-code ROM ID structure.
If there is a base-code ROM image in the system, it may have
been corrupted.
Solution: Repeat the installation procedure as described above.

Error: PXE-EC3
Description: Base-code ROM ID structure is invalid.
Reason: The base-code ROM ID structure is invalid. The base-code ROM
image may have been corrupted.
Solution: Repeat the installation procedure as described above.

Error: PXE-EC6
Description: UNDI driver image is invalid.
Reason: The UNDI ROM image may have been corrupted.
Solution: Repeat the installation procedure as described above.

Error: PXE-EC8
Description: !PXE structure was not found in UNDI driver code segment.
Reason: The UNDI ROM image may have been corrupted, or has not been
initialized by the BIOS.
Possible reasons for this error:
— A network adapter image was programmed into a BIOS, not
into the network adapter.
— The memory allocated by the POST Memory Manager ($PMM)
during PXE option ROM initialization has been corrupted or
erased before PXE option ROM boot.
— The UNDI_Loader structure was not initialized correctly
during option ROM initialization.
Solution: Repeat the installation procedure as described above.

Error: PXE-EC9
Description: PXENV+ structure was not found in UNDI driver code segment.
Reason: The UNDI ROM image may have been corrupted, or has not been
initialized by the BIOS.
Possible reasons for this error:
— A network adapter image was programmed into a BIOS, not to
the network adapter.
— The memory allocated by the POST Memory Manager ($PMM)
during PXE option ROM initialization has been corrupted or
erased before PXE option ROM boot.
— The UNDI_Loader structure was not initialized correctly
during option ROM initialization.
Solution: Repeat the installation procedure as described above.

Источник

Bios extended memory copy error

The Message Text column in the table below contains an alphanumeric list of error and informational messages that the Boot Agent may display during initialization. Possible causes for the messages are listed in the table’s Cause column. Wherever applicable, advice regarding how to avoid an error condition also appears in the Cause column.

Flash device wrong size.

This can occur as an error message when using IBAUtil. The full version of Boot Agent software cannot be loaded into a flash ROM device smaller than 64 KB. If a 32 KB (or smaller) flash ROM device is detected in the adapter, the flash update software returns this message. Assuming the device is socketed, remove the «too small» device and install a blank 64 KB (or larger) flash ROM device. Invalid PMM function number. PMM is not installed or is not working correctly. Try updating the BIOS. PMM allocation error. PMM could not or did not allocate the requested amount of memory for driver usage. Press Ctrl+S to enter the Setup Menu. Instructs you how to enter the Configuration Setup Menu. PXE-E00: This system does not have enough free conventional memory. The Boot Agent cannot continue. System does not have enough free memory to run PXE image. The Boot Agent was unable to find enough free base memory (below 640K) to install the PXE client software. The system cannot boot via PXE in its current configuration. The error returns control to the BIOS and the system does not attempt to remote boot. If this error persists, try updating your system’s BIOS to the most recent version. Contact your system administrator or your computer vendor’s customer support to resolve the problem. PXE-E01: PCI Vendor and Device IDs do not match! Image vendor and device ID do not match those located on the card. Make sure the correct flash image is installed on the adapter. PXE-E04: Error reading PCI configuration space. The Boot Agent cannot continue. PCI configuration space could not be read. Machine is probably not PCI compliant. The Boot Agent was unable to read one or more of the adapter’s PCI configuration registers. The adapter may be mis-configured, or the wrong Boot Agent image may be installed on the adapter. The Boot Agent will return control to the BIOS and not attempt to remote boot. Try to update the flash image. If this does not solve the problem, contact your system administrator or Customer Support. PXE-E05: The LAN adapter’s configuration is corrupted or has not been initialized. The Boot Agent cannot continue. The adapter’s EEPROM is corrupted. The Boot Agent determined that the adapter EEPROM checksum is incorrect. The agent will return control to the BIOS and not attempt to remote boot. Try to update the flash image. If this does not solve the problem, contact your system administrator or Customer Support. PXE-E06: Option ROM requires DDIM support. The system BIOS does not support DDIM. The BIOS does not support the mapping of the PCI expansion ROMs into upper memory as required by the PCI specification. The Boot Agent cannot function in this system. The Boot Agent returns control to the BIOS and does not attempt to remote boot. You may be able to resolve the problem by updating the BIOS on your system. If updating your system’s BIOS does not fix the problem, contact your system administrator or Customer Support. PXE-E07: PCI BIOS calls not supported. BIOS-level PCI services not available. Machine is probably not PCI compliant. PXE-E09: Unexpected UNDI loader error. Status == xx The UNDI loader returned an unknown error status. xx is the status returned. PXE-E20: BIOS extended memory copy error. BIOS could not move the image into extended memory. PXE-E20: BIOS extended memory copy error. AH == xx Error occurred while trying to copy the image into extended memory. xx is the BIOS failure code. PXE-E51: No DHCP or BOOTP offers received. The Boot Agent did not receive any DHCP or BOOTP responses to its initial request. Make sure that your DHCP server (and/or proxyDHCP server, if one is in use) is properly configured and has sufficient IP addresses available for lease. If you are using BOOTP instead, make sure the BOOTP service is running and is properly configured. PXE-E53: No boot filename received. The Boot Agent received a DHCP or BOOTP offer, but has not received a valid filename to download. If you are using PXE, please check your PXE and BINL configuration. If using BOOTP, be sure that the TFTP service is running and that the specific path and filename are correct. PXE-E61: Media test failure. The adapter does not detect link. Please make sure that the cable is good and is attached to a working hub or switch. The link light visible from the back of the adapter should be lit. PXE-EC1: Base-code ROM ID structure was not found. No base code could be located. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. PXE-EC3: BC ROM ID structure is invalid. Base code could not be installed. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. PXE-EC4: UNDI ROM ID structure was not found. UNDI ROM ID structure signature is incorrect. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. PXE-EC5: UNDI ROM ID structure is invalid. The structure length is incorrect. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. PXE-EC6: UNDI driver image is invalid. The UNDI driver image signature was invalid. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. PXE-EC8: !PXE structure was not found in UNDI driver code segment. The Boot Agent could not locate the needed !PXE structure resource. An incorrect flash image is installed or the image has become corrupted. Try to update the flash image. PXE-EC9: PXENV + structure was not found in UNDI driver code segment. The Boot Agent could not locate the needed PXENV+ structure. An incorrect flash image is installed, or the image has become corrupted. Try to update the flash image. PXE-M0F: Exiting Intel PXE ROM. Ending execution of the ROM image. This option has been locked and cannot be changed.

You have attempted to change a configuration setting that has been locked by your system administrator with the IBAUtil. This message can appear either from within Intel® PROSet’s Boot Agent tab when operating under Windows* or from the Configuration Setup Menu when operating in a stand-alone environment. If you think you should be able to change the configuration setting, consult your system administrator.

Источник

← Вернуться в раздел «Драйверы и прошивки BIOS»

Страницы: 12

Предыдущая тема: Дрова на nVidia-nForce-6A61BE19C-00

Форум Ru-Board.club — поднят 15-09-2016 числа. Цель — сохранить наследие старого Ru-Board, истории становления российского интернета. Сделано для людей.

Init/Boot/Loader Codes

• PXE-E00: Could not find enough free base memory.

PXE BaseCode and UNDI runtime modules are copied from FLASH or upper memory into the top of free base memory between 480K (78000h) and 640K (A0000h). This memory must be zero-filled by the system BIOS. If this memory is not zero-filled, the relocation code in the PXE ROMs will assume that this memory is being used by the system BIOS or other boot ROMs.

• PXE-E01: PCI Vendor and Device IDs do not match!

This message should never be seen in a production BIOS. When the system BIOS initializes a PCI option ROM, it is supposed to pass the PCI bus/device/function numbers in the AX register. If the PCI device defined in the AX register does not match the UNDI device, this error is displayed.

• PXE-E04: Error reading PCI configuration space.

This message is displayed if any of the PCI BIOS calls made to read the PCI configuration space return an error code. This should not happen with a production BIOS and properly operating hardware.

• PXE-E05: EEPROM checksum error.

This message is displayed if the NIC EEPROM contents have been corrupted. This can happen if the system is reset or powered down when the NIC EEPROM is being reprogrammed. If this message is displayed the PXE ROM will not boot.

• PXE-E06: Option ROM requires DDIM support.

This message should not be seen in a production BIOS. PCI option ROMs must always be installed as DDIM option ROMs (they must be installed into read/write upper memory).

• PXE-E07: PCI BIOS calls not supported.

This message should not be seen in a production BIOS. PCI BIOS must have PCI BIOS services.

• PXE-E08: Unexpected API error. API: xxxxh Status: xxxxh

This message is displayed if a PXE API returns a status code that is not expected by the runtime loader.

• PXE-E09: Unexpected UNDI loader error. Status: xxxxh

This message is displayed if the UNDI runtime loader returns an unexpected status code.

ARP Codes

• PXE-E11: ARP timeout.

The PXE ROM will retry the ARP request four times. If it does not get any valid ARP replies, this message is displayed. This error can be caused by a number of network and service configuration errors. The most common are:

1. Setting the DHCP Class Identifier (option 60) on the DHCP server and installing the proxyDHCP on a separate machine.
2. Using routers that do not respond to ARP requests.

BIOS and BIS Codes

• PXE-E20: BIOS extended memory copy error. AH == nn

This message is displayed if the BIOS extended memory copy service returns an error. This should not happen on a production BIOS. The variable «nn» is the BIOS error code returned by the BIOS extended memory copy service (Int 15h, AH = 87h).

• PXE-E21: BIS integrity check failed.

This message is displayed if the BIS image in extended memory has been corrupted.

• PXE-E22: BIS image/credential validation failed.

The downloaded image and credential do not match the client key.

• PXE-E23: BIS initialization failed.

BIS could not be initialized. No more data is available.

• PXE-E24: BIS shutdown failed.

BIS could not be shutdown. No more data is available.

• PXE-E25: BIS get boot object authorization check flag failed.

Could not determine if BIS is enabled/disabled.

• PXE-E26: BIS free memory failed.

Could not release BIS allocated memory.

• PXE-E27: BIS get signature information failed.

Required BIS credential type information could not be determined.

• PXE-E28: BIS bad entry structure checksum.

BIS entry structure in the SM BIOS table is invalid.

TFTP/MTFTP Codes

• PXE-E32: TFTP open timeout.

TFTP open request was not acknowledged. Verify that the TFTP service is running.

• PXE-E35: TFTP read timeout.

Next TFTP data packet was not received.

• PXE-E36: Error received from TFTP server.

A TFTP error packet was received from the TFTP server.

• PXE-E38: TFTP cannot open connection.

A hardware error occurred when trying to send the TFTP open packet out.

• PXE-E39: TFTP cannot read from connection.

A hardware error occurred when trying to send a TFTP acknowledge packet out.

• PXE-E3A: TFTP too many packages.

This message can mean one of two things: PXE-E3B: TFTP error — File not found.
The requested file was not found on the TFTP server.

• PXE-E3C: TFTP error ? Access violation.

The request file was found on the TFTP server. The TFTP service does not have enough access rights to open/read the file.

• PXE-E3F: TFTP packet size is invalid.

The TFTP packet received is larger than 1456 bytes.

Using TFTP, you are trying to download a file that is larger than the allocated buffer.

Using MTFTP, you started downloading a file as a slave client, and the file increased in size when you became the master client.

BOOTP/DHCP Codes

• PXE-E51: No DHCP or proxyDHCP offers were received.

The client did not receive any valid DHCP, BOOTP, or proxyDHCP offers.

• PXE-E52: proxyDHCP offers were received. No DHCP offers were received.

The client did not receive any valid DHCP or BOOTP offers. The client did receive at least one valid proxyDHCP offer.

• PXE-E53: No boot filename received.

The client received at least one valid DHCP/BOOTP offer but does not have a boot filename to download.

• PXE-E55: proxyDHCP service did not reply to request on port 4011.

The client issued a proxyDHCP request to the DHCP server on port 4011 but did not receive a reply.

UNDI Codes

• PXE-E60: Invalid UNDI API function number.

An API being used by the BaseCode is not implemented in the UNDI ROM.

• PXE-E61: Media test failed, check cable.

Most likely the cable is not plugged in or connected. Could be a bad cable, NIC, or connection.

• PXE-E63: Error while initializing the NIC.

An error occurred while trying to initialize the NIC hardware. Try another NIC.

• PXE-E64: Error while initializing the PHY.

An error occurred while trying to initialize the PHY hardware. Try another NIC.

• PXE-E65: Error while reading the configuration data

An error occurred while reading the NIC configuration data. Try another NIC.

• PXE-E66: Error while reading the initialization data.

An error occurred while reading the NIC initialization data. Try another NIC.

• PXE-E67: Invalid MAC address.

The MAC address stored in this NIC is invalid. Try another NIC.

• PXE-E68: Invalid EEPROM checksum.

The EEPROM checksum is invalid. The contents of the EEPROM have been corrupted. Try another NIC.

• PXE-E69: Error while setting interrupt.

The interrupt hardware could not be configured. Try another NIC.

Bootstrap and Discovery Codes

• PXE-E74: Bad or missing PXE menu and/or prompt information.

PXE tags were detected, but the boot menu and/or boot prompt tags were not found/valid.

• PXE-E76: Bad or missing multicast discovery address.

Multicast discovery is enabled but the multicast discovery address tag is missing.

• PXE-E77: Bad or missing discovery server list.

Multicast and broadcast discovery are both disabled, or use server list is enabled, and the server list tag was not found/valid.

• PXE-E78: Could not locate boot server.

A valid boot server reply was not received by the client.

• PXE-E79: NBP is too big to fit in free base memory.

The NBP is larger than the amount of free base memory.

• PXE-E7A: Client could not locate a secure server.

This message is displayed when the client did not receive any security information from the boot server and BIS is enabled on the client.

• PXE-E7B: Missing MTFTP server IP address.

This message is displayed when the ROM did not receive any PXE discovery tags or proxyDHCP offers and the DHCP SIADDR field is set to 0.0.0.0.

APITest.0 and DOSUNDI.0 Codes

• PXE-E81: !PXE structure is invalid.

The !PXE structure is missing or has been corrupted.

• PXE-E82: PXENV+ structure is invalid.

The PXENV+ structure is missing or has been corrupted.

• PXE-E83: Invalid DHCP option format.

PXE discovery tags in the cached packets are not valid.

• PXE-E84: Could not get pointer to original packet storage.

The PXE ROM being used did not return pointers to its local cached packet storage. The API test bootstrap program will not work with this boot ROM.

• PXE-E85: Not enough extended memory.

The size of the RAMdisk image is larger that the available extended memory.

• PXE-E86: ENV RAMdisk image corrupted.

The bootstrap program was expecting a DOS diskette image. The first 512 bytes of the downloaded image did not contain a DOS boot signature.

• PXE-E87: Could not find selected boot item.

The cached discovery reply packet did not contain a PXE boot-item tag (PXE option 71).

• PXE-E88: Could not locate boot server.

The bootserver did not reply to the RAMdisk image discovery request. The RAMdisk image is not on the bootserver, or the bootserver service is not running.

• PXE-E89: Could not download boot image.

The RAMdisk image could not be downloaded. The RAMdisk image is not on the bootserver, or the TFTP service on the bootserver is not running.

Miscellaneous Codes

• PXE-EA0: Network boot canceled by keystroke.

User pressed ESC during DHCP/Discovery/TFTP.

BaseCode/UNDI Loader Codes

• PXE-EC1: BaseCode ROM ID structure was not found.

UNDI boot module could not find the BaseCode ROM ID structure. If there is a BaseCode ROM image in the system, it has probably been corrupted.

• PXE-EC3: BaseCode ROM ID structure is invalid.

The BaseCode ROM ID structure is invalid. The BaseCode ROM image has probably been corrupted.

• PXE-EC4: UNDI ROM ID structure was not found.

The BaseCode loader module could not locate the UNDI ROM ID structure.

• PXE-EC5: UNDI ROM ID structure is invalid.

The UNDI ROM image has probably been corrupted.

• PXE-EC6: UNDI driver image is invalid.

The UNDI ROM image has probably been corrupted.

• PXE-EC8: !PXE structure was not found in UNDI driver code segment.

The UNDI ROM image has probably been corrupted or has not been initialized by the BIOS. This error is most often caused by one of three things:

1. A NIC image was programmed into a BIOS when a .LOM image should have been used.
2. The memory allocated by the POST Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
3. The UNDI_Loader structure was not properly initialized during option ROM initialization.

• PXE-EC9: PXENV+ structure was not found in UNDI driver code segment.

The UNDI ROM image has probably been corrupted or has not been initialized by the BIOS. This error is most often caused by one of three things:

1. A NIC image was programmed into a BIOS when a .LOM image should have been used.
2. The memory allocated by the POST Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
3. The UNDI_Loader structure was not properly initialized during option ROM initialization.

 What Are The PXE Error Codes?

Article: 138

Applies to: All releases

Init/Boot/Loader Codes
• 	PXE-E00 Could not find enough free base memory. PXE BaseCode and UNDI runtime modules are copied from FLASH or upper memory into the top of free base memory between 480K (78000h) and 640K (A0000h). This memory must be zero filled by the system BIOS. If this memory is not zero filled, the relocation code in the PXE ROMs will assume that this memory is being used by the system BIOS or other boot ROMs.
• 	PXE-E01: PCI Vendor and Device IDs do not match! This message should never be seen in a production BIOS. When the system BIOS initializes a PCI option ROM, it is supposed to pass the PCI bus/device/function numbers in the AX register. If the PCI device defined in the AX register does not match the UNDI device, this error is displayed.
• 	PXE-E04: Error reading PCI configuration space. This message is displayed if any of the PCI BIOS calls made to read the PCI configuration space return an error code. This should not happen with a production BIOS and properly operating hardware.
• 	PXE-E05: EEPROM checksum error. This message is displayed if the NIC EEPROM contents have been corrupted. This can happen if the system is reset or powered down when the NIC EEPROM is being reprogrammed. If this message is displayed the PXE ROM will not boot.
• 	PXE-E06: Option ROM requires DDIM support. This message should not be seen in a production BIOS. PCI option ROMs must always be installed as DDIM option ROMs (they must be installed into read/write upper memory).
• 	PXE-E07: PCI BIOS calls not supported. This message should not be seen in a production BIOS. PCI BIOS must have PCI BIOS services.
• 	PXE-E08: Unexpected API error. API: xxxxh Status: xxxxh. This message is displayed if a PXE API returns a status code that is not expected by the runtime loader.
• 	PXE-E09: Unexpected UNDI loader error. Status: xxxxh. This message is displayed if the UNDI runtime loader returns an unexpected status code.

ARP Codes
• 	PXE-E11: ARP timeout. The PXE ROM will retry the ARP request four times, if it does not get any valid ARP replies, this message is displayed. There are several possible causes:
• 	Setting the DHCP Class Identifier (option 60) on the DHCP server and installing the proxyDHCP on a separate machine.
• 	Using routers that do not respond to ARP requests.
• 	A situation that may lead to this error is with ProLiant BL p-Class blade servers connected to a ProLiant BL p-Class GbE Interconnect Switch with Port Trunking (802.3ad) enabled uplinked to another switch where port trunking is not enabled, and perhaps instead, the customer inadvertently enabled VLAN trunking.

The GbE switch options are based on IEEE terminology which is sometimes different than Cisco terminology. The Port Trunking option on the GbE switch is meant for the bonding together of multiple ports (802.3ad) for faster throughput and reliability. The Cisco term for this is etherchannel. The term "trunking" on a Cisco switch means vlan tagging and is often confused with IEEE port trunking. The two are not the same and cannot be used on one switch without the same option being enabled on both switches.

To resolve this issue, correct the port trunk configuration on both switches.
• 	After certain deployment operations, the server's MAC address might be set to 0.

To resolve this issue, apply the SoftPaq for Network Adapter Boot Code and PXE Firmware refered to in the Knowledge Base article Minimum Firmware Requirements For Target Servers (Article 200).

BIOS and BIS Codes
• 	PXE-E20: BIOS extended memory copy error. AH == nn This message is displayed if the BIOS extended memory copy service returns an error. This should not happen on a production BIOS. nn is the BIOS error code returned by the BIOS extended memory copy service (Int 15h, AH = 87h).
• 	PXE-E21: BIS integrity check failed. This message is displayed if the BIS image in extended memory has been corrupted.
• 	PXE-E22: BIS image/credential validation failed. The downloaded image and credential do not match the client key.
• 	PXE-E23: BIS initialization failed. BIS could not be initialized. No more data is available.
• 	PXE-E24: BIS shutdown failed. BIS could not be shutdown. No more data is available.
• 	PXE-E25: BIS get boot object authorization check flag failed. Could not determine if BIS is enabled/disabled.
• 	PXE-E26: BIS free memory failed. Could not release BIS allocated memory.
• 	PXE-E27: BIS get signature information failed. Required BIS credential type information could not be determined.
• 	PXE-E28: BIS bad entry structure checksum. BIS entry structure in the SM BIOS table is invalid.

TFTP/MTFTP Codes
• 	PXE-E32: TFTP open timeout. The PXE client was able to get a DHCP address and a boot file name, but timed out when attempting to download the boot file using TFTP or MTFTP. To resolve this issue, check each of the following network configuration items:
• 	This message is sometimes displayed, and the operation is retried, allowing for a successful download of the boot image. The message Transferring control to DOS boot diskette image... indicates that the boot file was successfully downloaded and the PXE boot has succeeded. In this case, no action is needed to correct the problem.
• 	By default, the Altiris PXE server is configured to use multicast TFTP. If multicast is disabled by the switches in the environment, either enable multicast (ports 1758 and 1759) or change the configuration of the PXE server to use regular TFTP (port 69).
• 	Verify that the Altiris MTFTP Service is running on the Deployment Server.
• 	PXE-E35: TFTP read timeout. Next TFTP data packet was not received.
• 	PXE-E36: Error received from TFTP server. A TFTP error packet was received from the TFTP server.
• 	PXE-E38: TFTP cannot open connection. A hardware error occurred when trying to send the TFTP open packet out.
• 	PXE-E39: TFTP cannot read from connection. A hardware error occurred when trying to send a TFTP acknowledge packet out.
• 	PXE-E3A: TFTP too many packages. This message can mean one of two things:
• 	You are trying to download a file using TFTP that is larger than the allocated buffer.
• 	You started downloading a file as a slave client using MTFTP and the file increased in size when you became the master client.
• 	PXE-E3B: TFTP error - File not found. The requested file was not found on the TFTP server.
• 	PXE-E3C: TFTP error - Access violation. The request file was found on the TFTP server. The TFTP service does not have enough access rights to open/read the file.
• 	PXE-E3F: TFTP packet size is invalid. The TFTP packet received is larger than 1456 bytes.

BOOTP/DHCP Codes
• 	PXE-E51: No DHCP or proxyDHCP offers were received. The client did not receive any valid DHCP, BOOTP or proxyDHCP offers. To resolve this issue, check each of the following network configuration items:
• 	DHCP services are not available on the network to which the PXE-enabled NIC is connected.
• 	A DHCP proxy or IP helper address is not configured for the subnet on which the PXE client is connected.
• 	The switch port connected to the PXE NIC is running Spanning Tree Protocol, EtherChannel Protocol, or Port Aggregation Protocol and is thus not activated immediately when a link is detected. This forces the DHCP request from the PXE client to timeout.
• 	DHCP is available on the network, but PXE is not.
• 	The network cable is not attached to the PXE-enabled NIC on the target server.
• 	PXE-E52: proxyDHCP offers were received. No DHCP offers were received. The client did not receive any valid DHCP or BOOTP offers. The client did receive at least one valid proxyDHCP offer.
• 	PXE-E53: No boot filename received. The client received at least one valid DHCP/BOOTP offer, but does not have a boot filename to download. There are several possible causes:
• 	The DHCP Server and the PXE Server were located on the same server, but one of them was moved to a different server. This would result in an incorrect PXE Server configuration.

To resolve this issue, reinstall the PXE Server component of the Altiris Deployment Solution.
• 	The DHCP relay agent, either a Proxy DHCP Server or a switch configured with helper addresses, is not configured correctly. For example, if DHCP and PXE are on separate servers, the DHCP relay agent needs to have both addresses in its configuration.

To resolve this issue, correct the DHCP relay agent configuration.
• 	If the Microsoft DHCP service is installed on the PXE server, but is disabled or unconfigured, Altiris PXE Setup configures PXE to work with the local DHCP service (even if the DHCP service is disabled). This causes the PXE server to not respond to PXE clients that get a DHCP address from DHCP services running elsewhere on the network.

To resolve this issue, remove Microsoft DHCP services from the PXE server and reinstall the PXE Server component of the Altiris Deployment Solution.
• 	PXE-E55: proxyDHCP service did not reply to request on port 4011. The client issued a proxyDHCP request to the DHCP server on port 4011 and did not receive a reply.

UNDI Codes
• 	PXE-E60: Invalid UNDI API function number. An API being used by the BaseCode is not implemented in the UNDI ROM.
• 	PXE-E61: Media test failed, check cable. Most likely the cable is not plugged in or connected. Could be a bad cable, NIC or connection.
• 	PXE-E63: Error while initializing the NIC. An error occurred while trying to initialize the NIC hardware. Try another NIC.
• 	PXE-E64: Error while initializing the PHY. An error occurred while trying to initialize the PHY hardware. Try another NIC.
• 	PXE-E65: Error while reading the configuration data. An error occurred while reading the NIC configuration data. Try another NIC.
• 	PXE-E66: Error while reading the initialization data. An error occurred while reading the NIC initialization data. Try another NIC.
• 	PXE-E67: Invalid MAC address. The MAC address stored in this NIC is invalid. Try another NIC.
• 	PXE-E68: Invalid EEPROM checksum. The EEPROM checksum is invalid. The contents of the EEPROM have been corrupted. Try another NIC.
• 	PXE-E69: Error while setting interrupt. The interrupt hardware could not be configured. Try another NIC.

Bootstrap and Discovery Codes
• 	PXE-E74: Bad or missing PXE menu and/or prompt information. PXE tags were detected but the boot menu and/or boot prompt tags were not found/valid.
• 	PXE-E76: Bad or missing multicast discovery address. Multicast discovery is enabled but the multicast discovery address tag is missing.
• 	PXE-E77: Bad or missing discovery server list. Multicast and broadcast discovery are both disabled, or use server list is enabled, and the server list tag was not found/valid.
• 	PXE-E78: Could not locate boot server. A valid boot server reply was not received by the client. Several possible causes are
• 	The PXE image is not correct for the target because a job that contains a task that is to run in a specific automation environment cannot be run on the target.
• 	The Virtualization Technology BIOS option may not be set on an Intel-based server running VMware ESX and a Windows 64-bit guest is being deploying to one of its virtual machines.
• 	PXE-E79: NBP is too big to fit in free base memory. The NBP is larger than the amount of free base memory.
• 	PXE-E7A: Client could not locate a secure server. This message is displayed when the client did not receive any security information from the boot server and BIS is enabled on the client.
• 	PXE-E7B: Missing MTFTP server IP address. This message is displayed when the ROM did not receive any PXE discovery tags or proxyDHCP offers and the DHCP SIADDR field is set to 0.0.0.0.

Miscellaneous Codes
• 	PXE-EA0: Network boot canceled by keystroke. User pressed Esc or Ctrl-C during DHCP/Discovery/TFTP.

BaseCode/UNDI Loader Codes
• 	PXE-EC1: BaseCode ROM ID structure was not found. UNDI boot module could not find the BaseCode ROM ID structure. If there is a BaseCode ROM image in the system, it has probably been corrupted.
• 	PXE-EC3: BaseCode ROM ID structure is invalid. The BaseCode ROM ID structure is invalid. The BaseCode ROM image has probably been corrupted.
• 	PXE-EC4: UNDI ROM ID structure was not found. The BaseCode loader module could not locate the UNDI ROM ID structure.
• 	PXE-EC5: UNDI ROM ID structure is invalid. The UNDI ROM image has probably been corrupted.
• 	PXE-EC6: UNDI driver image is invalid. The UNDI ROM image has probably been corrupted.
• 	PXE-EC8: !PXE structure was not found in UNDI driver code segment. The UNDI ROM image has probably been corrupted, or has not been initialized by the BIOS. This error is most often caused by one of three things:
• 	A .NIC image was programmed into a BIOS when a .LOM image should have been used.
• 	The memory allocated by the POST Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
• 	The UNDI_Loader structure was not properly initialized during option ROM initialization.
• 	PXE-EC9: PXENV+ structure was not found in UNDI driver code segment. The UNDI ROM image has probably been corrupted, or has not been initialized by the BIOS. This error is most often caused by one of three things:
• 	A .NIC image was programmed into a BIOS when a .LOM image should have been used.
• 	The memory allocated by the POST Memory Manager ($PMM) during PXE option ROM initialization has been corrupted or erased before PXE option ROM boot.
• 	The UNDI_Loader structure was not properly initialized during option ROM initialization. 







page source: http://h18013.www1.hp.com/products/servers/management/rdp/knowledgebase/00000138.html

PCI configuration space could not be read. Machine is probably not PCI compliant. The Boot Agent

was unable to read one or more of the adapter’s PCI configuration registers. The adapter may be

misconfigured, or the wrong Boot Agent image may be installed on the adapter. The Boot Agent

returns control to the BIOS and not attempt to remote boot. Try to update the flash image. If this does

not solve the problem, contact your system administrator or HP Customer Support.

PXE-E05: The LAN adapter’s configuration is corrupted or has not been initialized. The Boot Agent

cannot continue.

The adapter’s EEPROM is corrupted. The Boot Agent determined that the adapter EEPROM checksum

is incorrect. The agent will return control to the BIOS and not attempt to remote boot. Try to update

the flash image. If this does not solve the problem, contact your system administrator or HP Customer

Support.

PXE-E06: Option ROM requires DDIM support.

The system BIOS does not support DDIM. The BIOS does not support the mapping of the PCI

expansion ROMs into upper memory as required by the PCI specification. The Boot Agent cannot

function in this system. The Boot Agent returns control to the BIOS and does not attempt to remote

boot. You may be able to resolve the problem by updating the BIOS on your system. If updating

your system’s BIOS does not solve the problem, contact your system administrator or HP customer

support to resolve the problem.

PXE-E07: PCI BIOS calls not supported.

BIOS-level PCI services not available. Machine is probably not PCI compliant.

PXE-E09: Unexpected UNDI loader error. Status == xx

The UNDI loader returned an unknown error status. xx is the status returned.

PXE-E20: BIOS extended memory copy error.

BIOS could not move the image into extended memory.

PXE-E20: BIOS extended memory copy error. AH == xx

Error occurred while trying to copy the image into extended memory. xx is the BIOS failure code.

PXE-E51: No DHCP or BOOTP offers received.

The Boot Agent did not receive any DHCP or BOOTP responses to its initial request. Be sure that

your DHCP server (and/or proxyDHCP server, if one is in use) is properly configured and has

sufficient IP addresses available for lease. If you are using BOOTP, be sure that the BOOTP service is

running and is properly configured.

PXE-E53: No boot filename received.

The Boot Agent received a DHCP or BOOTP offer, but has not received a valid filename to

download. If you are using PXE, please check your PXE and BINL configuration. If you are using

BOOTP, be sure that the TFTP service is running and that the specific path and filename are correct.

PXE-E61: Media test failure.

The adapter does not detect link. Be sure that the cable is good and is attached to a working hub or

switch. The link light visible from the back of the adapter should be lit.

PXE-EC1: Base-code ROM ID structure was not found.

No base code can be located. An incorrect flash image is installed or the image has become

corrupted. Try to update the flash image.

PXE-EC3: BC ROM ID structure is invalid.

Adapter configurations 76

Не так давно я уже опубликовал статью по звуковым ошибкам BIOS. Но кроме звука, ошибка может дублироваться на экране компьютера в виде текста. При условии, что видеокарта и монитор в исправном состоянии.

Как я уже писал, во время загрузки компьютера, BIOS производит процедуру самотестирования (Power-On Self Test – POST). В короткий промежуток времени, производится общая диагностика системы и если есть проблемы, система вас оповестит об этом. При удачном прохождении проверки, начнется загрузка операционной системы.

В прошлый раз я разобрал звуковые сигналы, символизирующие ошибку, но не у всех компьютеров есть динамик, который воспроизводит последовательность сигналов ошибки. Для таких случаев есть текстовое отображение сообщения об ошибке. Да и прочитать сообщение, что от вас хочет компьютер, наверное, проще, чем прислушиваться к сигналам.

У разных производителей сообщение об ошибке может различаться, поэтому я выбрал только самых популярных производителей. Все ошибки собраны в виде таблиц, сообщение на английском языке и перевод.

Текстовые сообщения об ошибках
AWARD BIOS

Текстовые сообщения об ошибках
Phoenix BIOS

Всем удачи!