Re: ftape 4.x with linux 2.4.22: can't find parport interface

[email protected] wrote:
> Problem: 
> 	insmod ftape.o
>  	insmod bpck-fdc.o
> 	dmesg
>   leads to:
> ftape v4.05 03/17/2002
>  
> (c) 1993-1996 Bas Laarhoven
> (c) 1995-1996 Kai Harrekilde-Petersen
> (c) 1996-2000 Claus-Justus Heine <[email protected])
>  
> QIC-117 driver for QIC-40/80/3010/3020/Ditto 2GB/MAX floppy tape drives.
> Compiled for Linux version 2.4.22 (SMP).
> installing QIC-117 floppy tape driver ...
> ftape_init @ 0xdcab2180.
> bpck-fdc.c: bpck_fdc_register @ 0xd89aab70
> [000] 0  fdc-parport.h (ft_parport_probe) - can't find parport interface for ftape id 0.
> [001] 0 bpck-fdc.c (bpck_fdc_detect) - can't find bpck interface for ftape id 0.[002] 0 bpck-fdc.c (bpck_fdc_detect) - ft_parport_probe(fdc, &bpck->parinfo) failed: -6.
> [...]
> [same errors for ftape id1-3]
> [...]
> 
>   Of course parport and parport_pc modules are loaded properly before:
> parport0: PC-style at 0x378 [PCSPP(,...)]
> 

Just a guess, what your modules configuration say about ftape? See below 
mine. Try with the line 'options parport_pc irq=auto' as below. I do not 
why, but seems that there were changes in modutils or the parallel port 
support that made parallel port units not work without it. In Debian 
that change was at some point between potato and woody, but I could not 
debug that more.

# snip ----------------------------------------------------------------
#
# load ftape/zftape automatically
#
#options parport_pc io=0x378 irq=7
options parport_pc irq=auto
# valid for all versions with zftape

alias char-major-27     zftape

# Bleeding edge ftape driver from ftape-module

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 ----------------------------------------------------------------


-- 
Agustin

-
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