pri-slave not detected/cable error [Was: Re: HEADSUP: ATA mkIII has been committed]

Am Mittwoch, 30. März 2005 14:07 schrieb Søren Schmidt:
> As pr subject make world is needed to get things in sync again.
>
> Let me know is there are problems / success stories..

Hi Søren,

-current doesn't detect my primary slave drive while RELENG_5 had no problem.
When I connect the slave drive to the secondary port everything is fine.
Also, if the slave drive is connected, ata reports that there's no 80pin 
cable, which is wrong.

Here the chipset info:

 atapci0: <VIA 8235 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xb400-0xb40f at device 17.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0

Here the working state:
ad0: 76319MB <Seagate ST380011A 3.06> at ata0-master UDMA100
ad2: 57259MB <MAXTOR 6L060J3 A93.0500> at ata1-master UDMA133

And that's what I get when I connect the drive from secondary master to 
primary slave:
ad0: DMA limited to UDMA33, device found non-ATA66 cable
ad0: 76319MB <Seagate ST380011A 3.06> at ata0-master UDMA33

Cables are all 80pin, jumper set to CS, but no change if I set the first disk 
to master and the second to slave, same error.

Thanks,

-Harry
>
> Give Thomas a chance to catch up with atapicam, he's on the ball and he
> is where questions/suggestions should be directed on that matter.
>
> Enjoy!