©Copyright 2003-2005 Marvell®.
All rights reserved..
sk98pxe.htm created 22-Jul-2005
Readme File for sk98pxe.rom v4.12.2.3
PXE ROM Yukon
This file contains
SK98PXE is the PXE support software for the SysKonnect SK-95xx V2.0,
SK-98xx V2.0, SK-9Exx and SK-9Sxx Adapters.
2.1 Installation of binary
sk98pxe.rom must be flashed to the network adapter using the SK98DIAG
utility.
To flash the binary to the network adapter, proceed as follows:
1. Start SK98DIAG.
2. Select 'FLASH PROM ...' > 'Load FLASH PROM from file".
3. Type the path and filename of the binary (sk98pxe.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 sk98pxe.rom, the network adapter FLASH PROM
must be cleared using the SK98DIAG utility.
To clear the Flash PROM, proceed as follwows:
1. Start SK98DIAG.
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.
During startup of SK98PXE it will take the port that first gets a
link for further operation. It will not switch to the other port in case
of link status changes.
4.1 PXELINUX
If you use LINUX as bootserver, you must include the SysKonnect SK-95xx
V2.0, SK-98xx V2.0, SK-9Exx and SK-9Sxx Adapters driver in the kernel of
the downloadable image. For details, please refer to the PXELINUX manual.
4.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 SysKonnect SK-95xx V2.0, SK-98xx V2.0,
SK-9Exx and SK-9Sxx Adapters. 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 SysKonnect SK-95xx
V2.0, SK-98xx V2.0, SK-9Exx and SK-9Sxx Adapters 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 driver's .INF file from the network adapter driver CD to the
directory i386 of the image directory on the server.
3. Copy the driver's .SYS file 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 SysKonnect SK-95xx V2.0, SK-98xx V2.0, SK-9Exx
and SK-9Sxx Adapters driver CD to install and configure the network
adapter when WINDOWS setup asks for it.
If you have installed SK98PXE on the adapter but it does not show up at
boot time, enter the BIOS setup and look for the boot order setup. It is
called 'Boot', 'Boot setup' or something similar. Follow these steps
below to enable booting with SK98PXE:
1. Enter the BIOS setup during the boot operation.
If SK98PXE is correctly installed you will find the entry
'B# D# SK PXE' in the boot device list.
2. Change the boot device list: Set 'B# D# SK PXE'
as the first entry. 'B#' and 'D#' show the bus number and device
(slot) number of the PCI slot, where the hardware is plugged in.
3. Restart your computer.
If this does not help or the menu entry is not there, try reinstalling the
binary.
6.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.
6.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.
6.3 Base-Code/UNDI Loader Codes
NOTE: The base-code ROM is part of sk98pxe.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***