On Thu, Jul 5, 2012 at 09:54 UTC, Victor Andres wrote: > Once I'm sure the PPS signals are arriving correctly to system, I start to > configure NTP. > In /etc/ntp.conf, I add the sentencies to use driver 22 ATOM - PPS > server 127.127.22.0 > fudge 127.127.22.0 refid pps > > but I can't to see the peer listing ntpq -p, and if I run NTP -D1 I can see > that it can not reconize it as a valid clock type 22: > ... > 5 Jul 08:27:48 ntpd[1168]: refclock_newpeer: clock type 22 invalid > 5 Jul 08:27:48 ntpd[1168]: 127.127.22.0 interface 127.0.0.1 -> (none) > ... > I've compiled NTP 4.2.6p5 with --enable-ATOM > > What could be the problem? perhaps the pps signal configuration?
config.log will tell you for sure, but my guess would be you are missing the timepps.h header file that provides Linux PPSAPI. Cheers, Dave Hart _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
