PREV UP NEXT The Ftape Installation and Usage Guide - Testing ftape


7.5: ftape Debugging messages

`wakeup type mismatch'

Follow the instructions in the message so that I can decide if I have to add this information to a new release of ftape. There is nothing to worry about as long as the tape drive works.


`unexpected stray interrupt'

An unexpected interrupt has occurred. A bit ugly but should be harmless.


`unknown vendor id'

If some messages appear with `unknown vendor id', follow the instructions in the message so that 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.


`no tape drive found!'

One of the really fatal error messages the drive can produce is `no tape drive found!' indicating that the driver cannot activate the drive. In this case you can try the other devices (`/dev/qft1', `/dev/qft2', `/dev/qft3'). In case they all fail the driver will not work with your drive.

In simple cases this can mean that you used the wrong settings for the io-address, irq and dma specifications. Check the documentation of your drive and try to find out if the software that was shipped together with the tape drive uses (and works) with other settings than you used when configuring ftape. See Compiling ftape, particularly see FDC_OPT.


ftape logo Use these buttons to jump to the top menu

TOP (previous node) TOP (parent node) TOP (next node) TOP (this node)