From owner-freebsd-questions Thu Apr 4 11:33:24 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA22940 for questions-outgoing; Thu, 4 Apr 1996 11:33:24 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA22932 for ; Thu, 4 Apr 1996 11:33:20 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA22274; Thu, 4 Apr 1996 12:28:15 -0700 From: Terry Lambert Message-Id: <199604041928.MAA22274@phaeton.artisoft.com> Subject: Re: cmos clock problem To: zgabor@CoDe.hu (Gabor Zahemszky) Date: Thu, 4 Apr 1996 12:28:15 -0700 (MST) Cc: freebsd-questions@freebsd.org In-Reply-To: <199604041427.OAA03052@CoDe.CoDe.hu> from "Gabor Zahemszky" at Apr 4, 96 02:27:47 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've got a 486-120, with Award BIOS. Once, I found that the date is wrong, > so I went into the BIOS Setup and corrected it. From that time, I have the > next problems: > on every boot, the BIOS says, sometyhing is wrong, "Press to continue > or to go Setup" > -- a) Setup: The time and date are set to the last date setting, and the clock > doesn't go. Set it, reboot, the same problem, but the time/date is a bit more > preciuos (;-) > -- b) Continue: FB (2.1R from Walnut Creek) screaming, that there is a problem > in the CMOS's time settings, go and correct it. I can ``date yymmdd..'' > and I can see the date changes (under Unix), but not in the BIOS. Next time, > the same problem. > > What's that, and what can I do to correct it? (I have no money for a new > machine, so don't tell buy another ...) Don't change the CMOS clock using the BSD kernel; it won't set the BIOS-specific CMOS checksum information, and you will get your boot warning. Look at the clock related man pages. I believe you can touch a file in /etc to fix this, but I can't remember which one. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.