Hi Mark,

Get the kernel sources, if they're not on your CD ROMs already. And
then read the ftape docs, it wants certain things turned off or on.

Also get:

The modules-2.0.0 utility package has some serious flaws and it
won't work with ftape-internal and others.  Get the newer
modutils-2.1.85 that is used with kernel 2.1.x.
You can get it at:

ftp://ftp.kernel.org/pub/linux/kernel/v2.1/

The docs with the package says it won't compile without a
kernel 2.1.x header files, but it worked with no problems with my
2.0.35 kernel header files.


On 25-Jan-99 [EMAIL PROTECTED] wrote:
> Folks,
> 
> I feel bad about writing to this list, but I'm at a loss.
> 
> I have a Compaq laptop running Slackware 3.5 with Linux kernal
> 2.0.34.
> I loaded the binaries -- I didn't try to compile my own kernal.  I
> have an 
> Iomega Ditto 2GB tape drive.  When I compiled ftape, it did complain
> about
> stuff (as the linux source was missing), but the three modules I
> needed were
> produced, so I figured I was okay.
> 
> This is what I added to /etc/conf.modules:
> alias char-major-27       zftape
> options ftape ft_fdc_driver=bpck-fdc,none,none,none
> 
> When I load the modules (ftape.o zftape.o and bpck-fdc.o) I get these
> error 
> messages in the log:
> 
> bpck-fdc.c (bpck_fdc_detect) - can't find bpck interface for ftape id
> 0.
> bpck-fdc.c (bpck_fdc_detect) - ft_parport_probe(fdc, &bpck->parinfo)
> failed: -6
> fdc-io.c (fdc_search_driver) - No tape drive found for "bpck-fdc"
> driver.
> fdc-io.c (fdc_init) - fdc_search_driver(ftape->drive_sel) failed: -6.
> ftape-ctl.c (ftape_enable) - fdc_init(ftape) failed: -6.
> zftape-ctl.c (_zft_open) - ftape_enable(sel) failed: -6.
> zftape-init.c (zft_open) - _zft_open failed.
> 
> What's a bpck interface?  What isn't it finding?
> 
> Am I right in thinking that some trivial setting is wrong?  Or should
> I bite
> the bullet, get the kernal sources and compile my own?
> 
>   Mark
----------------------------------
E-Mail: Carl J. Nobile <[EMAIL PROTECTED]>
Date: 25-Jan-99
Time: 17:59:41
----------------------------------

Reply via email to