Juergen Leising wrote:
> On Sun, May 23, 1999 at 11:48:25PM -0400, Adam Grossman wrote:
> >
> > i tried compiling ftape 4.02, 4.03 and 3.04 and i am getting this error:
> >
> > fdc-io.c : In Function 'fdc_interrupt_wait' :
> > fdc-io.c : 433 : Structure has no member named 'timeout'
> > fdc-io.c : 454 : Structure has no member named 'timeout'
> > make [2] : *** [fdc-io.c] error 1
> > make [2] : leaving directory '/usr/src/ftape-4.02/ftape/lowlevel'
> > make [1] : *** [modules] error 2
> > make [1] : leaving directory '/usr/src/ftape-4.02/ftape'
> > make : *** [all] error 2
> >
> > this is my setup:
> >
> > RH 6.0 (kernel 2.2.5)
> > AMD K6-2 350
> >
> Hi, please upgrade to those "unstable" drivers - they are quite
> stable, however:
>
> http://www.math1.rwth-aachen.de/~heine/ftape/archives/ftape-4.x/unstable/
I have a similar system R.H.6.0, kernel 2.2.5-15, CPU is 166MHz Pentium, and
I cannot get Ftape to work either. The version that is supplied is quite
obviously 3.04d, because I can make it run enough to get entries in the
/var/log/messages file and it so identifies itself. The main trouble I have
with it is that it insists on running the floppy disk controller even though
I have a dedicated CTC-2Mb controller just for the tape drive. This worked
for R.H.5.0, but not for 6.0. I stuck parameters into the /etc/conf.modules
file as follows:
# Load ftape/zftape automatically
alias char-major-27 zftape
pre-install ftape /sbin/swapout 32
# Try to set CTC-2Mb floppy controller
# and
# Try to reduce overruns: can be [1-16]: higher: less overruns
options ftape ft-fdc-base=0x370 ft-fdc-irq=6 ft_fdc_dma=2 ft-fdc-threshold=16
# Try harder to reduce overruns: can be [1000, 500, 250]: lower: less
overruns
#options ftape ft_fdc_rate_limit=250
but it seems to ignore them. It certainly sees the alias car-major-27 zftape
line and the pre-install ftape /sbin/swapout 32 line. An extract of my
/var/log/messages file, after I ran ftape -f /dev/ftape status, is:
May 27 14:34:01 localhost kernel: ftape v3.04d 25/11/97
May 27 14:34:01 localhost kernel: (c) 1993-1996 Bas Laarhoven ([EMAIL PROTECTED])
May 27 14:34:01 localhost kernel: (c) 1995-1996 Kai Harrekilde-Petersen
([EMAIL PROTECTED])
May 27 14:34:01 localhost kernel: (c) 1996-1997 Claus-Justus Heine
([EMAIL PROTECTED])
May 27 14:34:01 localhost kernel: QIC-117 driver for QIC-40/80/3010/3020
floppy tape drives
May 27 14:34:01 localhost kernel: Compiled for Linux version 2.2.5-15 with
versioned symbols
May 27 14:34:01 localhost kernel: [000] ftape-init.c (ftape_init) -
installing QIC-117 floppy tape hardware drive ... .
May 27 14:34:01 localhost kernel: [001] ftape-init.c (ftape_init) -
ftape_init @ 0xc485c04c.
May 27 14:34:01 localhost kernel: [002] ftape-buffer.c (add_one_buffer) -
buffer nr #1 @ c2e90ae0, dma area @ c0e58000.
May 27 14:34:01 localhost kernel: [003] ftape-buffer.c (add_one_buffer) -
buffer nr #2 @ c2e90c20, dma area @ c0e50000.
May 27 14:34:01 localhost kernel: [004] ftape-buffer.c (add_one_buffer) -
buffer nr #3 @ c2e90900, dma area @ c0318000.
May 27 14:34:01 localhost kernel: [005] ftape-calibr.c (time_inb) - inb()
duration: 634 nsec.
May 27 14:34:01 localhost kernel: [006] ftape-calibr.c (ftape_calibrate) -
TC for `ftape_udelay()' = 664 nsec (at 10239 counts).
May 27 14:34:01 localhost kernel: [007] ftape-calibr.c (ftape_calibrate) -
TC for `fdc_wait()' = 1774 nsec (at 5119 counts).
May 27 14:34:01 localhost kernel: zftape for ftape v3.04d 25/11/97
May 27 14:34:01 localhost kernel: (c) 1996, 1997 Claus-Justus Heine
([EMAIL PROTECTED])
May 27 14:34:01 localhost kernel: vfs interface for ftape floppy tape driver.
May 27 14:34:01 localhost kernel: Support for QIC-113 compatible volume
table, dynamic memory allocation
May 27 14:34:01 localhost kernel: and builtin compression (lzrw3 algorithm).
May 27 14:34:01 localhost kernel: Compiled for Linux version 2.2.5-15 with
versioned symbols
May 27 14:34:01 localhost kernel: [008] zftape-init.c (zft_init) - zft_init @
0xc4880ca8.
May 27 14:34:01 localhost kernel: [009] zftape-init.c (zft_init) - installing
zftape VFS interface for ftape driver ....
May 27 14:34:01 localhost kernel: [010] fdc-io.c (fdc_config) - fdc base:
0x3f0, irq: 6, dma: 2.
May 27 14:34:01 localhost kernel: [011] fdc-io.c (fdc_probe) - Type
82077AA compatible FDC found.
May 27 14:34:06 localhost kernel: [012] ftape-ctl.c (ftape_activate_drive)
- no tape drive found !.
May 27 14:34:06 localhost kernel: [013] ftape-ctl.c
(ftape_enable_R7ec0d5d4) - ftape_activate_drive(&ftape_status.fti_drive_type)
failed: -19.
May 27 14:34:06 localhost kernel: [014] zftape-ctl.c (_zft_open) -
ftape_enable failed: -19.
May 27 14:34:06 localhost kernel: [015] zftape-init.c (zft_open) -
_ftape_open failed.
May 27 14:35:34 localhost PAM_pwdb[1204]: (su) session closed for user root
May 27 14:40:25 localhost PAM_pwdb[1263]: (su) session opened for user root
by jdbeyer(uid=500)
May 27 14:50:00 localhost kernel: [016] zftape-init.c (cleanup_module) -
successful.
May 27 14:50:00 localhost kernel: zftape successfully unloaded.
May 27 14:50:00 localhost kernel: [017] ftape-buffer.c (del_one_buffer) -
releasing buffer nr #3 @ c2e90900, dma area @ c0318000.
May 27 14:50:00 localhost kernel: [018] ftape-buffer.c (del_one_buffer) -
releasing buffer nr #2 @ c2e90c20, dma area @ c0e50000.
May 27 14:50:00 localhost kernel: [019] ftape-buffer.c (del_one_buffer) -
releasing buffer nr #1 @ c2e90ae0, dma area @ c0e58000.
May 27 14:50:00 localhost kernel: ftape: unloaded.
It is quite obvious, from the line marked [010] that it is ignoring the
address I specify (0x0370) I specify. I assumed if I rebuilt the driver I
could compile in the address (as I did with the old 3.04d driver) and have it
come up OK. I cannot even compile the 3.04d driver on this system. None of
them.
There are a lot of different drivers in
http://www.math1.rwth-aachen.de/~heine/ftape/archives/ftape-4.x/unstable/ .
Does it matter which one I use? I tried ftape-4.x-1999_04_25 and all I get is
this:
[jdbeyer@localhost ftape-4.x-1999_04_25]$ make
for i in ftape ; do make -C $i all ; done
make[1]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape'
for i in setup lowlevel internal parport zftape compressor; \
do \
make -C $i NODEP=true versions; \
done
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/setup'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/setup'
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/lowlevel'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/lowlevel'
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/internal'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/internal'
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/parport'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/parport'
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/zftape'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/zftape'
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/compressor'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/compressor'
set -e; for i in setup lowlevel internal parport zftape compressor; do make
-C $i modules; done
make[2]: Entering directory `/usr/src/ftape-4.x-1999_04_25/ftape/setup'
make[2]: *** No rule to make target `/usr/src/linux/.config', needed by
`.ftape-setup.d'. Stop.
make[2]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape/setup'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/ftape-4.x-1999_04_25/ftape'
make: *** [all] Error 2
It obviously insists on a .config file, which I do not have in the
/usr/src/linux directory, since I have never configured or built a kernel,
nor do I wish to. I did not need this when building 3.04d on Red Hat Linux
5.0. All I needed to do was fill in the MCONFIG file correctly. I could
install the kernel source, make a .config file, and perhaps even compile the
OS. Since the help messages take over 86 pages, and I do not understand them
well enough to configure my kernel, I hesitate to do this. As far as I can
tell, my kernel was not built with the ftape driver in it. I infer this from
the following:
[jdbeyer@localhost jdbeyer]$ cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
4 ttyS
5 cua
7 vcs
10 misc
14 sound
29 fb
36 netlink
128 ptm
136 pts
Block devices:
1 ramdisk
2 fd
3 ide0
9 md
22 ide1
What next?
--
Windows is not the answer. Windows is the question. The answer is no.
Jean-David Beyer
Shrewsbury, New Jersey
