From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 40F95138010 for ; Wed, 29 Aug 2012 11:11:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0D87FE0521; Wed, 29 Aug 2012 11:10:50 +0000 (UTC) Received: from mx.virtyou.com (mx.virtyou.com [178.33.32.244]) by pigeon.gentoo.org (Postfix) with ESMTP id 2405DE0458 for ; Wed, 29 Aug 2012 11:09:03 +0000 (UTC) Received: from [127.0.0.1] (p578b7bed.dip0.t-ipconnect.de [87.139.123.237]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx.virtyou.com (Postfix) with ESMTPSA id B52CEDC04A for ; Wed, 29 Aug 2012 13:09:02 +0200 (CEST) Message-ID: <503DF84D.20700@wonkology.org> Date: Wed, 29 Aug 2012 13:09:01 +0200 From: Alex Schuster Organization: Wonkology User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] My PC died. What should I try? References: <502DF7D0.8010200@wonkology.org> <502E9E84.4060500@wonkology.org> <503D30C7.1000209@wonkology.org> <201208290115.30740.peter@humphrey.ukfsn.org> <20120829022900.0e6d7be7@khamul.example.com> <503D6AB7.7080208@gmail.com> In-Reply-To: <503D6AB7.7080208@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: f58dcfaa-b563-4738-8ffa-a7b053740a92 X-Archives-Hash: f528be6c68f2001a9d974479c88dbbab Dale writes: > Alan McKinnon wrote: >> Rule #1 in dealing with odd weird strange computer faults is ALWAYS >> test with another PSU of at least twice the capacity you think you need. > > +1 I always start with the P/S. Well, unless I see something else > unrelated letting the smoke out. Even then tho, a bad P/S can cause the > smoke to get out of something else too. It's good advice all the way > around. > > Why not let the computer shop test the P/S? If it blows up something of > theirs, it's bad. ;-) I would have preferred to give them the whole PC, but I cannot carry that around easily when going to work by bus and tram, so I could drop it of the store when I leave work in the evening. It was easier to just carry mainboard and CPU in a small bag. Well, not really true, I gave them the hardware on Friday, and on Saturday I could have used the car to transport the PC, but I was somewhat busy that day, and just didn't think about the PSU frying the board. And I had hoped that they would test the board right when I was there on Friday, so I could leave with the new one. Or with the new CPU, if that had turned out to be defective. Wonko