Re: Colorado Trakker Parallel drive.

On Monday, 17. June 2002 15:58, smed wrote:
> 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
>
> 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 --->

These symbols should be exported by the parport module.  Since you 
have this module loaded, there is probably a versioning problem.  The 
version is encoding in the 8 hex-digits at the end of the symbol. 
When you compile ftape it is important that the LINUX_LOCATION in 
MCONFIG is pointing to the correctly configured kernel sources of the 
current kernel.

Nowadays, most distributions provide the correctly configured kernels 
now, there's a symlink /lib/modules/<version>/build.  If that is not 
the case the bestt way is to compile kernel and all modules yourself. 
There is also a configure option to compile both kernel and modules 
without the version tags. 

  Jochen

-- 
Jochen Hoenicke, University of Oldenburg, 26111 Oldenburg, Germany
Email: [email protected]  Tel: +49 441 798 3124
-
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