From: jlaiho@ichaos.nullnet.fi (Juha Laiho) Subject: Re: Problems with CMOS after using Linux on my 486 Date: Sat, 14 Nov 1992 17:08:01 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:
>>>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
>[...]
>
>Anyway, on my system, CAD/reboot works only about 30% of the time.
>It hangs the machine the other 70%. On a couple of friends' systems,
>it wipes the CMOS. Now they shut down linux by just doing a couple of
>syncs turning off the power.
>
>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.
>
I have a similar problem with 386sx/16, Phoenix BIOS.
From time to time, rebooting gives me the message 'CMOS checksum failure'.
No CMOS info seems to be trashed, though.
..Wolf