+++++++++++++++++++++++++++++++++              ++++
           ++++++++++++++++++++++++++++++++++++           +++++++
          +++++++++++++++++++++++++++++++++++++         ++++++++
          ++++++++++++++++++++++++++++++++++++        ++++++++
          +++++++++++++++++++++++++++           ++++++++
          +++++++++++++++++++++++++++++       ++++++++
           +++++++++++++++++++++++++++++     ++++++++
             +++++++++++++++++++++++++++     ++++++++
    ++++++++++++++++++++++++++++++++++++        ++++++++
   +++++++++++++++++++++++++++++++++++++         ++++++++
   ++++++++++++++++++++++++++++++++++++           ++++++++
    +++++++++++++++++++++++++++++++++               +++++

(C)Copyright 1998-1999 SysKonnect,
a business unit of Schneider & Koch & Co. Datensysteme GmbH.
All rights reserved

Readme File for SKFP.o
	v1.04 (19990514)

May 14, 1999

This file contains

(1) Overview

This README explains how to use the driver 'skfp' for Linux with your
network adapter. Currently, only Linux on X86 processors is supported.

Chapter 2: Contains a list of all network adapters that are supported by
	   this driver.

Chapter 3: Gives some general information.

Chapter 4: Describes the manual (first time) installation process.

Chapter 5: Describes adapter inclusion in the boot process.

Chapter 6: Describes common problems and solutions.

Chapter 7: History of development.

(2) Supported Adapters

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

	*) SK-NET FDDI PCI series

(3) General Information

You must log in as 'root' to install the driver.

The package contains:
- this readme in ASCII amd HTML format
- the driver source code and a SysKonnect specific FDDI library,
  for compiling the driver on your kernel version.

A kernel with FDDI support (2.0.25 and above) is required.
The driver supports both 2.0.x and 2.2.x kernel versions.

(4) Installation

The following steps describe the actions that are required to install
the driver and to start it manually. These steps should be carried
out for the initial driver setup and once confirmed to be ok, can
be included in the system start which is described in the next

NOTE 1: You must have 'root' access to the system to perform
        the following tasks.
NOTE 2: If anything goes wrong, check again all the steps you did
        and also read the TROUBLESHOOTING section below.

1) If you got this driver on a CD, copy the driver directory
   on you harddisk (cp -r <driver-directory> <harddisk-path>).
   If you downloaded it from the web, you probably have already
   unpacked it to you harddisk (tar xvfz skfplin.tgz).
   You now have the driver directory with the readme-files and
   a subdirectory 'src'.

2) You have to compile the driver. To do this, change to the 'src'
   directory and enter 'make'.
   After make has finished, the file 'skfp.o' will exist in this
   'src' directory and can be used as follows.
   During make, you will see a message that your kernel source
   has been patched. This is necessary to make two FDDI function
   available for the driver which are not exported by default.
   NOTE 1: if you see a message saying that you do not have permission
           to patch the kernel, you are probably not logged in as 'root'.
	   Login as root and retry.
   NOTE 2: If you compiled the driver before, enter 'make clean'
           before 'make'.
   NOTE 3: Depending on your gcc compiler version, the compilation
           for kernel version 2.0.36 may fail with a warning.
	   The warning says that you need a patch for the kernel
	   to compile correctly and gives you an internet address where
	   you can get this patch. Install it and retry.
3) Rebuild and reinstall the linux kernel.
   If your kernel is not configured with 'FDDI driver support',
   you must first enable this option in the kernel configuration
   menu. Your kernel must also have 'loadable module support' and
   'Kernel daemon support (...)' enabled.
   Reboot your system with the new kernel.
   NOTE: Kernel versions newer than 2.0.36 or 2.2.3 may already
         incorporate the kernel patch described in 2). In this case,
	 you will not get the corresponding message and you do not
	 need to rebuild your kernel if your old one already has FDDI,
	 loadable module and kernel daemon upport enabled.

4) Load the module manually by entering:
       insmod skfp
   If the SysKonnect FDDI PCI adapter is installed in your
   computer and you have a /proc filesystem, running the command
   'more /proc/net/dev' should produce an output containing a
   line with the following format:
       fddi0:    0    0 ...
   which means that your adapter has been found and initialized.
   NOTE: If you have more than one SysKonnect FDDI PCI adapter,
   the adapters will be listed as 'fddi1', 'fddi2', etc.
   For each adapter, repeat the steps 5) and 6).

5) Select an IP address and assign it to the respective adapter by
       ifconfig fddi0 <ip-address>
   This causes the adapter to attach to the FDDI ring. The green
   LED corresponding to the port at the adapter should now 
   be active.
   NOTE: If you are in doubt about IP addresses, ask your network
   administrator for assistance.

6) This step is only required for the 2.0.x kernel series. The 2.2.x
   kernel do this automatically:
   Add a route to the routing table with the following command:
       route add -net <netaddress> netmask <netmask> dev fddi0
   Using your IP-address, you can normally get your netaddress by
   replacing the host part with '0'. For a class C address, the
   netmask is normally ''.

7) Your adapter should now be fully operational.
   Use 'ping <otherstation>' to verify the connection to other
   computers on your network.
   By entering 'ifconfig', you can check the number of packets send
   and received by your adapter and additional some other information
   regarding the adapter configuration.
   NOTE: 'ifconfig' will also show the hardware address of your adapter
   in the form 'HWaddr 00-00-5A-xx-xx-xx-xx-xx-...'. Only the first
   six bytes of this address are valid.

8) The driver module can be stopped and unloaded using the following
       ifconfig fddi0 down
       rmmod skfp

(5) Inclusion of the adapter in system start

Since a large number of different Linux distributions are 
available, we are unable to describe a general installation procedure
for the driver module. However, we will provide some help for the 
manual inclusion in the system startup as well as a description of the
installation with two distributions (SuSE and RedHat).
For other distributions, we recommend you read these descriptions
and also refer to the distribution's manual for information regarding
the network configuration.
This chapter assumes that you have at least executed steps 1-3 as 
described in the previous chapter.


To initialize the adapter at system start, you must add the
commands from the previous chapter (steps 4-6) to one of the
system startup scripts. Read the man pages for 'init' and
'inittab' to learn more about the boot process and to locate the
correct script.
You will need to add the full path to the driver module in the 


1) Copy the driver module file skfp.o to your modules directory:
       cp skfp.o /lib/modules/<kernelversion>/net/
   If this directory does not yet exist, please create it.

2) In Linux, modules can be loaded automatically by a kernel
   daemon if required. To make the new module known to
   this daemon, you must add one line to its configuration
   file (/etc/conf.modules):
       alias fddi0 skfp
   This identifies the module (skfp.o) which must be loaded if
   any accesses are made to the device fddi0.

3) Continue with the section for the distribution in use.


1) Call the SuSE setup tool, 'yast'. Go to:
       System administration
         Network configuration
           Network base configuration
   Proceed to the windows asking "... TCP/IP only in loopback ..."
   and select 'No'.
   Enter the IP address. For type of network, select 'eth0'.
   NOTE: Since this version of yast does not directly support FDDI,
   you must select ethernet (eth0) here and make some manual
   changes later.
   Enter the netmask and the gateway address (if required).
   Continue with choices appropriate for your system. Once the
   configuration is completed, quit yast.

2) Edit the file /etc/rc.config.
   You must change the line
   and save the file.

3) Run '/sbin/SuSEconfig' to incorporate the changes from
   the rc.config file into the startup scripts.

4) Reboot your computer and test if your adapter is working.

5.4 SuSE DISTRIBUTION (5.2 and above)

1) Call the SuSE setup tool, 'yast'. Go to:
       System administration
         Network configuration
           Network base configuration
   Select the first unused line, press F5 and select 'FDDI'.
   Press F6 and enter the required addresses. Do not forget to
   activate the device by pressing F4.
   Press F10 to save the new configuration and quit the
   setup tool.

2) Reboot your computer and test if your adapter is working.

5.5 RedHat DISTRIBUTION (5.0)

1) To use the RedHat configuration tool, you must have XWindow
   running (NOTE: the configuration tools seems to require a 
   screen mode with at least 256 colors).
   Start X11 as root or change to root user in a xterm window
   with 'su'.
   Call 'control-panel' and select 'network configuration'.
   After a short moment, the network configuration window
   is displayed.
   Select 'Interfaces',then 'Add'.
   NOTE: Since this version of the configuration tool does not
   directly support FDDI, you must select 'Ethernet' here.
   Press 'Ok'. For step 5, we assume that the new device is
   the first one, in which case it will be called 'eth0'.
   Insert the IP address in the appropriate field and
   press ENTER. The network address and the netmask will be
   automatically inserted. Make a note of these since you
   will need them in step 4. Select the check box 'Activate
   interface at boot time'. Press 'Done'.
   Back in the network configuration window, press 'Activate'.
2) Select 'Routing', 'Add' and enter the following:
       Device:    fddi0
       Network:   <network address>
       Netmask:   <netmask>
       Gateway:   <enter gateway address if you use one>
   NOTE: a gateway is a device that connects your IP network
   to other IP networks. If you are not sure whether you need
   one, ask your network administrator.
   Press 'Done', then press 'Save' and 'Quit'.
   Close the control panel.
3) Change to the directory /etc/sysconfig/network-scripts.
   Rename the file 'ifcfg-eth0' to 'ifcfg-fddi0':
       mv ifcfg-eth0 ifcfg-fddi0
   Open the file in an editor and change the line
   and save the file.

4) Reboot your computer and test if your adapter is working.
   If you re-enter the configuration tool later, your device
   will be shown correctly as 'fddi0'.

(6) Troubleshooting

If you run into problems during installation, check those items:

Problem:  The FDDI adapter can not be found by the driver.
Reason:   Look in /proc/pci for the following entry:
             'FDDI network controller: Unknown ...'
	     'Vendor id=1148. Device id=4000'
	  If this entry exists, then the FDDI adapter has been
	  found by the system and should be able to be used.
	  If this entry does not exist or if the file '/proc/pci'
	  is not there, then you may have a hardware problem or PCI
	  support may not be enabled in your kernel.
	  The adapter can be checked using the diagnostic program
	  which is available from the SysKonnect web site:
	  Some COMPAQ machines have a problem with PCI under
	  Linux. This is described in the 'PCI howto' document
	  (included in some distributions or available from the
	  www, e.g. at 'www.linux.org') and no workaround is available.

Problem:  Programs such as 'ifconfig' or 'route' can not be found or
          you get an error message 'Operation not permitted'.
Reason:   You are not logged in as user 'root'. Logout and 
          login as root or change to root via 'su'.

Problem:  Using the command 'ping <address>', you get a message
          "ping: sendto: Network is unreachable".
Reason:   Your route is not set up correct.
          If you are using SuSE 4.4, you might have forgotten to
	  call 'SuSEconfig' after changing the config file.
	  If you are using RedHat, you probably forgot
	  to set up the route in 'network configuration'.
	  Check the existing routes with the 'route' command
	  and check if there is an entry for 'fddi0' and if
	  it is correct.

Problem:  The driver can be started, the adapter is inserted
          into the ring, but you can not receive or transmit
          any packet; e.g. 'ping' does not work.
Reason 1: You are using a kernel version without FDDI support.
          Either your kernel is too old (pre 2.0.25), you
	  have not configured FDDI support into your kernel
	  or you simply installed/booted a wrong kernel version.
	  Update your boot kernel.
Reason 2: You have an incorrect route in your routing table.
          Check the routing table with the command 'route' and
	  read the manual pages about route ('man route').
Problem:  You want to use your computer as a router between
          multiple IP subnetworks (using multiple adapters), but
	  you can not reach computers in other subnetworks.
Reason:   Either the router's kernel is not configured for IP
	  forwarding or there is a problem with the routing table
	  and gateway configuration in at least one of the

Problem:  You find data corruption in files copied over the network
	  or locally, running Linux on a EIDE harddisk.
Reason:   You may have a motherboard that has problems with the
	  IDE DMA. Try to disable the IDE DMA (see manual page of hdparm)
	  and contact your Linux-distributor.
Problem:  At 'insmod skfp.o', you get one (or both) of the messages:
	  skfp.o: unresolved symbol fddi_type_trans
	  skfp.o: unresolved symbol fddi_setup
Reason:   You did not recompile the kernel after it has been patched
	  or the patched failed. Look in /usr/src/linux/net/netsyms.c.
	  You should find those two symbols there. If they are,
	  recompile the kernel and reinstall it. If not, the patching
	  did not succeed. Try executing (as root) the file patchit.sh
	  in the 'src' subdirectory. If it fails again, you have to
	  add those symbols manually.

If your problem is not listed here, please contact our
technical support for help. Refer to the file 'support.inf'
for contact addresses. When contacting our technical support,
please ensure that the following information is available:
- System Manufacturer and Model
- Boards in your system
- Distribution
- Kernel version

(7) Function of the adapter LEDs

        The functionality of the LED's on the FDDI network adapters was
        changed in SMT version v2.82. With this new SMT version, the yellow
        LED works as a ring operational indicator. An active yellow LED
        indicates that the ring is down. The green LED on the adapter now
        works as a link indicator where an active GREEN LED indicates that
        the respective port has a physical connection.

        With versions of SMT prior to v2.82 a ring up was indicated if the
        yellow LED was off while the green LED(s) showed the connection
        status of the adapter. During a ring down the green LED was off and
        the yellow LED was on.

        All implementations indicate that a driver is not loaded if
        all LEDs are off.

(8) History

v1.04 (990427)
	- New SMT module included, changing LED functionality
    Problems fixed:
	- Synchronization on SMP machines was buggy

v1.03 (990325)
    Problems fixed:
	- Interrupt routing on SMP machines could be incorrect

v1.02 (990310)
    New features:
	- Support for kernel versions 2.2.x added
	- Kernel patch instead of private duplicate of kernel functions

v1.01 (980812)
    Problems fixed:
	Connection hangup with telnet
	Slow telnet connection

v1.00 beta 01 (980507)
    New features:
    Problems fixed:
    Known limitations:
        - tar archive instead of standard package format (rpm).
	- FDDI statistic is empty.
	- not tested with 2.1.xx kernels
	- integration in kernel not tested
	- not tested simultaneously with FDDI adapters from other vendors.
	- only X86 processors supported.
	- SBA (Synchronous Bandwidth Allocator) parameters can
	  not be configured.
	- does not work on some COMPAQ machines. See the PCI howto
	  document for details about this problem.
	- data corruption with kernel versions below 2.0.33.

*** End of information file ***