On 8/20/2011 17:36, Dave Hart wrote:
On Sun, Aug 21, 2011 at 00:12, A C<[email protected]> wrote:
No luck there either. It still refuses to connect to the kernel PPS code
and I still get a message that says "kern PPS no signal".
Try ensuring all ntpd logging is enabled with the following in ntp.conf:
logconfig =sysall +syncall +peerall +clockall
Then check syslog or your configured ntpd logfile for messages
mentioning PPSAPI or time_pps_kcbind.
Good luck,
Dave Hart
Ok, so here's what I've got in the log file after enabling all those
options:
21 Aug 01:03:05 ntpd[6147]: 169.229.70.201 8011 81 mobilize assoc 21538
21 Aug 01:03:05 ntpd[6147]: 108.71.253.20 8011 81 mobilize assoc 21539
21 Aug 01:03:05 ntpd[6147]: GPS_NMEA(1) serial /dev/gps1 open at 4800 bps
21 Aug 01:03:05 ntpd[6147]: GPS_NMEA(1) 8011 81 mobilize assoc 21540
21 Aug 01:03:05 ntpd[6147]: 0.0.0.0 c016 06 restart
21 Aug 01:03:05 ntpd[6147]: 0.0.0.0 c012 02 freq_set kernel -74.006 PPM
21 Aug 01:03:05 ntpd[6147]: 169.229.70.201 8024 84 reachable
21 Aug 01:03:06 ntpd[6147]: 108.71.253.20 8024 84 reachable
21 Aug 01:03:07 ntpd[6147]: GPS_NMEA(1) 8024 84 reachable
21 Aug 01:06:25 ntpd[6147]: 169.229.70.201 963a 8a sys_peer
21 Aug 01:06:26 ntpd[6147]: 0.0.0.0 c615 05 clock_sync
21 Aug 01:06:26 ntpd[6147]: 0.0.0.0 c61d 0d kern PPS enabled
21 Aug 01:06:26 ntpd[6147]: 0.0.0.0 c62d 0d kern PPS no signal
21 Aug 01:14:04 ntpd[6147]: 0.0.0.0 063d 0d kern PPS no signal
21 Aug 01:17:21 ntpd[6147]: 0.0.0.0 064d 0d kern PPS no signal
21 Aug 01:17:43 ntpd[6147]: ntpd exiting on signal 2
The GPS refclock config:
server 127.127.20.1 minpoll 4 mode 1 prefer iburst
fudge 127.127.20.1 time1 0 time2 0.245 flag1 1 flag2 0 flag3 1 refid GPS
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
