Hi!
Trying to kill the keyboard, [EMAIL PROTECTED] produced:
> When I apply the ftape-4.02 patches for Kernel v2.0 to my 2.0.36
> Kernel, the first hunk failes. Maybe this is the cause of my
It's better *not* to put ftape into the kernel. Just say NO
to the ftape in the kernel and generate the ftape modules
once you are happy with the new kernel.
> When I try to access /dev/ftape, I get the error that the device does
> not exist.
/etc/conf.modules and depmod -a will take care of this, once
the modules work when inserted by hand.
> Then I do a modprobe for ftape, zftape and ftape-internal, access
> /dev/ftape again, and now I get an error telling me that the device is
> busy.
Did you specify the correct values and options (either in
/etc/conf.modules & ran depmod afterwards or by giving them
to insmod)?
Is your modules-package (modprobe & co) newer than 2.0.0?
(older ones cannot handle multi-arguments needed by ftape-4.x,
modules-2.1.xx warns that it won't work with 2.0.xx kernels
but actually will.)
What does ftmt -f /dev/ftape status say?
And most important ... *What do the logs say?*
> I don't access the floppy drives between booting and accessing
> /dev/ftape. Accessing /dev/ftape usually means using tar:
> tar -cf /dev/ftape RMAIL
You do have a card for the Ditto? I seem to remember (but
could be wrong) that the Ditto 2GB needs a booster card ...
please correct me?
-Wolfgang
--
PGP 2 welcome: Mail me, subject "send PGP-key".
Unsolicited Bulk E-Mails: *You* pay for ads you never wanted.
How to dominate the Internet/WWW/etc? Destroy the protocols! See:
http://www.opensource.org/halloween.html
