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 (4096 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 65DDA1581F3 for ; Tue, 3 Dec 2024 00:34:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2078CE07FA; Tue, 3 Dec 2024 00:34:16 +0000 (UTC) Received: from mail.w14.tutanota.de (mail.w14.tutanota.de [185.205.69.214]) (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 6944DE07C9 for ; Tue, 3 Dec 2024 00:34:15 +0000 (UTC) Received: from tutadb.w10.tutanota.de (w10.api.tuta.com [IPv6:fd:ac::d:10]) by mail.w14.tutanota.de (Postfix) with ESMTP id E1DA341D79F2 for ; Tue, 3 Dec 2024 01:34:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1733186053; s=s1; d=tutanota.com; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=publh2aFaIn0CVjvqFs46P/V6zOuLoNKwuAHZXye2DE=; b=rNbALKa8vFPOefAqVkqMwRYlXzny6gq9qhNUaa79WzsKpF23Rnc3HyGTXv9BHPxi C+DKH6UY4DOWZmarRBbAXtuQK3WMevn5lIvLFt3Ivt7UctWjNp8YVTja4DovHLShg4J jfRnoicP3UJnpJMC9THp8bETxHzukjlAeS4HMRt/+IDCQFWt5NYwb57dnACNdzwcls/ khH6+9ZL7rvpUB03UFA6mxKhdoCC3DDpSf+6wLn6AzkUUOa/C2412Tzd5uU+2dnstxU zrhFA4paFj2aRcT1UCrmHh1sAMnNzh77ceTYt87tL1Uzq+YjHOgVyEI7Mu2JX5wcFYB EVbc3bM9/g== Date: Tue, 3 Dec 2024 01:34:13 +0100 (GMT+01:00) From: mad.scientist.at.large@tutanota.com To: Gentoo User Message-ID: In-Reply-To: <2009247.usQuhbGJ8B@rogueboard> References: <23309301.6Emhk5qWAg@rogueboard> <2105849.bB369e8A3T@rogueboard> <2009247.usQuhbGJ8B@rogueboard> Subject: Re: [gentoo-user] [OT] Very slow POST process 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 2537ca85-82e7-4f11-88f4-f10d7b8d0103 X-Archives-Hash: 2c3427c8f057b83a1b0ab206a98b0bbf usually in laptops which become dirty (they all do, and it's very difficult= to take them apart and clean and reassemble) the hard drive is the first t= hing to fail completely.=C2=A0 A dying hard drive can easily slow/halt boot= .=C2=A0=20 CPU/GPU are likely next along with the power supplies for those chips.=C2= =A0 All you can really do is take it apart, clean it, and if possible test = the hard drive etc. in a known good machine.=C2=A0 Alternately, try a diffe= rent hard drive (either a replacement or a small, cheap used one for testin= g).=C2=A0 Check that all the fans still spin freely after cleaning them, if= possible test them on a power supply (note that some will be 5V and some 1= 2V, be careful to read the labels or start low).=C2=A0=20 The CPU/GPU may or may not have become marginal, same goes for the memory a= nd all the other chips and other temperature sensitive parts.=C2=A0 Really,= it's essential to fix a laptop soon after it starts acting up, those highe= r temperatures age everything rapidly and make all the parts more likely to= fail.=C2=A0 You may or may not be able to get that laptop working again. If you can get it basically working test the hell out of everything with ut= ilities like stress so it doesn't fool you and die hard soon. I hate working on laptops and AIO desktops, always hard to take them apart = and put them back together and they both need regular cleaning, before they= act up (or at least immediately when they start acting up).=C2=A0 Because = of the dust I clean my desktops at least once a year, also a pain but much = easier than a laptop or AIO.=C2=A0 This keeps them from wearing out as quic= kly and as some one on a small fixed income that's very important to me. Depending on your' situation and what your' time is worth replacement might= be the way to go, though you still probably want to recover what you can f= rom the drive. =20 --"Fascism begins the moment a ruling class, fearing the people may use the= ir political democracy to gain economic democracy, begins to destroy politi= cal democracy in order to retain its power of exploitation and special priv= ilege." Tommy Douglas Dec 2, 2024, 09:06 by confabulate@kintzios.com: > On Wednesday 29 November 2023 00:16:11 GMT you wrote: > >> On Tuesday, 28 November 2023 15:49:10 GMT Daniel Frey wrote: >> > On 11/28/23 03:38, Michael wrote: >> > > Over the last 8-9 months I noticed an old Lenovo G505s laptop is >> > > spending >> > > a >> > > long time in the POST process, before eventually the OEM logo shows = up >> > > on >> > > the screen. Last time I timed it, it took 2.5-3.0 minutes. Normall= y it >> > > would only take ~20-30 seconds. Once the logo shows up the boot pro= cess >> > > proceeds without further delay. >> > >=20 >> > > Initially, this delay to POST would happen randomly and rarely. Now= it >> > > happens every time. >> > >=20 >> > > Things I tried: >> > >=20 >> > > 1. Reflashing the UEFI firmware - it didn't work because it already = has >> > > the >> > > latest firmware. >> > >=20 >> > > 2. Removing the main battery and holding down the power button for 1= 5 >> > > seconds, hoping to reset the firmware. >> > >=20 >> > > 3. Leaving the PSU cable connected overnight. >> > >=20 >> > > 4. Testing the RAM and HDD. >> > >=20 >> > > None of the above improved the situation, or indicated what might be >> > > wrong. >> > >=20 >> > > I'll reseat the RAM sticks and the HDD next, in case a contact is >> > > oxidised, >> > > but what else could cause this noticeable delay to POST? A failing = RTC >> > > CMOS battery? >> >=20 >> > We have had a few of these at work and these symptoms were cured by a >> > new CMOS battery. The voltage on the battery has likely dipped to >> > 2.9-3.0 volts; they get unreliable then (i.e. it's dead.) If you leave >> > it long enough you'll start getting RTC errors on POST. >> >=20 >> > I'd try that first, assuming you can still get the CMOS battery for th= ese. >> >=20 >> > Dan >> >> Thanks Dan, will do. I was planning to take it apart soon to replace th= e >> HDD with an SSD, so this would be the first thing to check. I expect >> finding a replacement unit will be difficult. Every Lenovo RTC battery >> seems to have a different part number. >> > > Some things are worth waiting for, others no so much. :-( > > So, this laptop was taking longer and longer and longer to boot, until it= =20 > eventually stopped booting 3-4 months ago: > > When the power button is pressed the cooling fan spins for a second or tw= o,=20 > then it stops. A few minutes later the CPU overheats and eventually it g= oes=20 > into a thermal shutdown. Using an external fan to push air through merel= y=20 > delays this process, but the laptop still does not boot. I am getting a = black=20 > screen and no POST for many minutes until it cuts out. > > I tried to reset the MoBo BIOS by pressing the power button with no batte= ry or=20 > mains connected. I also removed the newly replaced CMOS/RTC battery and= =20 > pressed the power button, but the same failure mode remains after I=20 > reassembled everything. > > Do I have: > > 1. Corrupted MoBo UEFI firmware? > 2. A dying/dead chipset? > 3. Something else? > > Is there anything else I could possibly try? >