From owner-freebsd-questions@FreeBSD.ORG Sat Feb 1 15:42:27 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4D40F08 for ; Sat, 1 Feb 2014 15:42:27 +0000 (UTC) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6A39617B7 for ; Sat, 1 Feb 2014 15:42:27 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.7/8.14.7) with ESMTP id s11FgHqZ005738 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 1 Feb 2014 09:42:17 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <52ED15D9.1090907@tundraware.com> Date: Sat, 01 Feb 2014 09:42:17 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Christian Weisgerber , freebsd-questions@freebsd.org Subject: Re: Invalid time in real time clock References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [75.145.138.73]); Sat, 01 Feb 2014 09:42:17 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s11FgHqZ005738 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 15:42:27 -0000 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/