From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 28 08:07:33 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8361C16A4CE; Fri, 28 Jan 2005 08:07:33 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C794F43D31; Fri, 28 Jan 2005 08:07:32 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [172.18.2.1] (axiell-gw1.novi.dk [130.225.63.24]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id j0S80cV4073732; Fri, 28 Jan 2005 09:00:50 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41F9F11E.2030006@DeepCore.dk> Date: Fri, 28 Jan 2005 09:00:30 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dave Myron References: <20050126183025.2550443D5D@mx1.FreeBSD.org> In-Reply-To: <20050126183025.2550443D5D@mx1.FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.6 cc: freebsd-hackers@freebsd.org cc: ctodd@chrismiller.com cc: freebsd-hardware@freebsd.org Subject: Re: Problem with FastTrak S150 SX4-M X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jan 2005 08:07:33 -0000 Dave Myron wrote: > It's not red but it is the PRI_RAID IDE connector. I have the controlle= r set > to IDE in the BIOS so it should act just as any other IDE controller > (according to the manual and many other sources). >=20 > I have two hard drives on the primary IDE (not on the controller) and a= CD > drive on the secondary IDE (also not on the controller). Then I have tw= o > more hard drives on the PRI_RAID channel (which *is* the P-ATA channel = on > the controller). Those two drives are getting the failure (or at least = one > is - see the error messages in my original text).=20 >=20 > I wish I had an S-ATA drive to test with so that I could verify that it= 's a > problem with the P-ATA part of this controller.=20 Thats a known problem, its partly fixed in -current, the real fix is in=20 the works. Try to take /sys/dev/ata from a fresh -current and let me=20 know if that helps you. --=20 -S=F8ren