On 6/12/99 19:14, Jean-David Beyer at [EMAIL PROTECTED] wrote:
>"T. Sean (Theo) Schulze" wrote:
>
>> I am trying to install ftape on my machine, which will be running kernel
>> 2.2.9. (I am upgrading from 2.2.5, but haven't compiled the kernel yet.)
>> Under ftape in the kernel configuration, I have to enter the I/O
>> address, IRQ and DMA for my FDC. What is the best method for finding
>> each of these addresses?
>
>If you have not touched the controller for your tape drive, it may be listed
>in the manual for your controller, or in the MCONFIG file for ftape.
>
>If there is any possibility that the factory settings have been changed,
>look in the manual and look at the board to see what the settings are. You
>will probably need to know the base address (something like 0x370), the DMA
>number (something like 3) and the IRQ (something like 6).
>
Well, I don't know if I have touched the controller or not. I have tried
to run ftape (and taper) on this tape drive, an Iomega Ditto 2GB, before,
but I don't know if it changed any settings on the controller when I did.
As for looking at the drives documentation, the manual says that I need
to know the I/O address, IRQ and DMA, but doesn't give any hint as to
what they are or how to find their values. In the end, I dug a bit more
into the kernel settings shown in the help when you use menuconfig to
configure the kernel. It gives an option called Standard that assumes an
I/O address of 0x3f0, an IRQ of 6 and a DMA of 2. I used procinfo to
find out the IRQ of my floppy drive, and since it matched that given in
the Standard configuration in the kernel, I crossed my fingers that the
I/O address and DMA were also correct. I guess I will see when I begin
testing.
>If you are willing to run Windows on your machine, you can find it out by
>starting at My Computer and working your way down. I do not have Windows
>running at the moment, so I cannot tell you exactly how, but that is what I
>did to verify that the settings had not been changed. If the base address
>does not end in 0, you will probably want to round it down until it does;
>i.e., if it says 0x372-0x375, you will wish to use 0x370. Remember that I am
>making these numbers up: you must use the ones for your machine.
>
I do have Windows installed, but since I have never used this drive with
Windows, I don't know how much information there would be there on the
drive. I am sure there is a control panel somewhere, perhaps System,
that I could look in. But for now, I will test what I've got and only
look further if it doesn't work.
>> The version of ftape that I am trying to install is ftape-4.x-1999_06_02.
>
>Probably wise. I am using tape-4.x-1999_04_25 (or something from the end of
>April) and it works fine, but the most up to date is probably best.
>
As I understood the message traffic here, one needs to use the unstable
versions with the 2.2.x kernels.
>> A second question: I am planning on compiling kernel 2.2.9, installing
>> ftape-4.x-1999_06_02, and installing ftape-tools 1.07. What is the best
>> order to do this in? I see from reading the INSTALL doc that ftape's
>> configure looks for the kernel configuration, so I am assuming it would
>> be best to configure and compile the kernel first (my current kernel does
>> not have ftape support compiled in or as a module), then ftape, then
>> ftape tools. Is that the best sequence?
>
>I believe so. I never compiled the kernel, but it is necessary to have a
>kernel .config file to do these latest unstable releases of ftape, so do at
>least make xconfig (or your choice of configurators) before building ftape.
>
Using 'make menuconfig', compiling the kernel is pretty easy, and I do it
fairly often to upgrade to the latest version or to add support for
features I want to learn more about (e.g., IP masquerading, NFS, ftape).
Since my note the other day, I have compiled both ftape 4.x and
ftape-tools 1.07, and both compiles went (seemingly) without a hitch. I
wish I could say the same for the ftape-docs. For some reason(s) I
haven't figured out yet, that particular procedure loads up on errors and
then exits. If I have the time today, I will take a closer look at the
error messages I get and try to figure out what is wrong. I seem to
remember the same thing happening about six months ago when I tried to
install ftape's docs. Now, even after compiling and installing ftape and
ftape tools, 'man ftape' still tells me there is no such page.
Cheers,
Sean
T. Sean (Theo) Schulze
[EMAIL PROTECTED] [EMAIL PROTECTED]
****************************************************
How large does the Internet need to get before the
planet becomes self-aware?