Juergen Leising (a0037@stud.uni-bayreuth.de)
Thu, 16 Sep 1999 16:33:44 +0200
On Thu, Sep 16, 1999 at 02:51:58PM +0200, Michael Franssen wrote:
(...)
> I am trying to get the IOmege ditto 2Gb external tape drive to work on my
> computer running RedHat linux 6.0.
>
> The following packages are already running:
>
> >lsmod
> Module Size Used by
> nfsd 150936 8 (autoclean)
> lockd 30856 1 (autoclean) [nfsd]
> sunrpc 52356 1 (autoclean) [nfsd lockd]
> parport_pc 5012 1 (autoclean)
> lp 4412 1 (autoclean)
> parport 7060 1 (autoclean) [parport_pc lp]
> 3c59x 18920 1 (autoclean)
> opl3 11208 0
> cs4232 2440 0
> ad1848 15920 0 [cs4232]
> uart401 5968 0 [cs4232]
>
> I did download the latest ftape version (and read the warnings, so I'm
> trying ftape-4.03-pre2), but everything I try goes wrong. Here's what
> I tried so far:
>
> 1) compiling ftape 4.03-pre2:
> This result in the compile-time error message:
>
> >fdc-io.c: In function dc_interrupt_wait':
> >fdc-io.c:433: structure has no member named imeout'
> >fdc-io.c:454: structure has no member named imeout'
> >make[2]: *** [fdc-io.o] Error 1
> >make[2]: Leaving directory /usr/src/ftape-4.03-pre-2/ftape/lowlevel'
> >make[1]: *** [modules] Error 2
> >make[1]: Leaving directory /usr/src/ftape-4.03-pre-2/ftape'
> >make: *** [all] Error 2
>
for kernels 2.2.x you need one of those "unstable" drivers, that can be found at
http://www.math1.rwth-aachen.de/~heine/ftape/archives/ftape-4.x/unstable/
4.03-pre2 is not suitable.
> Even after recompiling my kernel, with all sources left in place this
> message persists.
>
> 2) installing ftape 4.02 with rpm (I know about the bug's concerning the
> external backpack devices, but I just wanted to get ANY reaction from my
> tape):
>
forget 4.02, sorry:
> * During install I get a whole bunch of unresolved symbol(s), but I believe
> that the documentation states that I can ignore these. The full list can
> be found at the end of this mail. Despite the messages rpm -qa reports that
> the package has been installed.
>
the mentioned upgrade is really necessary...
> * When trying insmod (or modprobe) to load ftape I then get the following
> message:
>
> >modprobe ftape
> /lib/modules/2.2.5-15/misc/ftape.o: invalid parameter ft_fdc_driver
>
this shouldn't have appeared, however. I cannot see a typo, so I cannot explain
this "invalid parameter".
> even though it is defined in /etc/conf.modules by:
>
> alias char-major-27 zftape
> options ftape ft_fdc_driver=bpck-fdc,none,none,none
>
> I even tried modprobe ftape ft_fdc_driver=bpck-fdc,none,none,none, but
> this resulted in the same error.
>
> I do not know what else I could try. I read through some history of this
> mailing list, the ftape-FAQ list and other documentation, but there seems
> to be no more information. Can anybody help me? Please?
linux-tape@vger.rutgers.edu often has to deal with that iomega stuff...
Maybe deja.com can provide you with some of the last postings referring
to this theme...
- Do not forget to modify MCONFIG
- maybe you will have to remove "lp" for the first time:
rmmod lp
and then go ahead with insmod or modprobe.
- maybe it is necessary to switch your BIOS settings from "ECP" for instance to
"bidirectional": at least this was the optinion of some people in the last
few days, although I can remember one year ago right the opposite was correct...
(...)
(my own ditto max page is NOT up to date, btw.)
Bye, Juergen.
-- ************************************************************************* * Juergen Leising, Germany http://leising.home.pages.de/ * * juergen.leising@gmx.de http://leising.freeshell.org/ * *************************************************************************-- To unsubscribe, send mail to: linux-parport-request@torque.net -- -- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Thu 16 Sep 1999 - 10:36:44 EDT