From owner-freebsd-questions@FreeBSD.ORG Wed Apr 18 12:07:20 2007 Return-Path: X-Original-To: freebsd-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 3E50316A404 for ; Wed, 18 Apr 2007 12:07:20 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from bcmelmx.bytecraft.au.com (bcmelmx.bytecraft.au.com [203.39.118.2]) by mx1.freebsd.org (Postfix) with ESMTP id A991413C4B0 for ; Wed, 18 Apr 2007 12:07:19 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from svmarshal2.bytecraft.internal (svmarshal2.bytecraft.internal [10.0.0.3]) by bcmelmx.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id l3IC7CQr056127; Wed, 18 Apr 2007 22:07:17 +1000 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal2.bytecraft.internal with MailMarshal (v6, 1, 4, 441) id ; Wed, 18 Apr 2007 22:07:11 +1000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Wed, 18 Apr 2007 22:07:09 +1000 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F12DF177@svmailmel.bytecraft.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IBM / FreeBSD Install problem Thread-Index: AceBshdAJ5gcowuvSWOf/9WwwAfQWw== From: "Murray Taylor" To: "FreeBSD Mailing List" Cc: general@vicfug.au.freebsd.org Subject: IBM / FreeBSD Install problem 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, 18 Apr 2007 12:07:20 -0000 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. 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=20 --------------------------------------------------------------- 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.=20 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 ###