From owner-freebsd-current@FreeBSD.ORG Tue Jun 22 21:59: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 948AE16A4CE for ; Tue, 22 Jun 2004 21:59:07 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B44B43D2D for ; Tue, 22 Jun 2004 21:59:07 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 12E5572DF4; Tue, 22 Jun 2004 14:58:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1117B72DF2; Tue, 22 Jun 2004 14:58:56 -0700 (PDT) Date: Tue, 22 Jun 2004 14:58:56 -0700 (PDT) From: Doug White To: Vinod Kashyap In-Reply-To: Message-ID: <20040622145703.E79584@carver.gumbysoft.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Patrick Hurrelmann cc: freebsd-current@freebsd.org Subject: RE: Problems installing Fre*BSD with 3ware 9500S-4LP 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: Tue, 22 Jun 2004 21:59:07 -0000 On Sun, 20 Jun 2004, Vinod Kashyap wrote: > > Looks like you cannot reboot after an install since the > driver is not part of the OS you just finished installing. > > This is what you can do: > > 1. While installing the OS, load the driver from a floppy > (sysinstall->Configure->KLDLoad). You are probably already > doing this. > 2. After installation, during reboot, escape to the loader > prompt, and again with a floppy with the driver inserted, > load the driver by doing 'load disk0:twa.ko'. > 3. Do a 'boot' and you should be able to boot. Vinod, the problem is that loader itself is crashing. It dies before you even get the loader prompt. Its as if the BIOS is not reading the array properly and returns bad data, or the BIOS is corrupting memory during certain reads. There are known cases where turning on DMA in the BIOS can cause BTX panics due to overly-promiscuous BIOS code, but this doesn't seem to be one of those cases. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org