Hi Sadhu,

> hi folks
> 
> would really appreciate some help, thanks!
> 
> (i saved the output if you care to see it).
> ...

Have you the necessary devices:

It's essential to have at least the following:

crw-------   1 root     root      27,   4 Dec  5 21:58 nqft0
crw-------   1 root     root      27,   0 Dec  5 21:58 qft0
crw-------   1 root     root      27,  32 Dec  5 21:58 rawft0  
> 
> 7) modprobe zftape.  seems fine.
> 
> 8)/sbin/modprobe ftape-internal
> Initialization of ftape-internal failed
> ftape: Device or resource busy

Ok, what's in your /etc/conf.modules? Try to load your drives
first manually. E.g.:

        insmod ftape ft_fdc_driver=ftape-internal,none,none,none ft_tracings=3,3,3,3,3

This ensures that nothing else is loaded by the kernel
daemon. I assume that your ditto is connected to a floppy
controller.

Next load ftape-internal:

        insmod ftape-internal ft_fdc_fc10=0 ft_fdc_mach2=0 ft_fdc_base=0x370 
ft_fdc_irq=5 ft_fdc_dma=1

Please replace your values against mine.

> 
> 
> WHAT>>??  why does it say device or resource busy?  there is no tape

This only means, that there i no driver serving the device.
That's from the point of view of programs like tar, ftmt or
other the same as when device or resource are busy.

> in the drive, and the drive hasn't been accessed. according to the faq,
> this message should only come if a process is still running holding
> on to the drive, like tar.  but the only command run was the modprobe, i
> haven't
> tried putting any tape in the drive yet >?????
> 
> i believe i am following the instructions exactly.  at this point i am stuck
> 
> HELP!
> thank you!
> sadhu
> 
> ps: here's the output of dmesg:
> 
> ftape v4.02 08/29/98
>  
> (c) 1993-1996 Bas Laarhoven
> (c) 1995-1996 Kai Harrekilde-Petersen
> (c) 1996-1998 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.0.36
> installing QIC-117 floppy tape hardware drive ...
> ftape_init @ 0x0280b1b0.
> zftape for ftape v4.02 08/29/98
> fdc-internal.c: fdc_internal_register @ 0x0284476c.
> [000]   fdc-io.c (fdc_register) - Probing for ftape-internal tape drive
> slot 1.
> [001]   fdc-io.c (fdc_register) - Probing for ftape-internal tape drive
> slot 2.
> [002]   fdc-io.c (fdc_register) - Probing for ftape-internal tape drive
> slot 3.

I am missing probing of slot 0. There seems to be something
wrong. If my above suggestion works, you should get something
like the above, but after probing ... slot 0 should come 

...
... (_fdc_int_detect) - called with count 0.
... (_fdc_int_detect) - fdc[0] base: 0x0370, irq: 5, dma: 1.
...


If loading modules by hand works, then adapt your
/etc/conf.modules. 

Good luck!

Marin

-- 
Martin Jacobs * Windsbach * [EMAIL PROTECTED]

Reply via email to