On 7/28/99 02:17, INTERNET:[EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:

> 
>Theo,
>
>       The answer is yes. You specify the parameters required via the
>append keyword of lilo. An example would be append="ide2=0x1e0,0x3e6,11".
>For more details, you need to read /usr/src/linux/Documentation/ide.txt
>
>Regards,
>Kenneth
>

OK, I tried this, but it didn't work either.  I read through 
Documentation/ide.txt, and following the advice there, I ran 
scripts/MAKEDEV.ide to make sure my devices were built correctly.  
Incorrectly built devices weren't the cause.  Then I added 
'ide1=0x170,0x376,15 hdc=cdrom' as a boot argument, but that didn't work 
either (in fact, there was no change at all to the boot messages).

In the meantime, I have rule out its being a distribution-specific 
problem.  I tried to install Slackware 4.0 to the first drive on the 
primary ide controller, but it couldn't find the CDROM drive either.

My next courses of action are to 1) put a hard drive on the secondary 
controller as a slave and see if the system's need to address that will 
force assignment of an IRQ for the secondary controller, or 2) follow 
another bit of advice in Documentation/ide.txt, to put the CDROM drive on 
the primary controller and mount any additional hard drives (in this 
case, my Linux system drive) on the secondary.  This second option will 
be the most difficult, because it will require changing /etc/fstab and 
telling lilo to expect root on /dev/hdc1 instead of /dev/hdb1, but I 
think, in the end, it might probably be the more permanent solution.

I haven't been able to fire off a message to DFI tech support yet, so I 
don't know what they have to say on this.  I am making the somewhat 
pessimistic assumption that they'll just tell me that they don't test for 
Linux compatability or some similar phrase.

Cheers,
Sean


                   Theo. Sean Schulze

[EMAIL PROTECTED]             [EMAIL PROTECTED]
*****************************************************
          Meandering to a different drummer.
          

Reply via email to