From owner-freebsd-questions@FreeBSD.ORG Tue Mar 23 21:38:50 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B7511065678 for ; Tue, 23 Mar 2010 21:38:50 +0000 (UTC) (envelope-from ruinermailchucker@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id 25D7E8FC14 for ; Tue, 23 Mar 2010 21:38:49 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 5so1501530qwi.7 for ; Tue, 23 Mar 2010 14:38:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:subject:from :reply-to:to:cc:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=1kcl+IxFRGpHekRLLnXYBX3mxsaTZ6O2y3kHNNIOf9k=; b=HddBEHZTw3Po30zoKeqMCbjx+ls1c1F+L9XkVGU8mnSggujgQMfMSBCuIqh2Ec2gzi B4xu+mwXfPcGeaIsVi1QoQtEOl4AfhNw+yh/RbM/yt1FHBLvDy5j6raebHgEfDst8Acv qbBY5tLqRzqztnNmGPu7qWeIArNkBqSZHUMfw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; b=qEz+zkEhN2jCV3wsAd+qCVLVCz0fP+DDYu7nWctYBqhiafmdjkc2Ot9h5GDv/pHkrc 5kuPocezuNcysE1SNMeJ+uXMXsyupay4g+MJkk9cz0TucyoWr/EiFTpPzov3T9nz/g4Y pfsp2rMdfxSTp6AP29c4y4w0Gi7vbPE4C0ByQ= Received: by 10.229.104.195 with SMTP id q3mr7132832qco.56.1269380329147; Tue, 23 Mar 2010 14:38:49 -0700 (PDT) Received: from ruiner.mine.nu (173-16-22-10.client.mchsi.com [173.16.22.10]) by mx.google.com with ESMTPS id 20sm4484902iwn.9.2010.03.23.14.38.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 23 Mar 2010 14:38:46 -0700 (PDT) Received: from [192.168.0.250] (revenant [192.168.0.250]) by ruiner.mine.nu (Postfix) with ESMTP id 29B714DA042; Tue, 23 Mar 2010 16:38:45 -0500 (CDT) From: Corey John Bukolt To: Tim Judd In-Reply-To: References: <20100321101137.GA8202@melon.esperance-linux.co.uk> <4BA601B6.1050807@onetel.com> <1269327949.3708.75.camel@redwood.bukolt.lan> Content-Type: text/plain; charset="us-ascii" Date: Tue, 23 Mar 2010 16:39:09 -0500 Message-ID: <1269380349.48845.41.camel@ignis.bukolt.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-questions Subject: Re: Also have a dead box [ WAS: Re: OT: dead box ] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: 4096@gmx.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2010 21:38:50 -0000 On Tue, 2010-03-23 at 06:57 -0600, Tim Judd wrote: > On 3/23/10, Corey John Bukolt wrote: > > On Sun, 21 Mar 2010 11:23:34 +0000 (06:23 CDT) Chris Whitehouse wrote: > >> When you press the power button does the cpu fan or the power supply fan > >> spin for a moment then stop? That's a sign that something on or plugged > >> in to the motherboard has blown. Unplug things and test again. > >> > >> Chris > > > > Just a few days ago, I was helping a friend build a system (with all > > brand new components, I might add) and we had this very problem. After > > sticking in the CPU and RAM and hooking up and turning on the PSU, the > > green LED on the motherboard turns on. However, the second the power > > button is pressed, everything flashes for a second, then turns back off. > > The green LED on the motherboard also remains on. The only way to get > > it to flash again is to turn off the PSU, wait, then turn it back on. > > We tried re-seating everything, to no avail. > > > > Reading this thread, someone else mentioned beep codes and that if there > > were none, it's most likely a fried motherboard. > > > > Can anyone else confirm this? > > > > ~Corey > > > Best way to confirm a dead board in any case is those POST diagnosis > cards. They have a dual-digit LED output that changes depending on > the signal on the wire. If at any time those dual-digit LEDs stay > permanently on anything OTHER THAN 00 is a failed POST. If it fails > before it gets a shot at testing RAM or anything, there may be no beep > codes. > > > Always good to have one in a toolkit. So that's what those damn things were for......I have three rack mounted servers sitting in my basement and they each have an on board dual digit readout. I figured they had something to do with the BIOS, but I was just too lazy to find out. ;) Learn something new everyday. Thanks for the advice, I'm going shopping for one right now.