[NTLUG:Discuss] Fw: Re: !@#$%^ hardware
LEROY TENNISON
leroy_tennison at prodigy.net
Wed Jan 27 23:38:28 CST 2010
(Top posting because "that's the way it is" using Web mail which is what I'm doing until I fully recover).
I had never seen a CMOS battery produce this kind of behavior before but initial indications are that the battery was indeed the problem. Fortunately I had just replaced the battery on the machine where I suspect the motherboard and the that battery was the same as used on this motherboard. Decided to swap batteries and the problem hasn't reappeared (yet, only a few boots since the change).
Thanks for the reply, I appreciate it.
--- On Tue, 1/26/10, Robert Pearson <e2eiod at gmail.com> wrote:
From: Robert Pearson <e2eiod at gmail.com>
Subject: Re: [NTLUG:Discuss] !@#$%^ hardware
To: "NTLUG Discussion List" <discuss at ntlug.org>
Date: Tuesday, January 26, 2010, 11:11 PM
On Tue, Jan 26, 2010 at 10:53 PM, LEROY TENNISON
<leroy_tennison at prodigy.net> wrote:
> As if hard drive woes weren't enough, now a different computer (the one I moved to in order to isolate my hard drive problems ...) is having CPU speed problems (improperly set) and won't even boot. Any ideas? I'm glad I have three PCs because I'm sending this via Web mail booted to a Debian Live CD and storing data on USB sticks - this is getting old fast...
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
>
This is just a WAG (Wild Ass Guess) based on my experience but here it is:
Two of my computers have lost the correct CPU parameters at boot time
when the "keep-alive" battery on the mobo was failing. By manually
resetting the values in the BIOS at boot time they would boot but fail
on any following restart or boot. Replacing the batteries and
resetting the parameters to the correct values solved the problem
permanently.
HTH, YMMV
_______________________________________________
http://www.ntlug.org/mailman/listinfo/discuss
More information about the Discuss
mailing list