Re: trakker 450 install problem follow up

First, slackware 8.0 the way I got it one had to modprobe ftape to get
that going.  That's no problem to reverse.  Second, this is unfortunately
ftape 3.x.  Included is what appears in /var/adm/messages when my system
boots up thank you grep and ex!

58:Sep 28 12:10:24 athame kernel: ftape v3.04d 25/11/97
64:Sep 28 12:10:24 athame kernel: [000] ftape-init.c (ftape_init) - installing QIC-117 floppy tape hardware drive ... .
65:Sep 28 12:10:24 athame kernel: [001] ftape-init.c (ftape_init) - ftape_init @ 0xc886b060.
66:Sep 28 12:10:24 athame kernel: [002]   ftape-buffer.c (add_one_buffer) - buffer nr #1 @ c4094ea0, dma area @ c0298000.
67:Sep 28 12:10:24 athame kernel: [003]   ftape-buffer.c (add_one_buffer) - buffer nr #2 @ c4094f30, dma area @ c0438000.
68:Sep 28 12:10:24 athame kernel: [004]   ftape-buffer.c (add_one_buffer) - buffer nr #3 @ c79a6020, dma area @ c0090000.
69:Sep 28 12:10:24 athame kernel: [005]   ftape-calibr.c (time_inb) - inb() duration: 947 nsec.
70:Sep 28 12:10:24 athame kernel: [006]  ftape-calibr.c (ftape_calibrate) - TC for `ftape_udelay()' = 202 nsec (at 40959 counts).
71:Sep 28 12:10:24 athame kernel: [007]  ftape-calibr.c (ftape_calibrate) - TC for `fdc_wait()' = 2320 nsec (at 2559 counts).
Jude <[email protected]>

On Thu, 14 Nov 2002, [ISO-8859-1] Agustín Martín Domingo wrote:

> dashielljt wrote:
> > The drive itself says trakker 450 on it and hooks to the parallel tape
> > drive and uses qic 80 tapes.  This t1000e identification is a puzzle to me
> > too.  I've downloaded link 98 and 127 so have the latest version and docs
> > and will try building all of this on slackware 8.0 a little later today.
> > Thanks.
>
> I have here an internal Colorado T1000 at /dev/qft0 and a parallel port
> Colorado Trakker 250 at /dev/qft1.  As Jochen told you, the stable
> drivers do not support parallel port units, so you will need to get and
> compile the development drivers.
>
> You will also need to put appropiate entries in your /etc/modules.conf
> file. My entries for the *development* drivers look someting like
>
> ---- snip ---------------
> options parport_pc irq=auto
> alias char-major-27     zftape
> options ftape ft_fdc_driver=ftape-internal,trakker,none,none
> options ftape-internal ft_fdc_base=0x3f0 ft_fdc_irq=6 ft_fdc_dma=2
> pre-install ftape-internal /usr/bin/swapout 15
> ---- snip ---------------
>
> Some systems seem not to require the first line. Also if you provide
> info on the information displayed by the driver when loading might help.
>
> I also hope your kernel does not have ftape support compiled built-in.
> If 'yes' you will need to recompile a kernel without ftape.
>
> If kernel ftape support is compiled as modules, be careful after
> installation, since the kernel places the ftape modules in a different
> place than development ftape, resulting in mixed dependencies between
> new and old modules being generated by 'depmod -a', breaking things. You
> might need to carefully move the old modules to a safe place outside the
> /lib/modules hierarchy and rerun depmod -a.
>
> Cheers,
>
> --
> =====================================================================
> Agustin Martin Domingo, Dpto. de Fisica, ETS Arquitectura Madrid,
> (U. Politecnica de Madrid)  tel: +34 91-336-6536, Fax: +34 91-336-6554,
> email:[email protected], http://corbu.aq.upm.es/~agmartin/welcome.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-tape" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html