Skip-
I was having very similar problems setting up my personal Ditto 2G drive.
Carl Nobile sent me some procedures for figuring out what resource
settings to use under Linux.
I won't resend the message to the entire list; If you think these
instructions might help you, let me know privately & I'll forward them to
you.
I also have a module insert script that I wrote, based on a script sent to
me by another member of this list. If you'd like that as well, just let
me know. :-)
-- Mike
________________________________________________________________
Mike Stevens * GeoCities Systems Administration * 310/314-8979
On Mon, 30 Nov 1998, Skip Egley wrote:
> Date: Mon, 30 Nov 1998 15:56:52 -0600
> From: Skip Egley <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: Linux Tape Mailing List <[EMAIL PROTECTED]>
> Subject: Still need help
>
>
> I still can't get anything out of it.
> I tried base=0x370 DMA=2 and IRQ=6 as suggested by another Skip, but to
> no avail. I still cannot get any response at all. I'm getting some
> messages in /var/log/messages that perhaps make sense to others.
> It appears that it is not finding my Exabyte accelerator card, or
> something like that.
> Here's a snippet of the messages file. Note the "no drive polling
> interrupt!" near the bottom...
>
> Nov 30 14:20:48 kernel: fdc-internal.c: fdc_internal_register @
> 0x088528f4. Nov 30 14:20:48 kernel: [005] fdc-io.c (fdc_register)
> - Probing for ftape-int
> ernal tape drive slot
> 0. Nov 30
> 14:20:48 kernel: [006] 0 fdc-internal.c (_fdc_int_detect) - called with
>
> count
> 0.
> Nov 30 14:20:48 kernel: [007] 0 fdc-internal.c (_fdc_int_detect) -
> fdc[0] base:
> 0x0370, irq: 6, dma:
> 2. Nov 30
> 14:20:48 kernel: [008] 0 ftape-buffer.c (add_one_buffer) - buffer nr
> #1
> @ 01318098, dma area @
> 00580000. Nov 30 14:20:48
> kernel: [009] 0 ftape-buffer.c (add_one_buffer) - buffer nr #2
> @ 01318318, dma area @
> 00fe0000. Nov 30 14:20:48
> kernel: [010] 0 ftape-buffer.c (add_one_buffer) - buffer nr #3
> @ 01318398, dma area @ 00ca8000.
> Nov 30 14:41:02 kernel: [011] 0 ftape-calibr.c (ftape_calibrate) -
> calibr_c
> ouNov 30 14:41:03 kernel: [013] 0 fdc-io.c (fdc_reset) - no drive
> polling interrupt!.
> Nov 30 14:41:03 kernel: [014] 0 fdc-io.c (__fdc_command) - fdc
> not ready.
> Nov 30 14:41:03 kernel: [015] 0 fdc-io.c (__fdc_issue_command) -
> __fdc_command(fdc, out_data, out_count) failed: -16.
> Nov 30 14:41:03 kernel: [016] 0 fdc-io.c (__fdc_command) - fdc
> not ready.
> Nov 30 14:41:03 kernel: [017] 0 fdc-io.c (__fdc_issue_command) -
> __fdc_command(fdc, out_data, out_count) failed: -16.nt: 6617,
> calibr_time: 9997 us.
> Nov 30 14:41:02 kernel: [012] 0 ftape-calibr.c (ftape_calibrate) -
> TC for `fdc_wait()' = 1510 nsec (at 6617 counts).
>
>
> Does anyone understand what this means?
>
> Thanks,
> Skip Egley
>
>
