[ntp:questions] NMEA / Garmin Etrex ntpd time sync not working

none none at none1.invalid
Sat Oct 28 05:36:22 UTC 2006


Hi,

I have a question as to why I cant get may garmin extrex to act as a time
source for ntpd in NMEA mode...

I have down loaded the latest ntpd code and compiled it. I set up the ntp.conf
per the nmea driver example. I see nmea gps strings in ntpd but it does not
use this as a time source still. I'm guessing it is something obvious but
I can't figure it out.

thanks for any help or pointers to get me going here...

thankyou

Matt

Here are all the logs and file outputs I have....


ntp.conf :

server 127.127.20.0 prefer

-------

ntpd debug output :

ntpd 4.2.2p4 at 1.1585-o Fri Oct 27 17:34:22 UTC 2006 (1)
addto_syslog: signal_no_reset: signal 13 had flags 4000000
addto_syslog: precision = 1.000 usec
create_sockets(123)
addto_syslog: no IPv6 interfaces found
addto_syslog: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
bind() fd 16, family 2, port 123, addr 0.0.0.0, flags=9
Added addr 0.0.0.0 to list of addresses
addto_syslog: Listening on interface wildcard, 0.0.0.0#123 Disabled
bind() fd 17, family 2, port 123, addr 127.0.0.1, flags=21
Added addr 127.0.0.1 to list of addresses
addto_syslog: Listening on interface lo, 127.0.0.1#123 Enabled
bind() fd 18, family 2, port 123, addr 10.0.16.25, flags=24
Added addr 10.0.16.25 to list of addresses
addto_syslog: Listening on interface eth0:1, 10.0.16.25#123 Enabled
init_io: maxactivefd 18
local_clock: time 0 base 0.000000 offset 0.000000 freq 0.000 state 0
key_expire: at 0
peer_clear: at 0 next 1 assoc ID 13271 refid INIT
refclock_setup fd 5 modem status: 0x4006
refclock_ioctl: fd 5 flags 0x1
newpeer: 127.0.0.1->127.127.20.0 mode 3 vers 4 poll 4 4 flags 0x10a1 0x1 ttl 1 key 00000000
addto_syslog: frequency initialized 0.000 PPM from /var/lib/ntp/drift
local_clock: time 0 base 0.000000 offset 0.000000 freq 0.000 state 1
report_event: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010)
refclock_transmit: at 1 127.127.20.0
auth_agekeys: at 1 keys 1 expired 0
timer: refresh ts 0
nmea: timecode 68 $GPRMC,051134,A,4727.1418,N,12209.8054,W,0.0,29.5,281006,18.1,E,A*0B
peer GPS_NMEA(0) event 'event_peer_clock' (0x85) status 'unreach, conf, 1 event, event_peer_clock' (0x8015)
nmea: timecode 68 $GPRMC,051136,A,4727.1418,N,12209.8054,W,0.0,29.5,281006,18.1,E,A*09
nmea: timecode 68 $GPRMC,051138,A,4727.1416,N,12209.8053,W,0.0,29.5,281006,18.1,E,A*0E
nmea: timecode 68 $GPRMC,051138,A,4727.1416,N,12209.8053,W,0.0,29.5,281006,18.1,E,A*0E
nmea: timecode 68 $GPRMC,051140,A,4727.1415,N,12209.8053,W,0.0,29.5,281006,18.1,E,A*02
nmea: timecode 68 $GPRMC,051142,A,4727.1415,N,12209.8052,W,0.0,29.5,281006,18.1,E,A*01
nmea: timecode 68 $GPRMC,051144,A,4727.1414,N,12209.8051,W,0.0,29.5,281006,18.1,E,A*05
nmea: timecode 68 $GPRMC,051146,A,4727.1413,N,12209.8051,W,0.0,29.5,281006,18.1,E,A*00
nmea: timecode 68 $GPRMC,051148,A,4727.1412,N,12209.8051,W,0.0,29.5,281006,18.1,E,A*0F
refclock_transmit: at 17 127.127.20.0
nmea: timecode 68 $GPRMC,051150,A,4727.1410,N,12209.8053,W,0.0,29.5,281006,18.1,E,A*06
nmea: timecode 68 $GPRMC,051152,A,4727.1411,N,12209.8053,W,0.0,29.5,281006,18.1,E,A*05
nmea: timecode 68 $GPRMC,051154,A,4727.1411,N,12209.8053,W,0.0,29.5,281006,18.1,E,A*03

/var/log/messages

Oct 28 05:13:53 localhost ntpd[28027]: ntpd 4.2.2p4 at 1.1585-o Fri Oct 27 17:34:22 UTC 2006 (1)
Oct 28 05:13:53 localhost ntpd[28027]: precision = 1.000 usec
Oct 28 05:13:53 localhost ntpd[28027]: no IPv6 interfaces found
Oct 28 05:13:53 localhost ntpd[28027]: Listening on interface wildcard, 0.0.0.0#123 Disabled
Oct 28 05:13:53 localhost ntpd[28027]: Listening on interface lo, 127.0.0.1#123 Enabled
Oct 28 05:13:53 localhost ntpd[28027]: Listening on interface eth0:1, 10.0.16.25#123 Enabled
Oct 28 05:13:53 localhost ntpd[28027]: kernel time sync status 0040
Oct 28 05:13:53 localhost ntpd[28027]: frequency initialized 0.000 PPM from /var/lib/ntp/drift

 root]# ntpq -pcrv
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 GPS_NMEA(0)     .GPS.            1 l    -   16    0    0.000    0.000   0.001
assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
version="ntpd 4.2.2p4 at 1.1585-o Fri Oct 27 17:34:22 UTC 2006 (1)",
processor="i686", system="Linux/2.4.21-27.EL", leap=11, stratum=16,
precision=-20, rootdelay=0.000, rootdispersion=0.975, peer=0,
refid=INIT, reftime=00000000.00000000  Wed, Feb  6 2036 22:28:16.000,
poll=6, clock=c8edc843.22d4ffc1  Sat, Oct 28 2006  5:14:59.136, state=1,
offset=0.000, frequency=0.000, jitter=0.001, noise=0.001,
stability=0.000, tai=0


# ntpdate -b -u -q localhost
server 127.0.0.1, stratum 16, offset 0.000003, delay 0.02563
28 Oct 05:15:12 ntpdate[28032]: no server suitable for synchronization found




More information about the questions mailing list