From: The Wyvern (wyvern@hal.gnu.ai.mit.edu)
Date: 11/17/92


From: wyvern@hal.gnu.ai.mit.edu (The Wyvern)
Subject: Re: Problems with CMOS after using Linux on my 486
Date: Tue, 17 Nov 1992 20:18:47 GMT

In article <1992Nov12.230055.28527@sfu.ca> rchen@fraser.sfu.ca (Robert Chen) writes:
>In article <BxIyzz.38z@undergrad.math.waterloo.edu> pcrichar@undergrad.math.waterloo.edu (Pat Richard) writes:
>>In article <96973@netnews.upenn.edu> dsimon@stipple.seas.upenn.edu (Derron Simon) writes:
>>>Hi. I recently purchased a 486DX33 and want to run Linux on a 50 meg parition.
>>>My problem is that after loading Linux from the latest SLS disks (.98pl1, I
>>>ftp'ed them 3 days ago) I get "CMOS checksum bad" errors after every reboot.
>>>Usually the portion of CMOS that gets trashed is the Hard Drive information!
>>
>>Yes, I have also had this problem running SLS .98 pl1, though I somehow
>>feel it wasn't to do with SLS (?). When I used mtools, and then re-booted,
>>the hard disk info was lost. It was my first time using mtools, and
>[...]
>>Pat C. Richard,
>>pcrichar@cayley.uwaterloo.ca
>
>
[...]
>I am told that this behavior happens only with AMI bios. Don't know
>why. Is there any chance there will ever be a fix for this? Linux
>has had this 'bug' (if you can call it that) since the CAD code was
>introduced.
>
>
>Can anyone out there who knows anything about this comment?
>

My system uses Phoenix BIOS and has the same problem.
Reboot just hangs the machine, so I just sync, halt,
and hit reset. It'd sure be nice to have a working
reboot, though.

>- Ken
>