dd
Hi,
> I have the Red Hat 5.1 distribution. Which gives me kernel 2.0.35.
ok -now it's clear: no parport module necessary.
BUT: Conner CTT800e: Well, it may be quic-3020, but the problem is the
protocol used in using the parport. Some parport drives work with ftape,
others not - independently from the quic standard they use.
For I know absolutely nothing about CTT800e, I would try different
configurations - the first one:
> >
modprobe ftape ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
> > modprobe zftape
> > modprobe bpck-fdc ft_fdc_parport=0
after realizing that this has failed:
rmmod bpck-fdc
rmmod zftape
rmmod ftape
the second:
modprobe ftape ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
modprobe zftape
modprobe bpck-fdc ft_fdc_base=0x387 ft_fdc_irq=7
(assuming you have plugged in your drive into your first parallel port)
Well, if your drive doesn`t work with bpck-protocol: The last two tries
are nonsense.
There's only one additional and different parallelport protocol supported by
ftape:
trakker
I don't know how to configure that, but there are examples in the
documentation - and it is similar to the given examples:
first ftape, after that zftape and the last one is trakker.
In doubt:
modprobe ftape ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
modprobe zftape
modprobe trakker
> >
> >but these are the right commands ONLY for external drives using the
> >bpck-protocol like iomega-ditto max. If you have a different drive
> >replace bpck-fdc with trakker or with ftape-internal
>
> That is the rub. The documentation says it supports the QIC-3020
> format but not what to load to use it. I have a Conner CTT800E
> external drive which is supposed to be QIC-3020.
>
> Thanks again. It will be nice to get this working. I don't want to put
> a lot of effort into Linux until I know I can backup and recover.
>
I do not have much hope; you have one if you get a message in your
/var/log/messages like FOUND Conner ....
errors after that can probably be solved - but I'm afraid ftape will not
be able to detect the drive.
But let's wait and see what your syslogd spits out.
Good luck,
Juergen.
