DragonFly bugs List (threaded) for 2005-02
ata controller card
here's my problem. I recently bought an external PCI ATA133 controller
in order to add two additional HDs to my box. This box has a normal
ATA100 controller and a SATA150 controller (to which my boot disk is
attached) on board. The CD-ROM is attached to the ATA100. So here's what
Without the new controller plugged in my ATA100 is atapci0 and the
SATA150 is atapci1. My boot disk is ad4.
If I plug in the controller it gets recognized as atapci0, my ATA100
becomes atapci1 and the SATA150 is atapci2. My boot disk is ad8 and
everything screws up.
Is this our bug or the hardware's bug? My feeling tells me that stuff I
plug in should always come "after" stuff that's on board.
What can I do about it? I've messed around with the kernel config but
there seems to be no way to force the new ATA133 controller to be
atapci2. And I'm still learning NEWBUS so looking at the source hasn't
brought up much either.
You can find a dmesg of the box with the new controller plugged in at:
I hope there's a way because I really need those disks badly. :|