🚀 go-pugleaf

Rob Crittenden (rcrit@saa.noaa.gov) wrote:
: In article <4runb2$ri8@news.mel.aone.net.au>,
: 	daveney@speednet.com.au (Graham Daveney) writes:
: >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.
: >
: > ...removed...
: 
: If I remember correctly, a patch was needed for 1.2.13 to handle > 2
: drives with EIDE.  I'd recommend that you upgrade to 2.0 for more reasons
: than just that.  You shouldn't need to do any LILO magic to get it to
: work.  When the kernel boots, does it recognize the 2 ide controllers?
: 
: On my EIDE card (Promise 2300+) the primary controller (Int 14) has
: the full VLB data path, the secondary (Int 15) is the standard IDE
: bus (16-bits), so I have the faster/most use drives connected to primary
: and the less-frequently used on the secondary.  Your milage may vary.
: 
: Rob

Thanks so much Rob !

    I recompiled the kernel with the newer ide driver (still using 1.2.13), and
switched the Quantum over to the second ide controller and the kernel recognised
the Quantum as hdc now. When I tried to do fdisk /dev/hdc I was getting an error
saying something like "Drive not recognisable" or something like that. Then I 
remembered that there was a problem with the Slackware distribution and hdc hdd.
I did a search on altavista and saw a reply that you had suggested to someone
a little while ago saying that they should run /usr/src/linux/drivers/block/
MAKEDEV.ide if they had the Slackware distribution. Anway I did that and I could
mount the beastie.

   Problem solved.
 
   I did have an older IDE card like yours where the secondary controller was
a regular 16 bit ISA controller, but now I am using a newer card which I think 
has the second port has a full VLB data path. I don't know I will have to check.



Many Thanks
Graham