(C)Copyright 2003 Marvell(R).
All rights reserved.
===========================================================================
sk98ypxe.txt created 23-Jul-2003
Readme File for sk98ypxe.rom v1.08
PXE ROM Yukon
This file contains
1 Overview
2 Installation
2.1 Installation of binary
2.2 Removal of binary
3 Boot process and configuration
3.1 Bios Boot Specification (BBS)
3.2 INT 18h
3.3 INT 19h
4 Boot servers
4.1 PXELINUX
4.2 WINDOWS 2000/XP Remote Installation Services (RIS)
5 PXE Client Status/Error Codes
5.1 Init/Boot/Loader Codes
5.2 BIOS Codes
5.3 Base-Code/UNDI Loader Codes
===========================================================================
1 Overview
===========
sk98ypxe.rom is the PXE support software for the SysKonnect SK-98xx V2.0
and SK-95xx V2.0 Gigabit Ethernet Adapters.
***
2 Installation
===============
2.1 Installation of binary
---------------------------
sk98ypxe.rom must be flashed to the network adapter using the SK98DIAG
diagnostics 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 (sk98ypxe.rom).
4. Press <ENTER>.
5. After the process is finished, exit the diagnostics utility.
PXE support is now installed on the network adapter.
2.2 Removal of binary
----------------------
To disable all actions of sk98ypxe.rom, the network adapter FLASH PROM
must be cleared using the SK98DIAG diagnostics
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 diagnostics utility.
PXE support is now removed from the network adapter.
***
3 Boot process and configuration
=================================
This chapter describes different boot mechanisms for sk98ypxe.rom the
user can select at each power-up of the PC.
If sk98ypxe.rom is installed on the network adapter, it is not
automatically selected as boot device by the BIOS. It depends on the
ability and the mechanisms of the BIOS to change the boot sequence.
There are three boot mechanisms during power-up of the BIOS ('Press
<CTRL>+<B> to choose a boot method for SK Boot Agent'). They are
described below. Consult your BIOS manual to find out which method is
suitable.
***
3.1 Bios Boot Specification (BBS)
----------------------------------
This is the default method if no selection is made. It is suitable for
BIOSes that support BBS ('Bios Boot Specification'). The BIOS setup
contains an entry similar to 'Boot Sequence'(depending on the BIOS
manufacturer) where you can define the order of the boot devices.
To configure BBS, proceed as follows:
1. Enter the BIOS setup during the boot operation.
If sk98ypxe.rom is correctly installed you will find the entry
'SK Boot Agent' in the boot device list.
2. Make 'SK Boot Agent' the first entry.
3. Restart your computer.
***
3.2 INT 18h
------------
This method is suitable for older BIOSes that do not support BBS but do
support boot device reordering. Older BIOSes often use INT18h to boot
with a network adapter.
To configure INT18, proceed as follows:
1. Enter the BIOS setup during the boot operation.
2. Change the boot sequence: make the network adapter the first boot
device.
3. Restart your computer.
4. Press <CTRL>+<B> when prompted during the boot operation.
5. Select <2> for INT18h.
***
3.3 INT 19h
------------
Select this method, if BBS and INT18 do not work with your BIOS.
sk98ypxe.rom replaces the standard boot method for the hard disk and
tries to boot from the network, regardless of any boot sequence in the
BIOS setup.
To configure INT19, proceed as follows:
1. Start your computer.
2. Press <CTRL>+<B> when prompted during the boot operation.
3. Select <3> for INT19h.
***
4 Boot servers
===============
4.1 PXELINUX
-------------
If you use LINUX as bootserver, you must include the SysKonnect SK-98xx
V2.0 and SK-95xx V2.0 Gigabit Ethernet 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-98xx V2.0 and SK-95xx
V2.0 Gigabit Ethernet 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-98xx V2.0
and SK-95xx V2.0 Gigabit Ethernet 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 file NETSK9X.INF from the network adapter driver CD to the
directory i386 of the image directory on the server.
3. Copy the file SK98W2K.SYS (2000) or SK98WXP.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 SysKonnect SK-98xx V2.0 and SK-95xx V2.0
Gigabit Ethernet Adapters driver CD to install and configure the network
adapter when WINDOWS setup asks for it.
***
5 PXE Client Status/Error Codes
================================
5.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.
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: EPXE-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.
***
5.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.
***
5.3 Base-Code/UNDI Loader Codes
--------------------------------
NOTE: The base-code ROM is part of sk98ypxe.rom.
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.
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***
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.