Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Mighty Mouse <"squeak!"@thecheesefactory.com> Newsgroups: aus.computers Subject: Re: Why secure boot might be a good idea on your Linux machine Date: Mon, 23 Dec 2024 11:14:28 +1100 Lines: 24 Message-ID: References: <6748e05b@news.ausics.net> <674b78d6@news.ausics.net> <6758b09e@news.ausics.net> <6762262e@news.ausics.net> <67639438@news.ausics.net> <6765e2d6@news.ausics.net> <67673963@news.ausics.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net l0qXcwZZf7SZEJSJEyo2gQ1g9kCZX//vJjOx+upsShm63i99z0 Cancel-Lock: sha1:RfLc6YtO2vMxLGB8UholqM+QgJk= sha256:dpfthNySwjLxSmo2EvjQbK8rTqNCAaWhcMM0B/RWq7Y= User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0 SeaMonkey/2.53.19 In-Reply-To: <67673963@news.ausics.net> Xref: csiph.com aus.computers:71540 Computer Nerd Kev wrote: > Mighty Mouse <"squeak!"@thecheesefactory.com> wrote: >> Mighty Mouse wrote: >>> Computer Nerd Kev wrote: >>>> If you've now tried different RAM sticks and different RAM slots, >>>> swapping back the old CPU would be the next test, and failing that >>>> then the motherboard must be broken. >>> yep. that's the final test. >> success at last! it was the CPU. put the old one back and it's working >> fine. many thanks for your help with this! :) > That's good. It could be that there was just a poor connection on > one of the address signal contacts when you inserted the new CPU > before. >  the CPU has pins that go into holes in the CPU socket, and a lever locks it in place. so I don't see how it would be possible to have it incorrectly inserted. and the heatsink exerts a lot of pressure on it. -- Have a nice day!.. stay sane, be happy, and enjoy living.