Date: Sat, 01 Feb 2014 09:42:17 -0600 From: Tim Daneliuk <tundra@tundraware.com> To: Christian Weisgerber <naddy@mips.inka.de>, freebsd-questions@freebsd.org Subject: Re: Invalid time in real time clock Message-ID: <52ED15D9.1090907@tundraware.com> In-Reply-To: <lcj2jj$2bu$1@lorvorc.mips.inka.de> References: <lcj2jj$2bu$1@lorvorc.mips.inka.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/01/2014 09:07 AM, Christian Weisgerber wrote: > Over the last few months I started noticing that my FreeBSD/amd64 > desktop box would often come up with a date of Jan 1, 2008 after > boot. Presumably the CMOS battery was dying and the motherboard > picked a date from its year of manufacture. > > So I replaced the CR2032 battery on the motherboard and reapplied > the BIOS settings that had been lost during the change. Unfortunately, > I'm still greeted with > > atrtc0: WARNING: Battery failure indication > Invalid time in real time clock. > Check and reset the date immediately! > > Incongruously, the RTC time is actually correct. Well, off by a > minute or so. Clearly the new battery is good. > > I guess this is more a PC question, but how do I get the RTC to > indicate a valid time again? The motherboard manual (Asus) is > rather silent on the whole issue of CMOS battery replacement. > I've seen something similar to this before. A good solution is to use ntpdate at boot to initially set the time properly, and the run ntpd to keep it correct. Both are enabled via /etc/rc.conf. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52ED15D9.1090907>