From owner-freebsd-hardware Wed Jan 10 13:36:40 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 3B8EA37B400 for ; Wed, 10 Jan 2001 13:36:22 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0ALntg00891; Wed, 10 Jan 2001 13:49:55 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101102149.f0ALntg00891@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Shawn Barnhart" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Doing an install with the aac driver In-reply-to: Your message of "Wed, 10 Jan 2001 08:48:41 CST." <007501c07b14$6ca970a0$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 10 Jan 2001 13:49:55 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Can someone outline the "correct" procedure for doing an installation of 4.2 > using the aac driver? Since it was only recently MFCd, its not going to be > on the install disk. > > Is it merely a matter of putting a 4.2 kernel with the aac driver on the > install disk? Will that kernel get copied to the new system as the boot > kernel, or is there more involved? No. Use a 4.2-STABLE snapshot install disk set. Then once you've installed, but before you reboot, you need to build a kernel with the driver brought back (or you can build/install a KLD). > I'd be using this with a Netraid 4M, which from what I read on Mike Smith's > RAID page is compatible with this driver. I do believe so, certainly the one I have works. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message