On Tue, Feb 19, 2008 at 08:38:50PM +0000, markbilk at comcast.net wrote: > Does anyone know if and how this was resolved? > Or should such motherboards still be avoided? It was fixed in a recent SATA driver infrastructure update. So, for example, RHEL 5 update 1 is OK, but RHEL 5 update 0 is not. -- greg