Well im using external ditto max pro with 2.2.14 with "unstable"
ftape-4.x-1999_09_11 and all work fine.
I compile the kernel without any modules except ftape and parport modules.
i not include lp support.
I configure de bios with EPP 1.9 that the ditto support and you coud get 9.6
MB/min without compression.
I use this script for load de drivers.
-----------------------
#!/bin/bash
# http://www.stud.uni-bayreuth.de/~a0037/ditto.html
# Example module insertion script for ftape-4.x
#
# Please modify to reflect your hardware configuration
#
# isapnp ./isapnp.conf
insmod ./ftape.o ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=3,3,3,3,3
insmod ./zftape.o ft_major_device_number=27 # ${27-FT_MAJOR}
#
# NOTE: YOU DON'T NEED zft-compressor.o UNLESS you want to decompress
# compressed volumes created by ftape-3.x. Writing of compressed
# volumes is no longer supported.
#
#insmod ./zft-compressor.o
#
# NOTE: even the newest modules utilities are broken like hell with
# 2.0 kernels. Try to specify a negative paramenter, i.e. -1, and it
# is interpreted as a string. Try to say: 0xffffffff, and NO, you
# DON'T get -1, but MAXINT. :-(
#
# NOTE: you can mess up things like hell if you specify wrong
#
# NOTE: you can mess up things like hell if you specify wrong
# parameters. Specifically, don't use the rate limit parameter if
# everything works without it. Valid setting for "rate_limit" are
# 4000, 3000, 2000, 1000 and 500 (500 is pretty useless).
#
# If you have a Ditto Max tape drive, DO NOT attempt to specify a rate
# limit below 2000Kbps! It _really_ needs at least 2000Kbps.
#
# TR-3 tape drives need at least 1000Kbps.
#
# QIC-80 tape drives need at least 500Kbps.
#
# QIC-40 tape drives work at 250Kbps.
#
# PLEASE MAKE SURE neither to forget any of the "0"s when specifying
# the rate limit, nor to add an additional "0". There is really much
# of a difference between "500" and "5000", or, even worse, "2000" and
# "200".
#
# I'll creep through your network interface and ask General Failure to
# read your hard disk if you mess up the ft_fdc_rate_limit parameter
# by messing up the number of "0"s!
# QIC-80 tape drives need at least 500Kbps.
#
# QIC-40 tape drives work at 250Kbps.
#
# PLEASE MAKE SURE neither to forget any of the "0"s when specifying
# the rate limit, nor to add an additional "0". There is really much
# of a difference between "500" and "5000", or, even worse, "2000" and
# "200".
#
# I'll creep through your network interface and ask General Failure to
# read your hard disk if you mess up the ft_fdc_rate_limit parameter
# by messing up the number of "0"s!
#
#insmod ./ftape-internal.o ft_fdc_fc10=0 ft_fdc_mach2=0 ft_fdc_base=0x210 ft_fdc
_dma=0 ft_fdc_threshold=15 # ft_fdc_rate_limit=4000
modprobe parport || true # pre-2.1 kernels don't have the parport module
#insmod ./trakker.o
#insmod ./bpck-fdc.o ft_fdc_parport=0 ft_fdc_irq=7 ft_fdc_base=0x378
insmod ./bpck-fdc.o ft_fdc_parport=0 ft_fdc_irq=7 ft_fdc_base=0x378
#
# maybe your klogd doesn't understand `-i', refer to its man-page ...
#
/sbin/klogd -i
------------------------------------------------------------------------------------------
JC
Nathan Meyers ha escrito:
> Hi,
>
> I'm trying to use ftape with an external DittoMax drive on a Compaq DeskPro
> running the 2.2.12 kernel... having numerous problems, the worst of which is
> a kernel hang when I try to use the device. I'm wondering if anyone is
> having success with such a configuration. Here are the particulars:
>
> - I'm using the "unstable" ftape-4.x-1999_09_11 which, unlike the 4.03
> pre-release, can be compiled against the 2.2 kernel.
>
> - I'm inserting the modules with reasonable values:
>
> /sbin/modprobe ftape ft_fdc_driver=bpck-fdc
> /sbin/modprobe zftape
> /sbin/modprobe bpck-fdc
>
> - The address and IRQ values reported for the parallel device are correct,
> and printing works just fine (when the bpck-fdc driver isn't loaded, of
> course).
>
> - I have the device configured more or less like an EPP (more detail below).
>
> - As soon as I try to use the device (for example, ftmt -f /dev/qft0
> status), the system locks up and will respond only to a power cycle.
>
> Now, I know that the driver is particular about using EPP and not ECP
> (according to info at LinuxTapeCert.org)... would that possibly account for
> the lockup?
>
> Configuring the parallel port on the DeskPro is an interesting exercise. The
> BIOS configuration menu doesn't offer choices like "SPP, EPP, ECP", it
> offers choices that look like this:
>
> <IO Address>
> <IO Address> <IRQ>
> <IO Address> <IRQ> <DMA>
>
> In other words, you can choose a configuration that specifies an IO address
> but nothing else (like SPP?), one that specifies an IO address and an IRQ
> (like EPP?), or one that specifies an IO address, IRQ, and DMA (like ECP?).
> I've chosen one that specifies an IO address and IRQ, which are correctly
> recognized by the parallel driver. /proc/parport/0/hardware reports the
> following:
>
> base: 0x378
> irq: 7
> dma: none
> modes: SPP, ECP, ECPEPP, ECPPS2
>
> These modes seem a little strange for a device without DMA enabled, but the
> IO and IRQ values match the BIOS settings. Might these mode choices explain
> the driver lockup?
>
> I observe something else strange when I insert the drivers: in the
> /sbin/lsmod output: zftape reports a "Used by" value of -1.
>
> That's my life with ftape in a nutshell. Does anyone recognize the problems
> and/or have suggestions on what steps might get this stuff to work?
>
> Nathan Meyers
> [EMAIL PROTECTED]
