On 2006-12-17 03:51, ByteEnable wrote: > On Sun, 2006-12-17 at 01:09 -0600, Darryl Gregorash wrote: > >> adjtimex -p >> > mode: 0 > offset: 0 > frequency: 0 > maxerror: 16384000 > esterror: 16384000 > status: 65 > time_constant: 6 > I don't know if this will change anything else, but all I've read says that this value is too high for a free-running system clock. You may try "adjtimex -T 0" followed by "adjtimex -c" again, to see if it brings the system clock within reason. I don't expect it to, but I really don't know very much about the internal workings of the sys clock.
Everything else is quite OK here. > --- current --- -- suggested -- > cmos time system-cmos error_ppm tick freq tick freq > 1166348614 1.782604 > 1166348622 3.565470 178286.6 10000 0 > Just so there is no confusion here, without the "-i" parameter, these measurements are taken every 10 seconds of system time, and the error is calculated accordingly. Thus: error = (3.56547 - 1.782604)/10 = 0.1782866, or 178268.8 ppm >> Also use "adjtimex -h <timeserver>" at least twice, over a period of at >> > > The estimated error in the cmos clock is 0.710913 +- 0.000014 ppm > This is very good, one of the best hardware clocks I've ever seen. However, it does make me wonder if you are running an over-clocked system. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
