This package contains three components you'll have to install
to get ftape running:

 1. The modules patches package `modules-plx.tar' where `x' is
    the version number of the kernel you need.
    This tar-file contains patches for the kernel and the
    sources for the utilities that allow you to load and unload
    kernel modules.
    Read the instructions included with the package.
 2. The ftape patches for the kernel `ftape-plx.diff'
    Patches for the patch level `x' kernel.
 3. the ftape driver.

First you'll have to install the modules package (1).
(Instructions are included with the sources) You'll only
need to apply the kernel patches for now.

Then apply the ftape patches (2) to the kernel:
Go to the kernel's root directory and type
`patch -p0 <_somewhere_/ftape-plx.diff'

Now build a new kernel starting from scratch:
Run `make config' first and set QIC-117 support to `y'.
Then set the number of tape buffers. Use 3 unless you know
what you're doing !
Then run `make depend ; make clean ; make' to build the new kernel.

Reboot the new kernel.

Go to the modules/util directory, build the tools and test them
as described in the documentation. (Don't forget `unlock' if you're
not running as root)

If the modules package is working you now can build the ftape driver.
Go to the driver's directory and run `make' (Ignore the `RCSid not
used messages' !). This will compile and install the driver.

Create the ftape devices if they don't exist already:

        mknod -m 666 /dev/ftape c 27 0
        mknod -m 666 /dev/nftape c 27 4

Put a formatted tape in the drive and wait for it to stop
making noise. Now type:

        mt -f /dev/ftape rewind

This will try to open the device. 
Because initially `tracing' is set to some value greater than
zero, some debugging output (printk) is generated on the console.

[[[[[[ start `syslog' intermezzo ]]]]]]

You'll want to capture these messages with syslogk or syslogd
(NET-2 version). If you don't have a syslog daemon running add
the following to your rc.local file:

        if [ -x /etc/syslogk ] ; then
                syslogk on 2>&1 >>/var/log/kernel &
        fi

This will append the kernel messages to the file `/var/log/kernel'.
(Make sure this file exists !)

[[[[[[ end `syslog' intermezzo ]]]]]]]

The messages generated when opening the device can start with some 
"timeout on Acknowledge" lines. This depends on the trace-level,
and is normal as long as the driver is probing for a tape drive.
If they keep appearing after the device is opened something is wrong.

If all goes well, messages will appear saying something about
"drive-wakeup compatible with <name>" and "ftape drive is <name>".
If not, "unknown drive type, no response" says that the driver
cannot activate the drive. In this case the driver will not work
with your drive.

If some message appears with "unknown vendor id", follow the
instructions in the message so I can include this information
with a new release.
In the meantime the driver will function correctly if it is
compatible with one of the known types.

Now try to retension the tape by issueing the command:
`mt -f /dev/ftape reten'
The tape should wind completely to the end once and back to
the beginning again.

If this all works you're ready to play with `dd' and `tar'
to see if reading and writing works.
If anything fails, make a logfile with `tracing' set to 13
and try to find out what's going wrong.


Bas               <bas@vimec.nl>               4-Dec-1993



