skfpuw21.htm created 30-Jun-1999

Readme File for skfp v1.08
SK-NET FDDI PCI

This file contains




(1) Overview

This README explains how to use the Unixware 2.1 driver 'skfp' for your
network adapter.

Chapter 2 contains a list of all network adapters which are supported by this
driver.

Chapter 3 describes the installation process.

Chapter 4 explains how to configure the adapter.


(2) Supported Adapters

The network driver 'skfp' supports the following network adapters:

	*) SK-NET FDDI PCI series


(3) Installation

To install the network driver on your system follow the steps below:

Step 0: Install the network adapter card and boot the system.

Step 1: Use the "pkginfo" command to check whether the following patches
	are installed on your system:
	- ptf3152c  APIC I/O fix.
	- ptf3254   PCI device supplement.
	- ptf3089   NFS fix.
	- ptf3131b  Virtual memory subsystem fixes.
	- ptf3280l  Networks supplement.

NOTE:
- Type "pkginfo | grep ptf" to see all installed patches.
- All patches and documentation about those can be obtained from the ftp site:
		"ftp://ftp.sco.com/UW21"
- UnixWare 2.1.3 includes all patches mentioned above.

Step 2: Install the driver via the 'niccfg' utility.

Step 3: Select "Install driver from IHV diskette".

Step 4: Before leaving the 'niccfg' program you need to make a number of
	selections regarding the adapters configuration. These selections must
	be made for each adapter installed on your system. The default value
	is the first in the list of possible values. To select the default
	values, press "F2" followed by "Enter" for each selected parameter.

Step 5: To install the TCP/IP protocol, run "/etc/inet/menu".
	Select the adapter for which TCP/IP is to be configured and enter the
	required information. Please ensure that the FDDI frame type is
	selected.


(4) Configuration

For the first configuration of the driver you will be prompted during the
installation process using 'niccfg' (see above). If you want to reconfigure
one or more installed boards you can use the 'dcu' utility. To do so select
'Hardware Configuration' first, then select the board that needs to be
reconfigured and press F7 for the advanced configuration.


(5) History

v1.08
    New features:
	None.
    Problems fixed:
	- The receive path sometimes hung, when too many packets were received
	  in a short time.
    Known limitations:
	None.

v1.07
    New features:
	None.
    Problems fixed:
	- Frames were doubled when a stream was bound to an LLC SAP and the
	  SNAP OUI was 0 by chance.
    Known limitations:
	None.
v1.06
    New features:
	None.
    Problems fixed:
	On some hardware errors the system paniced instead of resetting the
	board.
    Known limitations:
	None.
v1.05
    New features:
	- Now at most 64 streams may be bound to a board.
    Problems fixed:
	None.
    Known limitations:
	None.
v1.04
    New features:
	- The LED's behaviour changed.
	- When a stream is reloaded the multicast table will be too.
    Problems fixed:
	- Dual homing with multiple adapters didn't work.
	- Possible problem when becoming beaconer.
	- Station disabled SMT packets receiver, if multiple directed beacons
	  were received.
	- Station could not receive any packets if more than 28 multicast
	  addresses were set or if promiscious mode was selected. This led
	  to a hung situation.
    Known limitations:
	None.
v1.03
    New features:
	None.
    Problems fixed:
	- Packets containing many fragments were discarded.
    Known limitations:
	None.
v1.02
    New features:
	- MTU is now configurable.
	- Add support for new FDDI PCI 64bit/66Mhz card.
    Problems fixed:
	None.
    Known limitations:
	None.
v1.01
    New features:
	None.
    Problems fixed:
	- Multicast address table was not correctly maintained.
	- LLC TEST frames were not handled correctly.
	- SBA/ESS RAF responses were not sent correctly.
	- When configuring SBA and ESS the message:
	  "skfp0: HWM: encoding error async TX queue"
	  could appear.
	- The system could hang, if promiscous mode is selected.
    Known limitations:
	None.
v1.00
    New features:
	None.
    Problems fixed:
	None.
    Known limitations:
	None.

*** End of readme file ***