bomzzz
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 Boot servers
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 Installation
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 <ENTER>.
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.
3 Boot servers
3.1 PXELINUX
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.
4.2 BIOS Codes
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.
***End of Readme file***
|
Всего записей: 13343 | Зарегистр. 13-01-2008 | Отправлено: 12:07 01-02-2011 | Исправлено: bomzzz, 12:08 01-02-2011 |
|
