To: linux-kernel@vger.kernel.org
From: Adam Jones <adam@yggdrasl.demon.co.uk>
Subject: Re: 2.4 ICH4 + SATA bridge problems
Date: 11 Nov 2003 12:34:41 GMT
Organization: none
Message-ID: <boql11$qps$1%proserpine.haus@yggdrasl.demon.co.uk>
References: <20031107013554.72178e8e.rumi_ml@rtfm.hu>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1266
Lines: 20

In a futile gesture against entropy, Rumi Szabolcs wrote:

> I have tested this with two different drives, a fully native
> SATA drive (ST3160023AS) and a pseudo-SATA drive (MX6Y120M0)
> which uses the same Marvell chip internally to convert SATA
> back to PATA because thats what the drive really is. The
> result is that both drives show up as UDMA100 in the BIOS
> and as UDMA33 in the kernel.

IIRC this is due to a problem with the cable-detection code in 2.4.22 -
it looks for an 80-conductor cable (which SATA certainly doesn't have!)
and sensibly refuses to enable modes above UDMA2 if one is not present.

I believe this is fixed in 2.4.23-pre, so the best answer is probably
either to install the latest of those or to wait for .23-final to
appear.  (I have the same issue; I've opted for the latter.)
-- 
Adam Jones (adam@yggdrasl.demon.co.uk)(http://www.yggdrasl.demon.co.uk/)
.oO("sudden vision of a klein pizza"                                   )
PGP public key: http://www.yggdrasl.demon.co.uk/pubkey.asc

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/