Re: pre-patch-2.0.16

Michael Driscoll (fenris@lightspeed.net)
Sat, 31 Aug 1996 14:51:03 -0700

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Ralph Sims: "Re: cdrom err & 2.0.15"
Previous message: Roeland Th. Jansen: "cdrom err & 2.0.15"
Maybe in reply to: John Storrs: "pre-patch-2.0.16"

>ftape error with pre-2.0.16:
> $ tar tf /dev/ftape
> $ tar: can't open /dev/ftape : No such device
>log contains:
> kernel: [008] fdc-io.c (fdc_interrupt_wait) - error: nested call.
> kernel: [009] fdc-io.c (fdc_reset) - missing interrupt after reset.
> kernel: [010] ftape-ctl.c (ftape_activate_drive) - no tape drive found !.
> kernel: [011] fdc-io.c (fdc_result) - fdc not ready.
> kernel: [012] fdc-isr.c (fdc_isr)
> - probably fatal error during FDC Result Phase.
> kernel: [013] fdc-isr.c (fdc_isr) - drive may hang until (power) reset :-(.
> kernel: [014] kernel-interface.c (ftape_open) - _ftape_open failed.
>
>Floppy works ok.
>
>Tape is Iomega Ditto 3200 drive with Dash controller. No problems writing and
>reading with 2.0.14.

Same thing here. Module seems to load fine, no errors, but when /dev/ft
or /dev/nft are accessed, I get a no such device error, and the logs show
things similar to the above.

I have a ditto 420, no dash controller.
Mike Driscoll
<fenris@lightspeed.net>

Next message: Ralph Sims: "Re: cdrom err & 2.0.15"
Previous message: Roeland Th. Jansen: "cdrom err & 2.0.15"
Maybe in reply to: John Storrs: "pre-patch-2.0.16"