Colorado Trakker Parallel drive.

smed <[email protected]> Mon, 17 Jun 2002 09:58:19 -0400
Newsgroups gmane.linux.tape
Message-ID <20020617135819.GA2881@thebog>
Good day folks:

I'm having difficulty with a Colorado Trakker 250 I've inherited whereby I can't 
seem to get the trakker driver to load.

Details:

Using ftape - these modules load successfully.
parport and parport_pc drivers load successfully per /proc/parport/0/hardware

Platform - Linux 2.2.16  Slackware 7.1

I've followed the instructions to the 'T' for loading the parport, parport_pc, ftape and associated drivers.
Read all the Hot-to's ftape/parport

Compiled the ftape driver from scratch several (billion?) times....still wont load the trakker driver.

Here is the specific complaint(s):

######################################################################################################3
{snip}

root@//Boardwalk /root --->lsmod
Module                  Size  Used by
zft-compressor         16860  -1  (unused)
zftape                 91692  -1  [zft-compressor]
ftape                 148248   0  [zft-compressor zftape]
parport_pc              7400   0  (unused)
parport                 6952   0  [parport_pc]
iBCS                  135636   0 
de4x5                  41172   1 
bsd_comp                3764   0  (unused)
ppp                    20652   0  [bsd_comp]
slip                    7388   0  (unused)
slhc                    4504   0  [ppp slip]
root@//Boardwalk /root --->modprobe trakker
/lib/modules/2.2.16/misc/trakker.o: unresolved symbol parport_claim_or_block_R7098ea8a
/lib/modules/2.2.16/misc/trakker.o: unresolved symbol parport_enumerate_R00173fa6
/lib/modules/2.2.16/misc/trakker.o: unresolved symbol parport_unregister_device_Rf190b30a
/lib/modules/2.2.16/misc/trakker.o: unresolved symbol parport_register_device_Rc0a47fb4
/lib/modules/2.2.16/misc/trakker.o: unresolved symbol parport_release_R4941ccbd
/lib/modules/2.2.16/misc/trakker.o: insmod /lib/modules/2.2.16/misc/trakker.o failed
/lib/modules/2.2.16/misc/trakker.o: insmod trakker failed
root@//Boardwalk /root --->
 
{snip}
###########################################################################################################################3


Where can I go to find out what these errors mean?
I'm fairly sure that it's complaing about the parallel port and that's why it won't load....however the /proc/parport filesystem
indicates that everthing is setup properly.
I can load lp support?
I can't see any reason why this driver (trakker.o) wont laod.
Now there is the /ftape-4.??/MCONFG file that must be editted prior to compiling the driver....I have tried editting this several ways
There is a section specifically for the trakker tape drives.....I can't imagine why it's not working.
Here is an excerpt from my /ftape/MCONFIG file:


#################################################################################################################################3
{snip}


# For a HP Colorado Trakker parallel port drive, try
#
TRAKKER_DEV=0
 FDC_OPT +=     -DCONFIG_FT_FDC_PARPORT_$(TRAKKER_DEV)=-1 \
                -DCONFIG_FT_PAR_$(TRAKKER_DEV)=1 \
                -DCONFIG_FT_TRAKKER_$(TRAKKER_DEV)=1

{snip}
##################################################################################################################################


Now....there is another section where you can SPECIFY the IOBASE, IRQ and DMA for the drive....but there doesn't seem to be 
any of the those parameters available int he trakker section of the driver config file.  Do I need to add them?
THis file is not very clear on what I'm supposed to do in this case....it is fairly well commented though and seems to imply that you
can only uncomment out one section of the file.


Anyway.....I know I'm on the right path here.....but I"m getting fairly frustrated with this drive.
I have compiled and inserted ftape and it's associated modules before on another machine where I recently was able to
put an old Iomega Ditto 800 Parallel tape drive in service.  This was a major headache as well....took nearly 12 man hours to figure
out, however I got it working eventually.  This trakker driver is stumping me.


Any thoughts, suggestions, ramblings welcome. 
I need to get this issue worked out.....it would be ashame to have to throw-out a perfectly good tape drive....even if it
only holds 250MB.......

Thanks in advance......


smed







-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html