Firstly, what version of ftape are ya all running? - I'd recommend getting
the latest snapshot and compiling that.
Secondly, what hardware are you running it on? I've never manager to get a
MaxPro with a Dash card to run at the (supposed) 4Mbps. Best I get is
usually around 3Mbps, and that is on a PII-350 with 256MB RAM and 10gig SCSI
HDD - unloaded. Lowlier hardware does have more problems.
Barry Zubel
Technical Manager
City Mutual Ltd
www.citymutual.com
-----Original Message-----
From: Tom Fawcett <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, March 18, 1999 2:19 PM
Subject: Re: Ditto Max Pro
>
>Hi. I'm glad to see someone else has this problem with a Ditto Max. I
>have a Ditto Max with DASH EZ FDC (PnP card), and I've confirmed with
>isapnp and /var/log/messages that the low-level communication is happening.
>But when trying to use the drive I get numerous overruns and retries, just
>as Paulo is reporting. I haven't yet made a successful backup.
>
>I've experimented with different parameter settings, different tapes,
>different IRQs, etc. I've checked ftape docs and dejanews. Can anyone
>explain what the problem is, and what we should try next?
>
>I can provide details of the hardware configuration if they would help.
>
>-Tom
>
>
>Paulo Almeida <[EMAIL PROTECTED]> writes:
>> I have an Iomega Ditto Max Pro and now I'm trying to install on Redhat
>> 5.2 with kernel 2.2.0.
>>
>> I'm using this script to install
>>
>> /sbin/insmod ./ftape.o ft_fdc_driver=ftape-internal,none,none,none
>> ft_tracings=3,3,3,3,3
>> /sbin/insmod ./zftape.o ft_major_device_number=27
>> /sbin/insmod ./ftape-internal.o ft_fdc_fc10=0 ft_fdc_mach2=0
>> ft_fdc_base=0x0210 ft_fdc_dma=0 ft_fdc_threshold=15
>> ft_fdc_rate_limit=2000
>>
>> And everything i get when i try to use my ditto max is
>>
>> Mar 18 12:42:05 server kernel: [011] 0 ftape-ctl.c
>> (ftape_log_vendor_id) - tape drive type: Iomega DITTO MAX.
>> Mar 18 12:42:07 server kernel: [012] 0 ftape-io.c
>> (ftape_report_configuration) - TR-3 tape detected.
>> Mar 18 12:42:07 server kernel: [013] 0 ftape-ctl.c (ftape_init_drive)
>> - post QIC-117B drive @ 2000 Kbps.
>> Mar 18 12:42:07 server kernel: [014] 0 ftape-ctl.c
>> (ftape_calibrate_data_rate_R20424b34) - Highest FDC supported data rate:
>> 2000 Kbps.
>> Mar 18 12:42:09 server kernel: [015] 0 ftape-io.c
>> (ftape_report_configuration) - TR-3 tape detected.
>> Mar 18 12:42:09 server kernel: [016] 0 ftape-ctl.c (ftape_init_drive)
>> - unknown length QIC-3020 tape.
>> Mar 18 12:42:35 server kernel: [017] 0 ftape-io.c
>> (ftape_increase_threshold) - New FIFO threshold: 16.
>> Mar 18 12:42:35 server kernel: [018] 0 ftape-rw.c
>> (ftape_start_tape) - increased threshold because of excessive overrun
>> errors.
>> Mar 18 12:42:52 server kernel: [019] 0 ftape-io.c
>> (ftape_increase_threshold) - cannot increase fifo threshold.
>> Mar 18 12:42:54 server kernel: [020] 0 ftape-io.c
>> (ftape_report_error_R64fbb47c) - errorcode: 31.
>> Mar 18 12:42:55 server kernel: [021] 0 ftape-io.c
>> (ftape_report_configuration) - TR-3 tape detected.
>> Mar 18 12:42:55 server kernel: [022] 0 ftape-io.c
>> (ftape_set_data_rate) - Rate change failed!.
>> Mar 18 12:43:11 server kernel: [023] 0 ftape-io.c
>> (ftape_increase_threshold) - cannot increase fifo threshold.
>> Mar 18 12:43:12 server kernel: [024] 0 ftape-io.c
>> (ftape_report_error_R64fbb47c) - errorcode: 31.
>> .
>> .
>> .
