Iomega Ditto 3200

Hello,
I have an Iomega Ditto 3200 tape drive, and compiled ftape.o into
kernel, zftape.o as module. Then I installed the ftape-modules.
Now, zftape loaded, I'm still not able to use the drive:
server:~# tar -cf /dev/ftape /home/jonas/
tar: /dev/ftape: Cannot open: No such device or address
tar: Error is not recoverable: exiting now

server:~# lsmod
Module                  Size  Used by    Not tainted
zftape                 58952  -1
[...]

ftape-modules has installed these modules:
bpck-fdc.o        fdc-parport.o     ftape-internal.o  trakker.o

do I have to load one? ftape-internal is not loadable:
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol schedule_timeout
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol __wake_up
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol __udelay
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol kmalloc
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol create_proc_entry
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol vfree
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol remove_wait_queue
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol request_module
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol proc_mkdir
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol kfree
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol remove_proc_entry
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol add_wait_queue
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol proc_root
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol sprintf
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol jiffies
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol __vmalloc
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol printk
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol irq_stat
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o:
unresolved symbol __const_udelay
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o: insmod
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o failed
/lib/modules/2.4.19/kernel/drivers/char/ftape/lowlevel/ftape.o: insmod
ftape-internal failed

I think the problem is that I have installed ftape.o into the kernel,
not as module. But do I need ftape-internal.o?

bye
 mejo

-- 
Efficiency and progess is ours one more
Now that we have the Neutron bomb
It's nice and quick and clean and gets things done
Kill kill kill kill kill the poor tonight
-
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