Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Iomega DITTO MAX woes

0 views
Skip to first unread message

Bruce Barnett

unread,
Jan 9, 1999, 3:00:00 AM1/9/99
to
This is my second posting for help. I think I read all of the
documents, have UNIX experience, but not much Linux experience.

System: IBM 385XD Thinkpad Laptop
Tape: Iomega Ditto Max Parallel Port Tape
Linux: 2.0.36 (RedHat 5.2) (Using a source I rebuilt)
FTape: 4.03-pre-2
/etc/conf.modules:
alias char-major-27 zftape
options ftape ft_fdc_driver=bpck-fdc,none,none,none
options bpck_fdc ft_fdc_base=0x378 ft_fdc_irq=7

(This last line was suggested to me by
Juergen...@stud.uni-bayreuth.de
I have no idea what the proper ft_fdc_base and irq are. I tried to find this
by booting under Windows, but it only listed the Floppy Disk
Controller:
interrupt request=6
I/O Reg: 03f0-03f5
dma=2

Symptom:
if I do a mt and query the status of the tape, I get operation not
supported.

I manually inserted ftape.o using insmod
I then typed "insmod trakker.o" and got:
trakker.o: init_module: Device or resource busy
If I then "insmod bpck-fdc.o", the LCD screen goes blank, and I have to
power cycle the system.


I have only a few more days where I can return the Iomega tape for a
refund. Is there anything else I can try?

Do I have the right I/O IRQ values?
Should I use a different version of ftape?
Should I try building it into the kernel instead of modules?


Piotr Szeptynski

unread,
Jan 11, 1999, 3:00:00 AM1/11/99
to
Bruce Barnett wrote:

> FTape: 4.03-pre-2
> /etc/conf.modules:
> alias char-major-27 zftape
> options ftape ft_fdc_driver=bpck-fdc,none,none,none
> options bpck_fdc ft_fdc_base=0x378 ft_fdc_irq=7
>
> (This last line was suggested to me by
> Juergen...@stud.uni-bayreuth.de
> I have no idea what the proper ft_fdc_base and irq are. I tried to find this

You can check it in your computer's bios setup. You can also compile ftape
with auto-detection. I'm not setting up any irqs etc. and it works.

> I manually inserted ftape.o using insmod
> I then typed "insmod trakker.o" and got:
> trakker.o: init_module: Device or resource busy

trakker.o is not a valid module for Ditto parallel port.
Read the documentation - bpck-fdc.o is the one.

> If I then "insmod bpck-fdc.o", the LCD screen goes blank, and I have to
> power cycle the system.

Check your parallel port settings in bios setup, look through M_CONFIG,
modify modules/insert file to satisfy you needs. I can show you my
configuration. I had the same problem with Ditto 2 weeks ago. It works now.
But... I still have a problem. It perfectly writes and read tapes under
Win95 but under linux I get write or read errors. I have changed 2 tapes
with no success...

> Do I have the right I/O IRQ values?

Nobody knows. It's up to your hardware

> Should I use a different version of ftape?

I don't thinks so.

> Should I try building it into the kernel instead of modules?

No.

--
__________________________________________________________________________
Piotr Szeptynski | GCM/O d- s++: a-- C BSL++++$ P+>++ L++>++++ E--- W+ N++
P...@agsmedia.pl | o-- K- w(--) O+ M V? PS-- PE Y? PGP->+ t 5 X+ R* tv
| b+>++ DI? D+ G>++++ e(+)>+++ h!(*) r+>+++ y**>+++++
COFH - Cool Operator From Heaven

Bruce Barnett

unread,
Jan 13, 1999, 3:00:00 AM1/13/99
to
Thanks for the help. I am getting closer.
I can load the ftape, ztape, and bpck-fdc modules.
However, when I try to do anything with the device:

mt -f /dev/ftape status
/dev/ftape: Device not configured

It's rft0. I tried other devices as well (dft0, etc.)

Also, when I execute in the ftape/modules directory, i.e.:

insmod ./ftape.o ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=3,3,3,3,3
insmod ./zftape.o ft_major_device_number=27
insmod ./bpck-fdc.o

The system log shows:

kernel: ftape v4.03-pre-2 11/05/98
kernel:
kernel: (c) 1993-1996 Bas Laarhoven
kernel: (c) 1995-1996 Kai Harrekilde-Petersen
kernel: (c) 1996-1998 Claus-Justus Heine (cl...@momo.math.rwth-aachen.de)
kernel:
kernel: QIC-117 driver for QIC-40/80/3010/3020/Ditto 2GB/MAX floppy tape drives.
kernel: Compiled for Linux version 2.0.36
kernel: installing QIC-117 floppy tape hardware drive ...
kernel: ftape_init @ 0x020441b0.
kernel: zftape for ftape v4.03-pre-2 11/05/98
kernel: (c) 1996, 1997 Claus-Justus Heine (cl...@momo.math.rwth-aachen.de)
kernel: vfs interface for ftape floppy tape driver.
kernel: Support for QIC-113 compatible volume table.
kernel: Compiled for Linux version 2.0.36 with versioned symbols
kernel: [000] zftape-init.c (zft_init) - zft_init @ 0x0207698c.
kernel: [001] zftape-init.c (zft_init) - installing zftape VFS interface for ftape driver ....
kernel: bpck-fdc.c: bpck_fdc_register @ 0x0201f3a8
kernel: [002] fdc-io.c (fdc_register_R3448e164) - Probing for bpck-fdc tape drive slot 0.
kernel: [003] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.
kernel: [004] bpck-fdc.c (bpck_fdc_query_proto) - Got 0xf8, expected either 0xc0 or 0x40.
kernel: [005] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.
kernel: [006] bpck-fdc.c (bpck_fdc_query_proto) - Got 0xf8, expected either 0xc0 or 0x40.
kernel: [007] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.
kernel: [008] 0 fdc-parport.h (ft_parport_claim) - Unable to grab address 0x03bc for <NULL>.
kernel: [009] 0 bpck-fdc.c (bpck_fdc_grab) - ft_parport_claim(fdc, &bpck->parinfo) failed: -16.
kernel: [010] 0 bpck-fdc.c (bpck_fdc_probe) - bpck_fdc_grab(fdc) failed: -16.
kernel: [011] 0 bpck-fdc.c (bpck_fdc_detect) - can't find bpck interface for ftape id 0.
kernel: [012] 0 bpck-fdc.c (bpck_fdc_detect) - ft_parport_probe(fdc, &bpck->parinfo) failed: -6.

This is obviously an error, but I'm not sure what to do to fix it.
Any clues? Thanks.

Piotr Szeptynski

unread,
Jan 13, 1999, 3:00:00 AM1/13/99
to
Bruce Barnett wrote:
>
> Thanks for the help. I am getting closer.
> I can load the ftape, ztape, and bpck-fdc modules.
> However, when I try to do anything with the device:
>
> mt -f /dev/ftape status
> /dev/ftape: Device not configured
>
> It's rft0. I tried other devices as well (dft0, etc.)

Valid devices fro ftape are: [n]qft[0-3] and [n]rawft[0-3]. However
documentation says that Ditto works as device number 0 only.
Don't use system built mt command. Get ftape-tools and use ftmt, e.g. like
this:
ftmt -f /dev/qft0 status
Manual pages for mt and ftmt are different so check them.


> kernel: [002] fdc-io.c (fdc_register_R3448e164) - Probing for bpck-fdc tape drive slot 0.
> kernel: [003] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.
> kernel: [004] bpck-fdc.c (bpck_fdc_query_proto) - Got 0xf8, expected either 0xc0 or 0x40.
> kernel: [005] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.
> kernel: [006] bpck-fdc.c (bpck_fdc_query_proto) - Got 0xf8, expected either 0xc0 or 0x40.
> kernel: [007] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.
> kernel: [008] 0 fdc-parport.h (ft_parport_claim) - Unable to grab address 0x03bc for <NULL>.
> kernel: [009] 0 bpck-fdc.c (bpck_fdc_grab) - ft_parport_claim(fdc, &bpck->parinfo) failed: -16.
> kernel: [010] 0 bpck-fdc.c (bpck_fdc_probe) - bpck_fdc_grab(fdc) failed: -16.
> kernel: [011] 0 bpck-fdc.c (bpck_fdc_detect) - can't find bpck interface for ftape id 0.
> kernel: [012] 0 bpck-fdc.c (bpck_fdc_detect) - ft_parport_probe(fdc, &bpck->parinfo) failed: -6.
>
> This is obviously an error, but I'm not sure what to do to fix it.

I am not sure, too. It looks like bpck driver can't find your Ditto.

Here is a piece of my config:

insmod ./bpck-fdc.o ft_fdc_threshold=16 ft_fdc_rate_limit=2000 \
ft_fdc_base=0x378 ft_fdc_irq=7

Bruce Barnett

unread,
Jan 14, 1999, 3:00:00 AM1/14/99
to
Piotr Szeptynski <P...@agsmedia.pl> writes:

> You can check it in your computer's bios setup. You can also compile ftape
> with auto-detection. I'm not setting up any irqs etc. and it works.

I followed your instructions, and I still get errors in the log files.


I also tried to find the info on the BIOS, but the Ditto on the
parallel port doesn't have any that I can tell. I tried to find in the
the Control Panel/System tool. I tried the exact values I got from the
Parallel Port, but this didn't work. The logs show:

kernel: [006] bpck-fdc.c (bpck_fdc_query_proto) - Got 0xf8, expected either 0xc0 or 0x40.

kernel: [009] 0 bpck-fdc.c (bpck_fdc_grab) - ft_parport_claim(fdc, &bpck->parinfo) failed: -16.


Bruce Barnett

unread,
Jan 18, 1999, 3:00:00 AM1/18/99
to
I'm not sure my last posting got out.Sorry for a duplicate.

>I am not sure, too. It looks like bpck driver can't find your Ditto.

>Here is a piece of my config:

>insmod ./bpck-fdc.o ft_fdc_threshold=16 ft_fdc_rate_limit=2000 \
>ft_fdc_base=0x378 ft_fdc_irq=7

How do I find the right value for ft_fcd_base?

I found the address of the parallel port, and of the floppy disk.
But the Iomega on the parallal port doesn't show up.

Is there some way I can test if I have the right address?
On other UNIX systems I used adb to probe the kernel memory.
Is there some set of values I can look for to make sure I have the
right values?

No matter what I try, I get

Bruce Barnett

unread,
Jan 18, 1999, 3:00:00 AM1/18/99
to
This is my current status. Linux 2.0.36. Ftape 4.03-pre-2. IBM
thinkpad 385XD. Iomega Ditto Max on parallel port.

I rebuilt the kernel
CONFIG_PARIDE=y -------------Devices on Parallel port
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m - Parallel tape
CONFIG_PARIDE_PG=m

CONFIG_PARIDE_ATEN=m
CONFIG_PARIDE_BPCK=y - BPCK YES
CONFIG_PARIDE_COMM=m
CONFIG_PARIDE_DSTR=m
CONFIG_PARIDE_FIT2=m
CONFIG_PARIDE_FIT3=m
CONFIG_PARIDE_EPAT=m
CONFIG_PARIDE_EPIA=m
CONFIG_PARIDE_FRPW=m
CONFIG_PARIDE_KBIC=m
CONFIG_PARIDE_KTTI=m
CONFIG_PARIDE_ON20=m
CONFIG_PARIDE_ON26=m


The parallel port is irq=7, io=ox03bc.
I executed the following:

insmod lp io=0x03bc irq=7
insmod ./ftape.o ft_fdc_driver=bpck-fdc,none,none,none ft_tracings=3,3,3,3,3
insmod ./zftape.o ft_major_device_number=27 # ${27-FT_MAJOR}
insmod ./bpck-fdc.o ft_fdc_threshold=16 ft_fdc_rate_limit=2000 ft_fdc_base=0x3bc ft_fdc_irq=7

The /var/log/messages file shows:


kernel: lp0 at 0x03bc, (irq = 7)


kernel: ftape v4.03-pre-2 11/05/98
kernel:
kernel: (c) 1993-1996 Bas Laarhoven
kernel: (c) 1995-1996 Kai Harrekilde-Petersen
kernel: (c) 1996-1998 Claus-Justus Heine (cl...@momo.math.rwth-aachen.de)
kernel:
kernel: QIC-117 driver for QIC-40/80/3010/3020/Ditto 2GB/MAX floppy tape drives.
kernel: Compiled for Linux version 2.0.36
kernel: installing QIC-117 floppy tape hardware drive ...

kernel: ftape_init @ 0x020411b0.


kernel: zftape for ftape v4.03-pre-2 11/05/98
kernel: (c) 1996, 1997 Claus-Justus Heine (cl...@momo.math.rwth-aachen.de)
kernel: vfs interface for ftape floppy tape driver.
kernel: Support for QIC-113 compatible volume table.
kernel: Compiled for Linux version 2.0.36 with versioned symbols

kernel: [000] zftape-init.c (zft_init) - zft_init @ 0x0207398c.


kernel: [001] zftape-init.c (zft_init) - installing zftape VFS interface for ftape driver ....

kernel: bpck-fdc.c: bpck_fdc_register @ 0x020813a8


kernel: [002] fdc-io.c (fdc_register_R3448e164) - Probing for bpck-fdc tape drive slot 0.
kernel: [003] 0 bpck-fdc.c (bpck_fdc_probe) - Bpck parallel port tape drive interface for ftape v4.03-pre-2 11/05/98.

-------------Trouble here-----
kernel: [004] 0 fdc-parport.h (ft_parport_claim) - Unable to grab address 0x03bc for <NULL>.
-------------
kernel: [005] 0 bpck-fdc.c (bpck_fdc_grab) - ft_parport_claim(fdc, &bpck->parinfo) failed: -16.
kernel: [006] 0 bpck-fdc.c (bpck_fdc_probe) - bpck_fdc_grab(fdc) failed: -16.
kernel: [007] 0 bpck-fdc.c (bpck_fdc_detect) - can't find bpck interface for ftape id 0.
kernel: [008] 0 bpck-fdc.c (bpck_fdc_detect) - ft_parport_probe(fdc, &bpck->parinfo) failed: -16.

Any suggestions on what I can do next?

to...@zingaretti.com

unread,
Jan 31, 1999, 3:00:00 AM1/31/99
to
Did you ever determine why you were getting the "unable to grab address at
0x03BC for <null>" error in the logfile? I get the same problem for
0x378.

I suspect that the parallel port is not enabled at a hardware level?

Any comments much appreciated.

Thanks,
-Tom-

In article <77vjes$pd$0...@206.231.152.133>,

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Bruce Barnett

unread,
Feb 1, 1999, 3:00:00 AM2/1/99
to
to...@zingaretti.com writes:

> Did you ever determine why you were getting the "unable to grab address at
> 0x03BC for <null>" error in the logfile? I get the same problem for
> 0x378.


Nope. I have no idea. I sent mail to Claus-Justus, hoping for a
clue.

0 new messages