From owner-freebsd-hardware@FreeBSD.ORG Fri Nov 7 00:15:24 2003 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 5CA9216A4CF for ; Fri, 7 Nov 2003 00:15:24 -0800 (PST) Received: from mega.octafed.dk (cpe.atm2-0-1141033.0x50a494ce.boanxx15.customer.tele.dk [80.164.148.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A3F843FB1 for ; Fri, 7 Nov 2003 00:15:23 -0800 (PST) (envelope-from moron@octafed.dk) Received: from mail.octafed.dk (localhost.octafed.dk [127.0.0.1]) by mega.octafed.dk (Postfix) with SMTP id A86FEA974 for ; Fri, 7 Nov 2003 09:14:23 +0100 (CET) Received: from 193.89.137.29 (SquirrelMail authenticated user moron@octafed.dk) by mail.octafed.dk with HTTP; Fri, 7 Nov 2003 09:14:23 +0100 (CET) Message-ID: <4510.193.89.137.29.1068192863.squirrel@mail.octafed.dk> Date: Fri, 7 Nov 2003 09:14:23 +0100 (CET) From: moron@octafed.dk To: freebsd-hardware@freebsd.org User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Regarding SuperMicro 6013P-T with Intel SATA controller. 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, 07 Nov 2003 08:15:24 -0000 Hello. I'm sitting here with the Supermicro 6013P-T and the optional (but important) Intel SCRZCR Sata controller. I need to install FreeBSD on this machine, but i'm having trouble with it when I use the Intel controller. When the system boots on the 4.9 floppies it states that it is not able to work out which disk it's booting from. The 5.1 floppies fails with the same error, as for the FreeBSD 4.4 in Intel's documentation. The controller is running with it's newest firmware, and I have used Intel's docs for their example on how to use it. So far I'm inclined to say the problem doesn't lie with the controller at all, but with the Supermicro board. Any help would be appreciated. Thanks. -- Peter Lønberg