From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 19 15:13:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2863616A409 for ; Thu, 19 Apr 2007 15:13:16 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (gizmo.acns.msu.edu [35.8.1.43]) by mx1.freebsd.org (Postfix) with ESMTP id 033B813C44C for ; Thu, 19 Apr 2007 15:13:15 +0000 (UTC) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: from gizmo.acns.msu.edu (localhost [127.0.0.1]) by gizmo.acns.msu.edu (8.13.6/8.13.6) with ESMTP id l3JEdtXi062309; Thu, 19 Apr 2007 10:39:55 -0400 (EDT) (envelope-from jerrymc@gizmo.acns.msu.edu) Received: (from jerrymc@localhost) by gizmo.acns.msu.edu (8.13.6/8.13.6/Submit) id l3JEdt7k062308; Thu, 19 Apr 2007 10:39:55 -0400 (EDT) (envelope-from jerrymc) Date: Thu, 19 Apr 2007 10:39:55 -0400 From: Jerry McAllister To: Murray Taylor Message-ID: <20070419143955.GB62190@gizmo.acns.msu.edu> References: <04E232FDCD9FBE43857F7066CAD3C0F12DF17C@svmailmel.bytecraft.internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <04E232FDCD9FBE43857F7066CAD3C0F12DF17C@svmailmel.bytecraft.internal> User-Agent: Mutt/1.4.2.2i X-Mailman-Approved-At: Thu, 19 Apr 2007 15:31:21 +0000 Cc: freebsd-hackers@freebsd.org, FreeBSD Mailing List Subject: Re: IBM / FreeBSD Install problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 15:13:16 -0000 On Thu, Apr 19, 2007 at 10:14:13AM +1000, Murray Taylor wrote: > Server: IBM X3850 (88633SM) > CPU X 4: 40K2522 > HDD X 6: 40K1051 > IBM ServeRAID 8i: 39R8729 > > We are attempting to install FreeBSD 6.2-RELEASE onto this machine and > are running into a problem getting the operating system to recognise the > RAID controller. As a result not finding any disks when it comes to > installing the O/S. > > We have attempted various modifications to the boot process, including > the loading of an "aac" module, which according to the BSD website, > should provide support for this type of controller. I have only installed on a couple of raids and so don't know about them all or even this one. So, this might not apply to your situation. But, I found that I had to study DMESG very carefully to find out what device to use for them. The system seemed to put out a lot of messages that looked like other device names but in the end there was just one little line that pointed to the correct one. The most recent one was a Dell Perc 3i or something like that and I had to run the fixit and study the boot messages to figure it out. I don't have that one available to look at what it turned out to be, but it was more simple than I first thought from all the stuff it wrote out. After mucking with fixit a bit, then sysinstall seemed to figure it out OK. I don't remember actually changing anything - just fishing around a while. I may have run fdisk under fixit to look at things and maybe delete some slices. So, rather than trying to change things right off, I would suggest looking carefully at stuff and trying to determine what it is already doing. Anyway, good luck, ////jerry > > When we attempt to boot to OS to install after making these above > modifications, the boot loader advises that this module already appears > to be loaded, which contradicts what I believe. In any respect, it > doesn't work either way (with or without the module manually loaded). > > One side note (which i don't think is contributing) is that when I > attempt to start the boot loader with ACPI enabled, it freezes with the > message "cpu id 38 too high". However if I boot the boot loader with > ACPI disabled, this message dissapears. It _may_ be a possibility that a > bi-product of disabling the ACPI is causing the RAID controller to have > issues. This appears to be an issue because of the X4 CPU count ?? > > That's a quick summary of the problem we have, and the path(s) we have > been down to date to attempt to fix it. Any help you can provide would > be very much appreciated. We are at the position now where we are > prepared to pay for consulting services to get it going. > > Dave Faulkner / Murray Taylor > > Bytecraft Systems > > > -- > > "Any intelligent fool can make things bigger and more complex... It > takes a > touch of genius - and a lot of courage to move in the opposite > direction." > --Albert Einstein > --------------------------------------------------------------- > The information transmitted in this e-mail is for the exclusive > use of the intended addressee and may contain confidential > and/or privileged material. Any review, re-transmission, > dissemination or other use of it, or the taking of any action > in reliance upon this information by persons and/or entities > other than the intended recipient is prohibited. If you > received this in error, please inform the sender and/or > addressee immediately and delete the material. > > E-mails may not be secure, may contain computer viruses and > may be corrupted in transmission. Please carefully check this > e-mail (and any attachment) accordingly. No warranties are > given and no liability is accepted for any loss or damage > caused by such matters. > --------------------------------------------------------------- > > ### This e-mail message has been scanned for Viruses by Bytecraft ### > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >