From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 11 21:22:11 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 D236116A4CE for ; Fri, 11 Feb 2005 21:22:11 +0000 (GMT) Received: from webcrossing.com (mailhost.webcrossing.com [208.185.149.90]) by mx1.FreeBSD.org (Postfix) with SMTP id 7A94C43D3F for ; Fri, 11 Feb 2005 21:22:11 +0000 (GMT) (envelope-from jsoule@webcrossing.com) Received: from adsl-68-120-249-249.dsl.scrm01.pacbell.net [68.120.249.249] by webcrossing.com; Fri, 11 Feb 2005 13:22:10 -0800 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jeff Soule Date: Fri, 11 Feb 2005 13:22:09 -0800 To: "Vinod Kashyap" X-Mailer: Apple Mail (2.619.2) cc: freebsd-hardware@freebsd.org Subject: Re: Problems with 4.10 Release and "supported" hardware 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, 11 Feb 2005 21:22:12 -0000 No other controllers. The built in SATA controller is turned off in the bios. The bios sees the controller, and I am able to access and configure the controller at boot. No errors are reported and I am able to delete/create the RAID Array with no problems. I waited more then a few minutes (Went to get coffee when the 'Kernel Configuration Menu' appeared.) Heck, I even back revved the motherboard bios to the same version as a server that is working. The only difference is some changes 3ware made to the latest 9000 series card (BBU added and firmware changed to support BBU Battery Backup Unit) I suspect that their changes broke the twa driver but am not slick enough to get any further with this :-( My vender is building another box with a different Supermicro Motherboard that does work, (Already verified), but the bus speed is slower so it is not the best solution by a long shot... On Feb 11, 2005, at 12:56 PM, Vinod Kashyap wrote: > Do you see PCI controllers other than 3ware? Do you > see them (other PCI controllers) if the 3ware controller > is not plugged in? Does the motherboard BIOS detect > the 3ware controller? i.e., do you see messages from > the 3ware BIOS at startup? For how much time did you > wait at the 'Kernel Configuration Menu'? You might want > to try waiting longer... > > One other thing I have observed is that, if there are > any degraded units attached to 3ware, the 3ware BIOS > waits for 30 seconds rather than the usual 5 seconds, > and when this happens, _all_ PCI controllers are seen!