Seagate STT3401A Travan

Hey all

Just got one of the above tape drives, it's an ide unit and has been set up to use the ide-scsi module (just like all the other tape drives I look after)

Now every time I try to write to the tape (with any piece of software) I get an Input/Output error as soon as it starts to write, and when using Taper - it exits with a segmentation fault.

I suspect it's either the IORDY state which is currently on - or the fact it's a 20/40 unit and Linux simply doesn't like it!  My question is then, how do I set the IORDY to off from the console prompt?  Or could it be the compression settings?

Using Mandrake 9.0

-----Original Message-----
From: C.A. 'Duke' Fleming [mailto:[email protected]]
Sent: 08 July 2003 22:33
To: [email protected]
Subject: RedHat 9 compile failure


All,

Tried to compile ftape-4x-2003_05_31 on RedHat 9 box running 2.4.20-18.9 kernel.  Compile failed with the following results:

for i in ftape ; do make -C $i all ; done
make[1]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape'
> ../include/linux/modftversions.h
for i in internal lowlevel parport zftape; \
do \
  make -C $i NODEP=true versions; \
done
make[2]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape/internal'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape/internal'
make[2]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape/lowlevel'
gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4/include -DCONFIG_X86 -mpreferred-stack-boundary=2 -march=i686  -E -D__GENKSYMS__ ftape_syms.c
| /sbin/genksyms  -k 2.4.20-18.9custom > ../../include/linux/modules/ftape_syms.ver.tmp
unrecognised kernel version : 2.4.20-18.9custom
mv ../../include/linux/modules/ftape_syms.ver.tmp ../../include/linux/modules/ftape_syms.ver
updating ../../include/linux/modftversions.h
make[2]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape/lowlevel'
make[2]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape/parport'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape/parport'
make[2]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape/zftape'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape/zftape'
make -C internal modules
make[2]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape/internal'
make[2]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape/internal'
make[2]: Entering directory `/root/temp/ftape-4.x-2003_05_31/ftape/internal'
gcc -Wall -Wstrict-prototypes -O2  -fomit-frame-pointer -fno-strength-reduce -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4/include -DCONFIG_X86 -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include ../../include/linux/modftversions.h    -c -o fdc-internal.o fdc-internal.c
In file included from ../lowlevel/ftape-tracing.h:35,
                 from fdc-internal.c:43:
../lowlevel/ftape-init.h: In function `ft_sigblockall':
../lowlevel/ftape-init.h:57: structure has no member named `sigmask_lock'
../lowlevel/ftape-init.h:60: too many arguments to function `recalc_sigpending_Rfb6af58d'
../lowlevel/ftape-init.h: In function `ft_sigrestore':
../lowlevel/ftape-init.h:65: structure has no member named `sigmask_lock'
../lowlevel/ftape-init.h:67: too many arguments to function `recalc_sigpending_Rfb6af58d'
make[2]: *** [fdc-internal.o] Error 1
make[2]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape/internal'
make[1]: *** [_modsubdir_internal] Error 2
make[1]: Leaving directory `/root/temp/ftape-4.x-2003_05_31/ftape'
make: *** [all] Error 2

Can anyone help me get past this problem and make a clean compile?

Thanks.

Duke Fleming
Principal
Fleming Associates Inc.
http://www.flemingassoc.com
-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html