From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id A332E15808D for ; Tue, 19 Apr 2022 18:34:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D3E00E093E; Tue, 19 Apr 2022 18:34:41 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AB5E9E092C for ; Tue, 19 Apr 2022 18:34:40 +0000 (UTC) Received: from host86-155-180-61.range86-155.btcentralplus.com ([86.155.180.61] helo=[192.168.1.218]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1ngsgQ-000CIf-8m for gentoo-user@lists.gentoo.org; Tue, 19 Apr 2022 19:34:38 +0100 Message-ID: Date: Tue, 19 Apr 2022 19:34:38 +0100 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [gentoo-user] for the speakup users on the list Content-Language: en-GB To: gentoo-user@lists.gentoo.org References: <8795e2b5-aaf4-c17f-6e32-74977bba8ca9@panix.com> From: Wols Lists In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 7c127592-2041-44cd-9bf0-b7516b413edc X-Archives-Hash: 3f885f3632836bbb48155c4fa3888c9a On 17/04/2022 18:28, Mark Knecht wrote: > Echoing Jack's comment, I'm not sure this is a heat > sink problem. Misoperation at the time of letting > go of the reset button prior to POST. If the machine is > starting cold a processor wouldn't overheat that fast but > I haven't yet read all of your thread. > > I think there's also an opportunity here to do some sort > of remote debug with you if we can find anything that does > boot. On quite a few occasions I've had machines that won't boot. Memory is notorious for causing a black screen on boot, no beeps, no nothing. My first PC (Cyrix 686) eventually cured itself after I'd reseated the memory 3 or 4 times. This machine, I nicked its 2x8GB for another machine and replaced it with 2x16GB - that took several reseats before it eventually worked. I'm sure I've had others ... Okay, if Jude is blind he wouldn't see if the problem is "nothing happening", but on any machine that won't do anything that is the first suspect... The other thing is, if the mobo and processor aren't bought as a "matched pair" you could get hit like I did with the first incarnation of this machine - the mobo and cpu were allegedly compatible, but the bios wasn't - I had to RMA the mobo, they upgraded the bios, and then everything allegedly was hunky dory. I still haven't rebuilt that mobo though ... Cheers, Wol