On Sat, Jul 17, 1999 at 08:23:22AM +0200, Julien Michielsen wrote:
>
> Thank you, Juergen. Your hints got me further on the road. It looks to
> me that modules are properly loaded. The output of lsmod:
>
> Module Size Used by
> bpck-fdc 30200 0
> trakker 14644 0
> ftape-internal 10252 0
> zft-compressor 16524 -1
> zftape 88076 -1 [zft-compressor]
> ftape 145880 0 [bpck-fdc trakker ftape-internal zft-compressor
>zftape]
> parport_probe 2824 0 (autoclean)
> parport_pc 4960 1 (autoclean)
> lp 5008 1 (autoclean)
> parport 6428 1 (autoclean) [parport_probe parport_pc lp]
> serial 41940 1 (autoclean)
> memstat 1352 0 (unused)
>
Ok, at least you have loaded everything...
> My tape is an old Conner C250MQ. Just got a new motherboard installed,
Hmmm, difficult for me, maybe somebody else knows this drive - I myself
am only a bit more familiar with that bloody ditto max external,
but let's see:
> and feared that it wasn't properly attached. But I can still read my
> old Dos backups with it, so that looks all right.
> The output in /var/log/messages suggests that the machine does not see
> the FDC. In earlier versions that worked for me I didn't need to specify
Hmm, I don't know if it is possible that the ftape modules are
already loaded at THIS time, so that they would claim irq 6
and so on; this could have provoked that message - but I am not sure.
> hardware parameters of the tapedrive. As a matter of fact I don't know
> what adress, interrupt and/or IRQ it uses, the manual doesn't say. In my
> MCONFIG file I didn't go further than comment out the lines of the drives
> that certainly did not apply (tracker, jumbo etc.) In earlier versions
> of ftape (I think it was level 3 I made backups with) I didn't need to
> specify them either.
> I did not go into /etc/conf.modules, as the output in log/messages
> seems to point to the FDC. Or is that too easy a thought?
>
> Although it is lengthy, below you'll find the section of the log where
> detection of the driver is attempted, and fails.
>
> Than you
> Julien
>
> Jul 17 07:23:08 beuk kernel: ftape v4.03-pre-4 06/30/99
(...)
> Jul 17 07:23:09 beuk kernel: zftape for ftape v4.03-pre-4 06/30/99
(...)
> Jul 17 07:23:09 beuk kernel: Compiled for Linux version 2.2.7
(...)
> Jul 17 07:23:09 beuk kernel: fdc-internal.c: fdc_internal_register @ 0xc408291c.
> Jul 17 07:23:09 beuk kernel: [004] fdc-io.c (fdc_register) - Probing for
>ftape-internal tape drive slot 0.
> Jul 17 07:23:09 beuk kernel: [005] 0 fdc-internal.c (fdc_int_detect) - called with
>count 0.
> Jul 17 07:23:09 beuk kernel: [006] 0 fdc-internal.c (fdc_int_detect) - fdc[0] base:
>0x0210, irq: 6, dma: 0.
> Jul 17 07:23:09 beuk kernel: [007] 0 ftape-buffer.c (add_one_buffer) - buffer nr #1
>@ c2ecaf00, dma area @ c0df0000.
> Jul 17 07:23:09 beuk kernel: [008] 0 ftape-buffer.c (add_one_buffer) - buffer nr #2
>@ c19ad360, dma area @ c0de8000.
> Jul 17 07:23:09 beuk kernel: [009] 0 ftape-buffer.c (add_one_buffer) - buffer nr #3
>@ c19ad2c0, dma area @ c0de0000.
Usually these are good lines;
(...)
> Jul 17 07:23:58 beuk kernel: [040] 0 fdc-io.c (__fdc_command) - fdc not ready.
> Jul 17 07:23:58 beuk kernel: [041] 0 fdc-io.c (__fdc_issue_command) -
>__fdc_command(fdc, out_data, out_count) failed: -16.
> Jul 17 07:23:58 beuk kernel: [042] 0 fdc-io.c (fdc_probe) - No FDC found.
> Jul 17 07:23:59 beuk kernel: [043] 0 fdc-io.c (fdc_reset) - no drive polling
>interrupt!.
> Jul 17 07:23:59 beuk kernel: [044] 0 fdc-io.c (__fdc_command) - fdc not ready.
Oh, I cannot interprete this. Maybe it is necessary to play a bit with
the values regarding ftape-internal in /etc/conf.modules -
but I hope somebody else has better suggestions anyway.
> Jul 17 07:23:59 beuk kernel: [045] 0 fdc-io.c (__fdc_issue_command) -
>__fdc_command(fdc, out_data, out_count) failed: -16.
> Jul 17 07:23:59 beuk kernel: [046] 0 ftape-buffer.c (del_one_buffer) -
>releasing buffer nr #3 @ c19ad2c0, dma area @ c0de0000.
> Jul 17 07:23:59 beuk kernel: [047] 0 ftape-buffer.c (del_one_buffer) -
>releasing buffer nr #2 @ c19ad360, dma area @ c0de8000.
> Jul 17 07:23:59 beuk kernel: [048] 0 ftape-buffer.c (del_one_buffer) -
>releasing buffer nr #1 @ c2ecaf00, dma area @ c0df0000.
> Jul 17 07:23:59 beuk kernel: [049] 0 fdc-internal.c (fdc_int_detect) - called
>with count 0.
> Jul 17 07:23:59 beuk kernel: [050] 0 fdc-internal.c (fdc_int_detect) - fdc[0]
>base: 0x0210, irq: 6, dma: 0.
> Jul 17 07:23:59 beuk kernel: [051] 0 ftape-buffer.c (add_one_buffer) - buffer
>nr #1 @ c2ecaf00, dma area @ c0dc0000.
> Jul 17 07:23:59 beuk kernel: [052] 0 ftape-buffer.c (add_one_buffer) - buffer
>nr #2 @ c19ad360, dma area @ c0df8000.
> Jul 17 07:23:59 beuk kernel: [053] 0 ftape-buffer.c (add_one_buffer) - buffer
>nr #3 @ c19ad2c0, dma area @ c0df0000.
> Jul 17 07:23:59 beuk kernel: [054] 0 ftape-calibr.c (ftape_calibrate) -
>calibr_count: 6455, calibr_time: 9997 us.
(...)
Can you tell us the ftape related parts of /etc/conf.modules?
Good luck, Juergen.
--
*****************************************************************
* Juergen Leising, E-Mail: [EMAIL PROTECTED] *
* http://www.stud.uni-bayreuth.de/~a0037/ *
*****************************************************************
