Re: Accessing the battery-backed clock via userland?

["James K. Lowden" <jklowden%schemamania.org@localhost>]

Ignatios Souvatzis wrote:
> On Thu, Jan 22, 2009 at 01:20:45AM -0500, James K. Lowden wrote:
> > Marc Tooley wrote:
> ...
> > > ntpd refuses to correct my time because there are so many seconds
> > > lost  it errs on the side of caution and simply does nothing
> > > instead.
> > 
> > I have a Soekris box that behaved like that until I built a kernel
> > with the magic config options. 
> 
> Which ones?

TIMER_FREQ, so it seems. Below is a patch for GENERIC.  

--jkl

$ diff -u  GENERIC Cherry      
--- GENERIC     2006-07-31 08:35:22.000000000 -0400
+++ Cherry      2006-11-12 17:31:41.000000000 -0500
@@ -22,6 +22,32 @@
 
 options        INCLUDE_CONFIG_FILE     # embed config file in kernel
binary
 
+##  Date: Sun, 12 Nov 2006 14:23:10 -0500
+##  From: Ken Hornstein <kenh%cmf.nrl.navy.mil@localhost>
+##  X-Spam-Score: () hits=0 User Authenticated
+##  X-Virus-Scanned: NAI Completed
+##  X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com /
mimedefang)
+##  Sender: netbsd-help-owner%NetBSD.org@localhost
+##  Precedence: list
+##  X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.92.8
+##  
+##  >> The soekris's timer is running at a different clock than usual.
Make
+##  >> sure you have
+##  >> # AMD Elan SC520's timer runs at a different frequency
+##  >> options         TIMER_FREQ=1189200
+##  >
+##  >but I don't see such an option in 3.1.  
+##  
+##  That option is still available, and still fixes the problem.  Just
+##  add that line into your kernel config and rebuild your kernel.  I
+##  believe that this option is not properly dependency-tracked, so you
+##  should do a "make clean" before rebuilding the kernel.
+##  
+##  --Ken
+#
+# AMD Elan SC520's timer runs at a different frequency
+options        TIMER_FREQ=1189200
+
 #ident                 "GENERIC-$Revision: 1.661.2.14 $"