Ditto 2 GB Parport External Tape Drive
----------------------------
Am still struggling to get my Ditto set up :(
My Script to Insert the Modules looks like this :-
-----------------------
#!/bin/bash
cd /lib/modules/2.2.10/misc/
# Example module insertion script for ftape-4.x
#
# Please modify to reflect your hardware configuration
#
# isapnp ./isapnp.conf
# insmod ./ftape.o ft_fdc_driver=ftape-internal,bpck-fdc:trakker,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
# 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!
#
# insmod ./ftape-internal.o ft_fdc_fc10=0 ft_fdc_mach2=0 ft_fdc_base=0x378
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
modprobe parport
modprobe parport_pc io=0x378 irq=7 || true
insmod ftape.o ft_fdc_driver=bpck-fdc:trakker,none,none ft-tracings=3,3,3,3
insmod zftape.o ft_major_device_number=27 # ${27-FT_MAJOR}
#
# maybe your klogd doesn't understand `-i', refer to its man-page ...
#
#/usr/sbin/klogd -i
........................................................................................................
BUT, when I execute this Script, the messages am getting are like :-
bash-2.03# sh ftins
ftape.o: invalid parameter parm_ft-tracings
zftape.o: unresolved symbol ftape_trace_log
zftape.o: unresolved symbol ftape_command
zftape.o: unresolved symbol ftape_report_error
zftape.o: unresolved symbol ftape_find_end_of_bsm_list
zftape.o: unresolved symbol ftape_abort_operation
zftape.o: unresolved symbol ftape_write_segment
zftape.o: unresolved symbol fdc_put_deblock_buffer
zftape.o: unresolved symbol ftape_get_drive_status
zftape.o: unresolved symbol ftape_loop_until_writes_done
zftape.o: unresolved symbol ftape_door_lock
zftape.o: unresolved symbol ftape_seek_to_eot
zftape.o: unresolved symbol ftape_decode_header_segment
..................................................................
What do I need to do, to get up and running ?
Thanks
--
____________
sent on Linux
____________
