From owner-freebsd-current@FreeBSD.ORG Fri May 7 16:47:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7F3E16A4CE for ; Fri, 7 May 2004 16:47:07 -0700 (PDT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.62.205.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1003B43D1F for ; Fri, 7 May 2004 16:47:07 -0700 (PDT) (envelope-from forrie@forrie.com) Received: from [127.0.0.1] (i-95.forrie.net. [192.168.1.95]) by forrie.com with ESMTP id i47NkvOt023209 for ; Fri, 7 May 2004 19:47:00 -0400 (EDT) (envelope-from forrie@forrie.com) Message-ID: <409C1FEF.8030906@forrie.com> Date: Fri, 07 May 2004 19:46:55 -0400 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 0.6+ (Windows/20040506) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean X-Mailman-Approved-At: Sat, 08 May 2004 05:10:16 -0700 Subject: SATA driver issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2004 23:47:07 -0000 Søren, Unfortunately, the first 2 drives were wiped out from having been tested... installed Windows/XP, and it all worked fine. The motherboard I have is a SOYO Dragon Platinum Edition which has the Silicon Image controller. I want to be sure what the problem is before I begin installing FreeBSD-5.2 again. I read in some release notes there were some issues with SATA, but I'm not certain if those issues still apply to the -CURRENT codebase. Thanks. Forrest Forrest Aldrich wrote: > I recently updated my FreeBSD 5.2 system to CURRENT via CVSup, and then > the system wasn't recognizing the secondary (slave) SATA drives. I > thought this might be a hardware issue, so brought it in to be looked > at. Turn out, it's fine with other operating systems (Windows/XP, et > al). So I'm presuming something with SATA support went bad in the > current codebase. Has anyone information about this or a fix. Please at least provide the output from dmesg so I have a chance to see what kind of HW we are talking about. A dmesg from a working kernel would be real handy as well... -- -Søren