From owner-freebsd-questions@FreeBSD.ORG Wed Jan 10 10:32:58 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 3B11C16A40F for ; Wed, 10 Jan 2007 10:32:58 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp02.sth.basefarm.net (ch-smtp02.sth.basefarm.net [80.76.149.213]) by mx1.freebsd.org (Postfix) with ESMTP id BD6A313C45A for ; Wed, 10 Jan 2007 10:32:55 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-29-241.bredband.comhem.se ([83.253.29.241]:51803 helo=falcon.midgard.homeip.net) by ch-smtp02.sth.basefarm.net with smtp (Exim 4.63) (envelope-from ) id 1H4alK-0004yy-8e for questions@freebsd.org; Wed, 10 Jan 2007 11:32:55 +0100 Received: (qmail 38222 invoked from network); 10 Jan 2007 11:32:52 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with SMTP; 10 Jan 2007 11:32:52 +0100 Received: (qmail 49459 invoked by uid 1001); 10 Jan 2007 11:32:52 +0100 Date: Wed, 10 Jan 2007 11:32:52 +0100 From: Erik Trulsson To: "Dan Mahoney, System Admin" Message-ID: <20070110103252.GA49447@owl.midgard.homeip.net> Mail-Followup-To: "Dan Mahoney, System Admin" , John Nielsen , questions@freebsd.org References: <20070103024752.J35175@prime.gushi.org> <20070103123155.V52719@prime.gushi.org> <200701031418.13125.lists@jnielsen.net> <200701031423.17415.lists@jnielsen.net> <20070103153916.S52719@prime.gushi.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070103153916.S52719@prime.gushi.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-ACL-Warn: Too high rate of unknown addresses received from you X-Scan-Result: No virus found in message 1H4alK-0004yy-8e. X-Scan-Signature: ch-smtp02.sth.basefarm.net 1H4alK-0004yy-8e 892a5e551c6a4340c605aa0229a19ae7 Cc: questions@freebsd.org, John Nielsen 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, 10 Jan 2007 10:32:58 -0000 On Wed, Jan 10, 2007 at 05:24:26AM -0500, Dan Mahoney, System Admin wrote: > On Wed, 3 Jan 2007, John Nielsen wrote: > > Apologies for top-posting. > > I've made some progress with this, but as I suspected, I'm screwed on > "namespace collision". I.e. I am unable to load a version of twa.ko that > supports my 3ware card because a previous version of twa.ko that does not > support it is already in the generic kernel. Changing the name of the > loadable doesn't help, either. > > It looks like I might have to make my own release, and my own ISO, using > the driver source from the 3ware site. > > Does anyone have an easier way of doing this? Might some of the following information from 3ware be of help? http://www.3ware.com/KB/article.aspx?id=15003 http://www.3ware.com/KB/article.aspx?id=14850 > > I've already emailed Scott Long asking about the possibility of the > inclusion of the new twa driver in the next FreeBSD, but I fear we're too > far down the release process, so it could be a YEAR before there's a > RELEASE that supports it. > > -Dan > > >>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. > > > -- Erik Trulsson ertr1013@student.uu.se