From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailout2-eri1.midsouth.rr.com ([24.165.200.7]) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 181ZzU-0006fU-00 for ; Tue, 15 Oct 2002 18:16:40 -0400 Received: from cpe-024-033-003-115.midsouth.rr.com (cpe-024-033-003-115.midsouth.rr.com [24.33.3.115]) by mailout2-eri1.midsouth.rr.com (8.11.4/8.11.4) with ESMTP id g9FMGab27788 for ; Tue, 15 Oct 2002 17:16:37 -0500 (CDT) Date: Tue, 15 Oct 2002 17:16:31 -0500 (CDT) From: Adam Myrow To: speakup@braille.uwo.ca Subject: Re: setting the hardware clock In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: If your clock quit setting and you've changed nothing, it's possible the battery may be failing. Assuming you have RTC support in the kernel (most stock kernels do and it's generally a good idea,) type "cat /proc/drivers/rtc." It will give the time that is in the RTC and will show the battery status plus a lot of other info.