[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: severely bad timekeeping
> On looking at my machine, I find, in printenv output,
> boot-command " /PowerPC,60?" select-dev B1BD50 encode-int "
> timebase-frequency" property 5000 ms catch 500 ms boot boot
> which it occurs to me actually might not be getting used,
It appears it's not getting used.
But it proved easy to fix, or at least work around.
setenv nvramrc " /PowerPC,60?" select-dev B1C2A2 encode-int "
setenv use-nvramrc? true
and the no-NTP timekeeping error went from the initial half-second per
minute to about 1.1 millisecond per minute. NTP is now quite willing
to sync up, and presumably will discpline the clock nicely. I suspect
I'd have got even closer by using B1C1C0 or so, but I'm content with a
clock ntp can easily discipline.
The default, it turned out, was B34A70 - 11750000 in decimal. I
determined this by using
and looking for the timebase-frequency line (before setting up the
above nvramrc, or after resetting with use-nvramrc? set false).
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse%rodents-montreal.org@localhost
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Main Index |
Thread Index |