From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 30 17:25:33 2005 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F30B16A423 for ; Wed, 30 Nov 2005 17:25:33 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from sdcexchange01.amcc.com (gatekeeper-out.amcc.com [198.137.200.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B0AE43D73 for ; Wed, 30 Nov 2005 17:25:25 +0000 (GMT) (envelope-from vkashyap@amcc.com) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Importance: normal Priority: normal Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 30 Nov 2005 09:25:19 -0800 Message-ID: <2B3B2AA816369A4E87D7BE63EC9D2F2601021D20@SDCEXCHANGE01.ad.amcc.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: More about the 9500S-4 issues with the MoBo and FreeBSD... thread-index: AcX1i6XgPOJRKOpkRz6pImB6+0wHrQARw4pQ From: "Vinod Kashyap" To: "Olaf Greve" Cc: amd64@freebsd.org Subject: RE: More about the 9500S-4 issues with the MoBo and FreeBSD... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2005 17:25:33 -0000 > -----Original Message----- > From: Olaf Greve [mailto:o.greve@axis.nl]=20 > Sent: Wednesday, November 30, 2005 12:56 AM > To: Vinod Kashyap > Cc: Nathan Vidican; ray@redshift.com; amd64@freebsd.org > Subject: Re: More about the 9500S-4 issues with the MoBo and=20 > FreeBSD... >=20 > Hi, >=20 > > Are you sure you have the installation CD for amd64? The error=20 > > messages make me think you might be using an i386 version of the CD. >=20 > ???? > Well, I D/L-ed it from the French (I think) FreeBSD mirror from the > AMD64 directory... Having said that, I did notice the CDs=20 > bootstrap loader mentions freebsd/i386 (I meant to ask about=20 > that one). >=20 > If indeed I somehow was totally numb (a thing which I cannot=20 > entirely exclude given some of the following I'm about to=20 > type) and made such a stupid mistake myself, then that could=20 > certainly explain a lot.=20 > However.... that still wouldn't explain why FreeBSD=20 > 5.4-release AMD64 also chokes on it; and on that CD I am 100%=20 > positive it's the AMD64 version, as I have installed it on my=20 > own AMD64 machine from the very same CDs. Also, really, I am=20 > about 99% (if not 100%) sure that I made very certain to D/L=20 > the AMD64 version. The ISO images also reflected that name (I=20 > think), so it's not very likely it's the i386 version. >=20 I am sorry about the question, but the error messages looked like ones that could get printed if the driver was running in a 64-bit environment, but thought it was running in a 32-bit environment. Anyways, please know that you can always contact 3ware support for help. > Then: I'm amased. Really I am. >=20 > As the client needs this machine to be up an running this=20 > Friday, yesterday evening I decided to opt for a different=20 > strategy: install this machine using the on-board RAID=20 > controller, then in the meantime ask the client to order an=20 > Opteron (or dual Opteron) with a Tyan MoBo, install, tune and=20 > test that one at ease and then when it's all set-up swap that=20 > with the machine I'm currently working on. >=20 > So, just when I thought I had a workable strategy again, look=20 > at what horrors were bestowed upon me next: the Sil 3114=20 > on-board RAID controller recognises the drives, enters the=20 > BIOS, but when confirming the total RAID array size it=20 > totally hangs! And that's the controller's BIOS; it didn't=20 > even get to the point where one could install FreeBSD (or=20 > anything else for that matter). So, with "Plan B" out, there=20 > was even a "Plan C": use the nVidia on-board RAID controller.=20 > O.k., I plugged over the SATA controllers, configured the=20 > MoBo's BIOS to do this, and what do ya guess? Indeed, another=20 > full blown controller hang.=20 > Nice. :( >=20 > Well, over the past 15 years I must have installed dozens of=20 > machines (several of them including Asus boards, in=20 > combination with Adaptec SCSI RAID controllers and various=20 > different versions and flavours (i.e.=20 > 1386/amd64) of FreeBSD), with OS-es ranging from MS-DOS,=20 > through the full array of W*nd*wses, FreeBSDs, Linuxes, and I=20 > can hardly recall any more troublesome installation process=20 > than this time; really, it reminds me of the good 'ole MS-DOS=20 > days where one had to jumper each and every ISA board and=20 > then tweak memory configurations in order to get the lot=20 > going. :(((((( >=20 > Actually, I think something is simply b*ll*xed up on the=20 > board, but I just can't put my finger on what it is. Surele=20 > even if it is primarily a gaming board, still these type of=20 > errors should not have occurred. I spent the better part of=20 > late last evening and the wee hours on reading the MoBo's=20 > docs, and checking if we perhaps missed something. >=20 > I didn't spot anything, but something MUST be off... :(((( >=20 > Dunno. Time for a "plan D" I guess; I'll ask if the client=20 > can somehow get a working machine, and then I'll pull two=20 > more late nighters to at least get the bit I was supposed to=20 > do done: installing and tuning FreeBSD and MySQL. At present=20 > it's highly frustrating that I can't even really reach the OS=20 > installation part...:(((( >=20 > OK, guys thanks for hanging in there with me. I'm sure some=20 > day in the future I can laugh out loud at it too, just not=20 > right now....;) >=20 > Cheers! > Olafo > -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, = is for the sole use of the intended recipient(s) and contains = information that is confidential and proprietary to Applied Micro = Circuits Corporation or its subsidiaries. It is to be used solely for = the purpose of furthering the parties' business relationship. All = unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply = e-mail and destroy all copies of the original message.