From: firehawk@polaris.unm.edu (-* FireHawk *-) Subject: Re: Linux Support for 'secondary' AT controllers Date: 12 Feb 1993 14:51:46 GMT
In article <1lfgkfINNdih@senator-bedfellow.MIT.EDU> alsaggaf@athena.mit.edu (M. Saggaf) writes:
:I have an interesting situation (well, desparate might be a better
:word for it). My system has and IDE drive connected to and IDE
:interface card, and an MFM drive connected to a 16-bit Seagate ST22
:MFM controller. The ST22 has its own BIOS and uses an alternate BIOS
:address and drive I/O port, so it can co-exist in harmony with the IDE
:drive. The CMOS is setup with type 0 (NO DRIVE PRESENT) for the MFM
:drive, since the controller has its own BIOS.
Glad I'm not the only one who has a MFM/IDE combo. I posted a similar
question a while back and didn't get answer. On my system, the MFM controller
is the primary while the IDE is the secondary. The 16-bit IDE controller has
its own BIOS and uses and alternative BIOS address and drive I/O port. It also
corresponds as type 0 in the CMOS. In DOS, these two coexist beautifully but
not so in Linux. Linux is able to acknowledge the MFM drive and its controller
but is unable to read the IDE and its controller.
:Does anybody have a recommendation in this regard? Where can find the
:modified driver, or who is the person that already did the
:modification?
If someone has an answer to this question, please post it! After I posted
my question concerning the MFM/IDE coexistence in Linux, I heard from other
people who have a similar setup and also want to know how to get it to work.
If I get and answer, I'll forward a response to those people. If a definite
answer can be found, could it added to the FAQ since this question seems to
be popping up often? In fact, could future kernel releases support these type
of BIOS addressible MFM/IDE hard disk controller cards?
Cheers! =)
--
INTERNET: firehawk@carina.unm.edu
UUCP: ...!ariel!firehawk