public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] for the speakup users on the list
Date: Tue, 19 Apr 2022 19:34:38 +0100	[thread overview]
Message-ID: <ba732546-04e9-e07b-41db-42f2041d2500@youngman.org.uk> (raw)
In-Reply-To: <CAK2H+ed_JrSOATtM-kVaW=+oViZDwXoGW_OoA4Y2nurKr+OSrA@mail.gmail.com>

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


      parent reply	other threads:[~2022-04-19 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17 15:13 [gentoo-user] for the speakup users on the list Jude DaShiell
2022-04-17 16:26 ` Mark Knecht
2022-04-17 16:53   ` Jude DaShiell
2022-04-17 17:07     ` Jack
2022-04-17 17:41       ` Jude DaShiell
2022-04-17 17:58         ` Mark Knecht
2022-04-17 17:28     ` Mark Knecht
2022-04-17 18:56       ` John Covici
2022-04-17 21:03         ` Mark Knecht
2022-04-19 18:34       ` Wols Lists [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ba732546-04e9-e07b-41db-42f2041d2500@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox