🚀 go-pugleaf

Hi Guys,

    running kernel 1.2.13
    have had WD Caviar 800meg drive working fine.
    just added Quantum Sirocco 2.5gig EIDE.

    The "problem" is that I can only get the drive working when I jumper the
WD as master and the Quantum as slave and daisy chain the Quantum off the WD.

    Problem with this as I see is that things are real slow when trying to use
the drives in tandem. From hearing what other people say as well as many
readings of the /usr/src/linux/drivers/block/README.ide I understand that you
can run drives off the second interface/port on the IDE card.

    When I jumper the Quantum as slave and daisy chain it off the WD the BIOS
will autodetect it, all 4969 cylinders of it. No worries. If I hang the Quantum
off the second IDE interface/port BIOS will not recognise it, and Linux seems
to have problems as well.

    I have heard that if you use LILO (I don't at the moment but that can
change), you can pass arguments to force the detection of drives that the BIOS
won't or can't recognise.

    Question: should I worry about getting the Quantum working off the second
interface/port, or just be happy with the daisy chained solution ?

    Question: once I get LILO happening. What is the line command that I use
so that Linux can see the drive even if the BIOS is oblivious of its existence.

    Question: how do I ensure that the Quantum is assigned its own IRQ, on top
of that how do I find out which memory address it wants to use, or more
importantly how do I assign the memory address. Should I throw away the $35
VLA IDE card that I am using and buy something a bit more substantial.
 

Thanks for your time guys, this one has been a bit of a headache.


Graham Daveney
daveney@speednet.com.au