--- Ron Stodden <[EMAIL PROTECTED]> wrote:
> Questions:  
> How do _you_ determine the appropriate append strings for the Promise
> channels from cat /proc/pci/?
> How do _you_ determine the appropriate append strings for the mobo
> IDE channels?
> 
> Once I have this information, I can experiment in your tracks.

Well, you have to boot with rescue disc or something (you can also get the info
from windows), and display /proc/pci:

[root@fulgore:~]# cat /proc/pci 

...

  Bus  0, device   7, function  1:
    IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (rev
0).
      Master Capable.  Latency=32.  
      I/O at 0xff90 [0xff9f].
  Bus  0, device  11, function  0:
    Unknown mass storage controller: Promise Technology, Inc. 20262 (rev 1).
      IRQ 10.
      Master Capable.  Latency=32.  
      I/O at 0xfff0 [0xfff7].
      I/O at 0xffe4 [0xffe7].
      I/O at 0xffa8 [0xffaf].
      I/O at 0xffe0 [0xffe3].
      I/O at 0xfe80 [0xfebf].
      Non-prefetchable 32 bit memory at 0xffba0000 [0xffbbffff].

...

Then follow this template: "ide0=ADD1,ADD2+2 ide1=ADD3,ADD4+2" where ADDx are
the staring I/O addresses listed after the "at" (the ones in brackets, are the
ending add.), and x is the line number. In my case, to have the Promise
controller handle ide0 and ide1, the append string would be:

append = "ide0=0xfff0,0xffe6 ide1=0xffa8,0xffe2"

Note that I don't have to explicitly tell the kernel to put the motherboard
controllers to ide2&3, since it will do it automatically.

> > (4) Linux is able to identify the drives on the channels correctly, but
> when it
> > tries to use DMA to talk to them for the partition check, it hangs (in
> fact,
> > this is not completely correct, it hangs on just one drive, and no it is
> not a
> > HW problem).
> 
> I have not experienced this (yet?).   My new mobo and drives accept
> DMA operation - to great advantage.  You may possibly be striking a
> very common defect in mobos.

I have a feeling it is related to Western Digital drives, but I don't think it
is a hardware problem, since it consistently works with some kernels and not
with others. So I guess the problem could be that one kernel may have an ide
driver with a WD workaround, and the other not.

=====
________________________
Eugenio Diaz, BSEE/BSCE   
Linux Engineer
[EMAIL PROTECTED]

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

Reply via email to