From owner-freebsd-questions@FreeBSD.ORG Wed Jun 14 22:19:57 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A49E816A41A for ; Wed, 14 Jun 2006 22:19:57 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BF1E43D46 for ; Wed, 14 Jun 2006 22:19:55 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.13.6+UW06.06/8.13.6+UW06.03) with ESMTP id k5EMJs4W016929 for ; Wed, 14 Jun 2006 15:19:54 -0700 X-Auth-Received: from [192.168.0.50] (dsl254-013-145.sea1.dsl.speakeasy.net [216.254.13.145]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.6+UW06.06/8.13.6+UW06.03) with ESMTP id k5EMJnRq009503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 14 Jun 2006 15:19:53 -0700 Message-ID: <44908B7D.6000703@u.washington.edu> Date: Wed, 14 Jun 2006 15:19:41 -0700 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.4 (X11/20060608) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <448F9A87.3070809@u.washington.edu> <6.0.0.22.2.20060614103744.0271cf10@mail.computinginnovations.com> <44907122.8000801@u.washington.edu> <6.0.0.22.2.20060614164104.026ac018@mail.computinginnovations.com> <44908B2F.6070103@u.washington.edu> In-Reply-To: <44908B2F.6070103@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_MEDIA_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: Making a L440GX+ work (was "Trying to revive a server... AIC-7896 freezes pre-POST completion") 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, 14 Jun 2006 22:19:57 -0000 Garrett Cooper wrote: > Derek Ragona wrote: >> The halt could be anything from bad RAM, or other IRQ issues. This >> begs the question as to why this board is not in use? >> >> You should be able to update the BIOS from a floppy or cd-rom boot >> disk. You can take your pick at bootdisk.org >> >> The general rule with ram is you can run faster ram than you need, >> just usually wastes money that faster RAM costs. But speed isn't the >> only issue with ram, some are ECC or non-ECC, plus the CAS timing can >> be different. So your RAM while it seems to work,may not be quite right. >> >> -Derek >> >> >> >> At 03:27 PM 6/14/2006, Garrett Cooper wrote: >>> Derek Ragona wrote: >>>> IF you can find the documentation for the motherboard, see if there >>>> is a reset jumper. That jumper should reset the BIOS to factory >>>> defaults to allow it to get through the post and into setup. Some >>>> motherboards actually take you into setup with the jumper moved to >>>> reset bad configurations. >>>> Also, unplug any cards and drives, leave the system board with just >>>> ram and cpu and video (unless it is built in) until you get it >>>> configured. >>>> -Derek >>>> >>>> At 12:11 AM 6/14/2006, Garrett Cooper wrote: >>>>> Hello again all, >>>>> I know this isn't a FreeBSD question really, but I just >>>>> started up a motherboard with onboard SCSI (Adaptec AIC-7896), and >>>>> for some odd reason it freezes pre-POST before it attempts to boot >>>>> and there isn't any way where I can get into the BIOS to change the >>>>> settings it seems. Does anyone know how I can maybe disable the >>>>> onboard SCSI controller since it appears to hang while detecting >>>>> disks? >>>>> Thanks a million! >>>>> -Garrett >>> >>> Thanks all for the help. It turns out after a bit of >>> researching and seeing some numbers on boot, I was able to find the >>> documentation for the motherboard. It's an L440GX+ motherboard which >>> does appear to still work properly, but here's the clincher. I read >>> that the processors I have installed are compatible (2xP3 600E CPUs), >>> _but_ only if the BIOS is updated past a particular version and I >>> don't know if that is true or not. Plus I don't know what is causing >>> the thing to halt because it appears to work on occasion--got the >>> system to boot once but halted it since I couldn't get into the BIOS >>> and change the settings. I cleared the CMOS--both by setting the >>> jumper and removing the battery, and all it appears to have done >>> superficially is make the original splash screen come up during boot. >>> So, my question is has anyone experienced anything like this >>> and if so how did you solve this problem, or does anyone know how to >>> fix this situation apart from (maybe) installing Windows and updating >>> the BIOS with a different processor? >>> Also, I have a horde of PC133 SD RAM and only one stick of >>> PC100 RAM, which doesn't appear to work in the motherboard, and the >>> motherboard is rated to _only_ support PC100 SD RAM. Is it all right >>> for me to use RAM which is rated 33MHz faster than recommended? I >>> think it's possible with some motherboards but I'm not sure about >>> this one. >>> Thanks again for all your help guys :). >>> -Garrett > > Thanks for your concerns. Supposedly when I received it last year in a > trade, this motherboard was a spare that was not used by the owner > because I don't think he had a reason to use the antique hardware. The > thing is that I need a replacement motherboard with working IRQ/PCI > slots because my previous motherboard (Tualatin ECS board) may have been > partially fried thanks to a bad PSU and a series of SCSI hard drives > drawing too much current within the case. Needless to say I fixed the > PSU issue, but the issue with the original motherboard still may linger on. > > I'll see about using a BIOS flash boot disk, but there is a list of > procedures that Intel gives on their website, which seems to involve > Windows a bit more extensively than I originally thought. > > Thanks again about the RAM part. I know that mixing and matching is the > only no-no in RAM-land, but other than that the motherboard says it > supports both flavors--either ECC or non-ECC. > > -Garrett Also, I have nothing plugged in (never did) and was strictly using the onboard components. -Garrett