On Tue, Jul 06, 1999 at 10:07:37PM +0200, Alex Schroeder wrote:
> 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
> problem. I upgraded my distribution a while ago, installing the new
> kernel. Now I find that ftape doesn't work anymore, eventhough it
> worked with my old kernel.
>
> When I try to access /dev/ftape, I get the error that the device does
> not exist.
>
What do you get on accessing /dev/qft0 instead of /dev/ftape?
> 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.
>
Ok, just for making sure:
Please present the outputs of
cat /proc/interrupts
cat /proc/ioports
cat /etc/conf.modules
> 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
>
> I recompiled and installed the kernel, recompiled and installed the
> modules, recompiled and installed ftape, added the options to
> /etc/conf_modules which got lost when I upgraded my distribution --
> but it still doesn't work.
>
> Did I forget anything? Will updating to ftape-4.03-pre-something
> help? Is there a new patch for Kernel versions 2.0.36 out there?
>
Sorry, I can't answer this, I am not familiar with that 2 GB drive;
upgrading to the most recent ftape-version is presumably a good idea,
but I'm not sure if it really helps...
Bye, Juergen.
--
****************************************************************
* Juergen Leising; email: [EMAIL PROTECTED] *
* http://www.stud.uni-bayreuth.de/~a0037/ *
****************************************************************
