From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 21 15:02:26 2006 Return-Path: X-Original-To: hardware@freebsd.org 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 C1B9916A4E1 for ; Mon, 21 Aug 2006 15:02:26 +0000 (UTC) (envelope-from wjw@withagen.nl) Received: from freebee.digiware.nl (www.tegenbosch28.nl [217.21.251.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EE0E43D76 for ; Mon, 21 Aug 2006 15:02:25 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.67] (opteron.digiware.nl [212.61.27.67]) by freebee.digiware.nl (Postfix) with ESMTP id 0EBB32AAA0 for ; Mon, 21 Aug 2006 17:02:24 +0200 (CEST) Message-ID: <44E9CB30.4050703@withagen.nl> Date: Mon, 21 Aug 2006 17:03:12 +0200 From: Willem Jan Withagen User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Problem with new ASUS K8N-LR motherbord and 3ware 9550SX X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2006 15:02:26 -0000 Hi, I'm trying to build a large file server, for which I picked: Asus K8N-LR server board with dual core opteron 165 1Gb 8*250 Western Digital SATA Gb on a 3ware 9550SX controller. However, i ran into a snag here. As soon as I put the board into the motherboard, the system no longer wants to boot.... It still reports a IDE disk can cd-rom player found. But after that the system freezes.... Sort of like the controller gets lost in it's own BIOS. 2Ware her in Europe/Germany is not very abble to help any further. The Asus board is already at it's newest Bios revision. I've actually picked the 3ware controller after talking to 3ware people at CeBIT. And good impressions on current@ and stable@. Never considering that this might be a problem that still existed. Any suggestions for getting this solved... --WjW Please also cc: me since I'm not subscribed to hardware@