From owner-freebsd-questions@FreeBSD.ORG Wed Jan 3 19:53:04 2007 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9ADFB16A412 for ; Wed, 3 Jan 2007 19:53:04 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 62CCC13C45A for ; Wed, 3 Jan 2007 19:53:04 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l03JPk4o082789; Wed, 3 Jan 2007 11:25:47 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: "Dan Mahoney, System Admin" Date: Wed, 3 Jan 2007 14:23:17 -0500 User-Agent: KMail/1.9.4 References: <20070103024752.J35175@prime.gushi.org> <20070103123155.V52719@prime.gushi.org> <200701031418.13125.lists@jnielsen.net> In-Reply-To: <200701031418.13125.lists@jnielsen.net> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701031423.17415.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: questions@freebsd.org Subject: Re: Easier way to install on 3ware 9550 card? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jan 2007 19:53:04 -0000 On Wednesday 03 January 2007 14:18, John Nielsen wrote: > On Wednesday 03 January 2007 12:34, Dan Mahoney, System Admin wrote: > > On Wed, 3 Jan 2007, Per olof Ljungmark wrote: > > > Dan Mahoney, System Admin wrote: > > >> Hey all, > > >> > > >> I have a new system with NO FLOPPY CONTROLLER and a 3ware 9550 card. > > >> It's a 1u system -- sticking extra things into PCI slots as a > > >> workaround is likely to be impossible. > > > > > > I don't think you need a driver - it's already there. > > > apropos 3ware > > > twa(4)- 3ware 9000/9500/9550 series SATA RAID controllers driver > > > twe(4)- 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapter driver > > > > Oh I'm sorry, then why didn't I just install the OS? Because it said "no > > drives found!" > > > > The card doesn't probe at boot, and there's an elaborate howto on 3ware's > > site that describes HOW to get it to probe at boot. > > > > While I myself stated that the driver DOES appear to be in the base, for > > whatever reason the kernel on the install CD doesn't include it, nor the > > ability to kldload a module from anyplace easy. > > You were on the right track with the emergency shell, but the "Fixit" mode > (now included on disk 1 for your convenience) gives you a lot more > flexibility (inclusion of "ls" is just the start!). Have you tried > something like this? > > 1) Boot to complete install CD > 2) Go into "Fixit" mode (not just the emergency shell) > 3) # sysctl kern.module_path="/dist/boot/kernel" > 4) # kldload twa > 5) # exit > 6) proceed with installation > > This shouldn't be necessary though, since twa is included in GENERIC for > both FreeBSD 6.1 and 6.2 (did you say what version you were trying to > install?). > > Now, if your controller is too new to be included in the shipping version > of twa then that's another matter. If you have a binary kernel module that > uses a different driver name from the vendor you could use the same general > approach, but you'd want to configure your network interface and set up > your NFS mount prior to step 3, and include the appropriate NFS path in the > sysctl command in step 3. Forgot to mention you'd also need to manually copy the vendor driver and modify /boot/loader.conf on the newly installed system so it could actually boot.. you could easily take care of that from the fixit mode shell after the installation, though.