On Tue, Sep 14, 2004 at 02:06:18PM -0400, Jeff Garzik wrote:

Michal 'hramrach' Suchanek wrote:

quoted

imho it did not query it, it is simply bogus. afaict the drive does not
produce write errors so the code cannot query it whatever it does.
But i do not know anything about ata or the kernel ata drivers, I did
not even try to look.

Currently I have another drive attached to the sata dongle and neither
bios nor Linux can see it. Perhaps it is because  the drive is switched
to slave or it does not like the drive rack.

The drive rack works, just the drive has to be master or cable select.
The weird thing is the driver would report there  is no drive on the
second channel but would not say anything about the first channel where
the drive is connected.

ahhhhhh, that may be a clue.  If you are attaching a PATA drive via a 
bridge, that is very different from attaching a SATA drive, in terms of 
field behavior across the controller spectrum.

There are limitations on bridges.  Does Brad Campbell's patch (attached) 
work for you?

Looks great!
I have just compiled my new kernel on the drive connected through sata
using the patched libata driver.

Thanks

Michal Suchanek