I've commented out the runcmd line, then even commented every part of the clock code. No luck.
Did 8.1 do this as well? 8.1 reboots just fine, no CMOS errors. Joe ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 26, 2002 4:03 PM Subject: Re: [expert] Mandrake 8.2/9.0 bad cmos checksum error > On Thu, 26 Sep 2002, Joseph Stegner wrote: > > > Here's the problem I had with 8.2, for those who don't remember: > > > > For some reason, whenever I reboot from 8.2 (not the betas/RC's, the > > 8.2 release version) or 8.2's installer after my mouse initializes and > > the BIOS tries to initialize communication with the hard drives, it will > > hang - the busy led tells me something is going on, but nothing happens. > > After waiting for a minute or so, I'll get either "Bad CMOS checksum, > > default used" or "Error System Clock" or something of that nature. > > Sometimes it'll reset all the changes I made in BIOS. With Win2k and > > Mandrake 8.1, nothing of that sort happens. > > It seems there should only be a couple places where Linux would interact > with the PC BIOS that could possibly cause a problem: > > 1) /dev/nvram is enabled and something is doing something weird. But > this would be highly unlikely. > > 2) /etc/rc.d/init.d/halt (called during shutdown) is causing a problem > when it syncs the hardware clock. If this is the case you can try > disabling the sync by commenting out the line and then doing a test > reboot. > > > > > ---------------------------------------------------------------------------- ---- > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
