Since I last wrote, I have upgraded to ftape-4.03-pre-2, and got my conf.modules and
insert script working. Both now load the modules sucessfully, as far as I can see, yet
both fail to allow me to sucessfully execute anything other than a 'ftmt -f /dev/qft0 
status'
command. It turns out I had ftape-tools-1.07 already. =)

Martin Jacobs wrote:
> No, the message "Device not configured" means that your
> program, let it be ftmt or tar, is not able to talk to the
> drive. That means that there is some configuration error.

This is extremely puzzling to me, as ftape/ftmt can correctly identify my drive, and I 
see
the drive light flashing, yet, even with a tape in, the kernel messages still say 'no 
tape
present', and ftmt returns this:

This is a Iomega DITTO 2GB floppy tape drive, (drive type = 0x8883)
drive status         = 0x00000009
generic drive status = 0x00040000
(In particular: * door open (no tape) * )
sense key error      = 0x00000000
residue count        = 0
file number          = -1
block number         = -1

> Tell us, how do you load the modules? Show us relevant
> snippets of /var/log/messages.

I use conf.modules to autoload the relevant modules. Here is what I get
after the ftape header, when executing 'ftmt -f /dev/qft0 status':

Jan  2 02:02:11 localhost kernel: Compiled for Linux version 2.0.36 with versioned 
symbols
Jan  2 02:02:11 localhost kernel: [000]   zftape-init.c (zft_init) - zft_init @ 
0x0305f98c.
Jan  2 02:02:11 localhost kernel: [001]   zftape-init.c (zft_init) - installing zftape 
VFS interface for ftape driver ....
Jan  2 02:02:11 localhost kernel: fdc-internal.c: fdc_internal_register @ 0x030677e4.
Jan  2 02:02:11 localhost kernel: [002]   fdc-io.c (fdc_register_R3448e164) - Probing 
for ftape-internal tape drive slot 0.
Jan  2 02:02:11 localhost kernel: [003] 0      fdc-internal.c (_fdc_int_detect) - 
called with count 0.
Jan  2 02:02:11 localhost kernel: [004] 0      fdc-internal.c (_fdc_int_detect) - 
fdc[0] base: 0x03f0, irq: 6, dma: 2.
Jan  2 02:02:11 localhost kernel: [005] 0       ftape-buffer.c (add_one_buffer) - 
buffer nr #1 @ 0090e418, dma area @ 00fc8000.
Jan  2 02:02:11 localhost kernel: [006] 0       ftape-buffer.c (add_one_buffer) - 
buffer nr #2 @ 0090e498, dma area @ 00fb8000.
Jan  2 02:02:11 localhost kernel: [007] 0       ftape-buffer.c (add_one_buffer) - 
buffer nr #3 @ 0090e518, dma area @ 00f60000.
Jan  2 02:02:12 localhost kernel: [008] 0     ftape-calibr.c (ftape_calibrate) - 
calibr_count: 6743, calibr_time: 9997 us.
Jan  2 02:02:12 localhost kernel: [009] 0     ftape-calibr.c (ftape_calibrate) - TC 
for `fdc_wait()' = 1482 nsec (at 6743 counts).
Jan  2 02:02:12 localhost kernel: [010] 0     fdc-io.c (fdc_probe) - Type 8272A/765A 
compatible FDC found.
Jan  2 02:02:14 localhost kernel: [011] 0    ftape-ctl.c (ftape_log_vendor_id) - tape 
drive type: Iomega DITTO 2GB.
Jan  2 02:02:14 localhost kernel: [012] 0    ftape-ctl.c 
(ftape_get_drive_status_Rfce64bdc) - no cartridge present.

I hope you can suggest some solutions.

> Martin

Rob

Reply via email to