Darrick Burch wrote:
Robert Hancock wrote:
Could be some kind of SATA PHY quirk or incompatibility that only shows
up in AHCI mode or something. It seems from the output that the SATA
link may be going up and down. You could try forcing 1.5Gbps
(libata.force=1.5Gbps if libata is built in, or force=1.5Gbps when the
libata module gets loaded) and see if that helps.
That appears to have done it--thanks! I feel kinda bad now because I was
suspecting a speed issue, but couldn't figure out how to force it. If I
had read the kernel documentation a little more, I would have found the
kernel option you mentioned. Duh. At any rate, thanks again.
Could be we need a quirk in libata for that drive to do that
automatically, or something.. Can you post the dmesg output from bootup
with the force 1.5Gbps option in place?
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
