On Tue, Jun 01, 1999 at 11:25:37AM +0200, Pierre Jung wrote:
> Hello,
>
> I am trying to get a Micro Solutions Backpack "Floppy" Tape drive to work
> on the parallel port interface (SuSE Linux 6.1). I first tried to compile
> the latest stable version (ftape-4_03-pre-2.tar.gz) of FTape, in which
> parallel port support for Micro Solutions BP-"floppy" tape drives is
> mentioned.
yes, should work - hopefully...
>
> I got two "undefined symbol" errors (timeout from struct current) in
> fdc-io.c. Thereafter, I took the *latest beta* on the FTape site, which
well done, in fact, under kernel 2.2.x it is necessary to take those "unstable"
drivers;
> compiled perfectly but does not "see" the drive on the parallel port when
> "inserting" the modules with the script provided in the modules directory
forget that "insert" script - set up your own loading method, for example
1st way: kmod loads needed modules "on demand", i. e. automatically: For this
it is necessary to add some entries to
/etc/conf.modules:
alias char-major-27 zftape.o
options ftape.o ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
options bpck-fdc.o ft_fdc_parport=0 ft_fdc_base=0x378 ft_fdc_irq=7
pre-install ftape.o /usr/local/bin/swapout 15
2nd way: You yourself load the modules manually:
insmod ftape ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=4,4,4,4,4
insmod zftape
insmod bpck-fdc ft_fdc_parport=0
As far as the bpck-fdc line is concerned it may be necessary to play around a bit
with the options, e. g. leaving out ft_fdc_parport, or accustomizing io address and
irq according to your bios settings and so on. This is true for both ways, of course.
(...)
After all it should be possible to type in
ftmt -f /dev/qft0 status
> irq7). I got the same behaviour on two different computers, one with an old
> SPP and a newer one with a EPP-32 parallel port. Although the connection
well, only those very old SPP ports that are even not bidirectional should have
problems, each newer parport version should work.
> May 24 19:27:47 u292_1 kernel: [005] 0 fdc-internal.c
> (fdc_int_request_regions) - address 0x3f0 occupied (by floppy driver?),
> using it anyway.
usually a bad message, but in your case, it doesn't matter, because this
is presumably the result of having used that "insert" script, that tries
to load a lot of modules, although they are not necessary..."insert" is
actually intended to be accustomized to your needs.
> May 24 19:27:47 u292_1 kernel: [006] 0 fdc-internal.c (_fdc_int_detect) -
> fdc[0] base: 0x0210, irq: 6, dma: 0.
(...)
> May 24 19:27:48 u292_1 kernel: trakker.c: trakker_register @ 0x0484f920
> May 24 19:27:48 u292_1 kernel: [010] fdc-io.c (fdc_register) - Probing for
> trakker tape drive slot 1.
well, you don't need ftape-internal nor trakker
Maybe it is necessary to have to removed parport and parport_pc before trying
to load the ftape modules, at least I do so, although in recent times it doesn't
seem to be necessary any more.
Good luck, Juergen.
--
****************************************************************
* Juergen Leising; email: [EMAIL PROTECTED] *
* http://www.stud.uni-bayreuth.de/~a0037/ *
****************************************************************
