Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Dennis Hilberg, Jr. wrote: Phil wrote: Dennis, Have you considered that the unit itself may be defective, Granted it used to work, but that doesn't mean it will last forever. It is a massed produced and rather inexpensive unit, I would think ordering a new unit would be cheaper than the time and labor of stringing wire all over the place. Just a thought, Phil It's certainly possible, maybe it's just gradually dying. If that's the case, it's still under warranty. I was actually going to order another GPS 18 LVC to use on my Linux machine as a refclock, so I suppose I could compare the performance of the two. Maybe I'll do that before I spend a bunch of time stringing wire all over the place, like you suggested. Thanks Phil, Dennis A follow-up: I ended up extending the cable on the GPS 18 LVC by about 50 feet anyway, and now the device sits on the peak of the roof with good exposure. It sees 8 - 10 satellites constantly, and my problem has gone away. Dennis -- Dennis Hilberg, Jr. \ timekeeper(at)dennishilberg(dot)com NTP Server Information: \ http://saturn.dennishilberg.com/ntp.php ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Phil wrote: Dennis, Have you considered that the unit itself may be defective, Granted it used to work, but that doesn't mean it will last forever. It is a massed produced and rather inexpensive unit, I would think ordering a new unit would be cheaper than the time and labor of stringing wire all over the place. Just a thought, Phil It's certainly possible, maybe it's just gradually dying. If that's the case, it's still under warranty. I was actually going to order another GPS 18 LVC to use on my Linux machine as a refclock, so I suppose I could compare the performance of the two. Maybe I'll do that before I spend a bunch of time stringing wire all over the place, like you suggested. Thanks Phil, Dennis -- Dennis Hilberg, Jr. timekeeper(at)dennishilberg(dot)com NTP Server Information: http://saturn.dennishilberg.com/ntp.php ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
The odd thing is, the GPS 18 LVC ran fine for a few weeks with the receiver inside, when it suddenly stopped getting any signal. After that, I mounted it on a bracket about a foot outside the window, where it ran fine for about three months. Now the signal is intermittent, although most of the time it is not synced. If I power-cycle the unit, it syncs for about 5 - 10 minutes, then loses signal. Sometimes it will sync again, sometimes it won't. But it's always intermittent. So it's apparent that it does get signal but it's weak. Dennis Hilberg, Jr. timekeeper(at)dennishilberg(dot)com NTP Server Information: http://saturn.dennishilberg.com/ntp.php Dennis, Have you considered that the unit itself may be defective, Granted it used to work, but that doesn't mean it will last forever. It is a massed produced and rather inexpensive unit, I would think ordering a new unit would be cheaper than the time and labor of stringing wire all over the place. Just a thought, Phil ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Dennis Hilberg, Jr. wrote: [] I knew you weren't joking. However, I need to solve my sudden lack-of-signal issue before I do anything. GPS satellites don't change orbits suddenly do they? Or at all? [] Dennis Dennis, Satellites do fail, and are replaced. Batteries wear out, thruster fuel comes exhausted and so forth. They do not change orbit suddenly, however The Chinese recently did shoot down a satellite of their own in a much lower orbit, creating lots of debris which could affect other low-earth-orbit satellites. GPS satellites orbit higher than this, and are unlikely to be affected. You could use a terminal emulation program (in Windows, FreeBSD or whatever) to see what is coming down the line from the GPS18 LVC. I also have a Windows program which will plot the signal strength received from each of the 12 channels. One possibility may be that the GBS18 has switched to Garmin mode instead of NMEA mode. Cheers, David ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
One possibility may be that the GBS18 has switched to Garmin mode instead of NMEA mode. That seems unlikely. You have to send it a sensible command. Garbage on the line is not likely to do that. On the other hand, maybe he ran some software that knows about Garmin GPS units... My GPS18 occasionally stops working. Usually it recovers by itself in an hour or so. I assume it ran out of satellites and got confused trying to lock up again and eventually did get locked up right. I've also seen it get stuck long enough so that I power cycled it. That fixed it. -- These are my opinions, not necessarily my employer's. I hate spam. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Dennis Hilberg, Jr. wrote: Thanks to everyone who replied to this thread. The server is running successfully. I had no problems recompiling and booting the kernel. If only the Linux kernel recompile process was as easy! The only issue I have is the GPS is loosing satellite sync periodically, whereas it rarely lost sync when it was hooked to the Linux box. Also, initially ntpd would stop using the GPS as the system peer shortly after startup, even though the GPS still had sync. I rebooted the system, thinking perhaps the links weren't created correctly, and that seems to have fixed that issue for now. I see a lot of this behavior in the ntp log: 16 Dec 12:06:21 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 12:06:21 ntpd[814]: kernel time sync status change 2101 16 Dec 12:07:04 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 12:07:04 ntpd[814]: kernel time sync status change 2107 16 Dec 15:30:05 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 15:34:26 ntpd[814]: kernel time sync error 2007 16 Dec 15:43:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 15:43:16 ntpd[814]: kernel time sync status change 2101 16 Dec 15:43:32 ntpd[814]: kernel time sync status change 2107 16 Dec 17:54:38 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 17:57:38 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 18:07:59 ntpd[814]: kernel time sync error 2307 16 Dec 18:08:17 ntpd[814]: kernel time sync status change 2107 16 Dec 21:13:28 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:22:12 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:28:30 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:32:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:33:54 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:36:43 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:44:27 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:51:25 ntpd[814]: synchronized to 64.125.78.85, stratum 1 16 Dec 21:55:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 23:15:18 ntpd[814]: kernel time sync error 2307 16 Dec 23:15:33 ntpd[814]: kernel time sync status change 2107 I don't know what 'kernel time sync error' and 'kernel time sync status change' mean, but I'm assuming that when ntpd switches from the GPS to one of the other internet servers that it's loosing sync. Thoughts? cf. kernel/sys/timex.h /* * Status codes (timex.status) */ #define STA_PLL 0x0001 /* enable PLL updates (rw) */ #define STA_PPSFREQ 0x0002 /* enable PPS freq discipline (rw) */ #define STA_PPSTIME 0x0004 /* enable PPS time discipline (rw) */ #define STA_FLL 0x0008 /* select frequency-lock mode (rw) */ #define STA_INS 0x0010 /* insert leap (rw) */ #define STA_DEL 0x0020 /* delete leap (rw) */ #define STA_UNSYNC 0x0040 /* clock unsynchronized (rw) */ #define STA_FREQHOLD0x0080 /* hold frequency (rw) */ #define STA_PPSSIGNAL 0x0100 /* PPS signal present (ro) */ #define STA_PPSJITTER 0x0200 /* PPS signal jitter exceeded (ro) */ #define STA_PPSWANDER 0x0400 /* PPS signal wander exceeded (ro) */ #define STA_PPSERROR0x0800 /* PPS signal calibration error (ro) */ #define STA_CLOCKERR0x1000 /* clock hardware fault (ro) */ 2107 = STA_PLL | STA_PPSFREQ | STA_PPSTIME | STA_PPSSIGNAL | 0x2000 (Where is 0x2000 defined?) 2307 adds STA_PPSJITTER (PPS signal jitter exceeded). ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
On Mon, 17 Dec 2007 08:41:04 -0800, Dennis Hilberg, Jr. [EMAIL PROTECTED] wrote: Speechless wrote: On Sun, 16 Dec 2007 23:34:48 -0800, Dennis Hilberg, Jr. [EMAIL PROTECTED] wrote: Thanks to everyone who replied to this thread. The server is running successfully. I had no problems recompiling and booting the kernel. If only the Linux kernel recompile process was as easy! The only issue I have is the GPS is loosing satellite sync periodically, whereas it rarely lost sync when it was hooked to the Linux box. Please post the output from command: uname -a apollo$ uname -a FreeBSD apollo.dennishilberg.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Dec 14 22:33:38 PST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC-PPS i386 Errr...I don't think I was joking when I wrote in a previous message in this thread: You may want to use FreeBSD 6.3, scheduled for release in about 10 days or FreeBSD 7.0 scheduled for release sometime mid January 2008. If you are in a hurry, the pre-release versions of both are available for download from the FreeBSD site: http://www.freebsd.org/ Also, initially ntpd would stop using the GPS as the system peer shortly after startup, even though the GPS still had sync. I rebooted the system, thinking perhaps the links weren't created correctly, and that seems to have fixed that issue for now. Please post the contents of: /etc/devfs.conf apollo$ cat /etc/devfs.conf (comments ommitted) own cuad0 root:wheel permcuad0 0660 own cuad0.init root:wheel permcuad0.init 0660 own cuad0.lock root:wheel permcuad0.lock 0660 link cuad0 gps0 The above looks okay. I see a lot of this behavior in the ntp log: 16 Dec 12:06:21 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 12:06:21 ntpd[814]: kernel time sync status change 2101 16 Dec 12:07:04 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 12:07:04 ntpd[814]: kernel time sync status change 2107 16 Dec 15:30:05 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 15:34:26 ntpd[814]: kernel time sync error 2007 16 Dec 15:43:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 15:43:16 ntpd[814]: kernel time sync status change 2101 16 Dec 15:43:32 ntpd[814]: kernel time sync status change 2107 16 Dec 17:54:38 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 17:57:38 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 18:07:59 ntpd[814]: kernel time sync error 2307 16 Dec 18:08:17 ntpd[814]: kernel time sync status change 2107 16 Dec 21:13:28 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:22:12 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:28:30 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:32:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:33:54 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:36:43 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:44:27 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:51:25 ntpd[814]: synchronized to 64.125.78.85, stratum 1 16 Dec 21:55:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 23:15:18 ntpd[814]: kernel time sync error 2307 16 Dec 23:15:33 ntpd[814]: kernel time sync status change 2107 I don't know what 'kernel time sync error' and 'kernel time sync status change' mean, but I'm assuming that when ntpd switches from the GPS to one of the other internet servers that it's loosing sync. Thoughts? Please post the contents of: /etc/ntp.conf apollo$ cat /etc/ntp.conf (comments omitted) restrict 127.0.0.1 server 127.127.20.0 minpoll 4 prefer The statement I used looked something like this: server 127.127.20.0 prefer mode 1 fudge 127.127.20.0 flag3 1 server tick.ucla.eduiburst server nist1-sj.WiTime.net iburst server time.xmission.comiburst server ntp.your.org iburst driftfile /var/lib/ntp.drift logfile /var/log/ntp/ntp.log statsdir /var/log/ntp/ statistics loopstats peerstats sysstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen sysstats file sysstats type day enable filegen clockstats file clockstats type day enable -- Dennis Hilberg, Jr. timekeeper(at)dennishilberg(dot)com NTP Server Information: http://saturn.dennishilberg.com/ntp.php ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Dennis Hilberg, Jr. wrote: If only the Linux kernel recompile process was as easy! I'd be interested in the problems you ran into? my mail addy is valid. uwe ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
On Sun, 16 Dec 2007 23:34:48 -0800, Dennis Hilberg, Jr. [EMAIL PROTECTED] wrote: Thanks to everyone who replied to this thread. The server is running successfully. I had no problems recompiling and booting the kernel. If only the Linux kernel recompile process was as easy! The only issue I have is the GPS is loosing satellite sync periodically, whereas it rarely lost sync when it was hooked to the Linux box. Please post the output from command: uname -a Also, initially ntpd would stop using the GPS as the system peer shortly after startup, even though the GPS still had sync. I rebooted the system, thinking perhaps the links weren't created correctly, and that seems to have fixed that issue for now. Please post the contents of: /etc/devfs.conf I see a lot of this behavior in the ntp log: 16 Dec 12:06:21 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 12:06:21 ntpd[814]: kernel time sync status change 2101 16 Dec 12:07:04 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 12:07:04 ntpd[814]: kernel time sync status change 2107 16 Dec 15:30:05 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 15:34:26 ntpd[814]: kernel time sync error 2007 16 Dec 15:43:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 15:43:16 ntpd[814]: kernel time sync status change 2101 16 Dec 15:43:32 ntpd[814]: kernel time sync status change 2107 16 Dec 17:54:38 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 17:57:38 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 18:07:59 ntpd[814]: kernel time sync error 2307 16 Dec 18:08:17 ntpd[814]: kernel time sync status change 2107 16 Dec 21:13:28 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:22:12 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:28:30 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:32:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:33:54 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:36:43 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:44:27 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:51:25 ntpd[814]: synchronized to 64.125.78.85, stratum 1 16 Dec 21:55:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 23:15:18 ntpd[814]: kernel time sync error 2307 16 Dec 23:15:33 ntpd[814]: kernel time sync status change 2107 I don't know what 'kernel time sync error' and 'kernel time sync status change' mean, but I'm assuming that when ntpd switches from the GPS to one of the other internet servers that it's loosing sync. Thoughts? Please post the contents of: /etc/ntp.conf ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Speechless wrote: On Sun, 16 Dec 2007 23:34:48 -0800, Dennis Hilberg, Jr. [EMAIL PROTECTED] wrote: Thanks to everyone who replied to this thread. The server is running successfully. I had no problems recompiling and booting the kernel. If only the Linux kernel recompile process was as easy! The only issue I have is the GPS is loosing satellite sync periodically, whereas it rarely lost sync when it was hooked to the Linux box. Please post the output from command: uname -a apollo$ uname -a FreeBSD apollo.dennishilberg.com 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Dec 14 22:33:38 PST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC-PPS i386 Also, initially ntpd would stop using the GPS as the system peer shortly after startup, even though the GPS still had sync. I rebooted the system, thinking perhaps the links weren't created correctly, and that seems to have fixed that issue for now. Please post the contents of: /etc/devfs.conf apollo$ cat /etc/devfs.conf (comments ommitted) own cuad0 root:wheel permcuad0 0660 own cuad0.init root:wheel permcuad0.init 0660 own cuad0.lock root:wheel permcuad0.lock 0660 link cuad0 gps0 I see a lot of this behavior in the ntp log: 16 Dec 12:06:21 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 12:06:21 ntpd[814]: kernel time sync status change 2101 16 Dec 12:07:04 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 12:07:04 ntpd[814]: kernel time sync status change 2107 16 Dec 15:30:05 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 15:34:26 ntpd[814]: kernel time sync error 2007 16 Dec 15:43:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 15:43:16 ntpd[814]: kernel time sync status change 2101 16 Dec 15:43:32 ntpd[814]: kernel time sync status change 2107 16 Dec 17:54:38 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 17:57:38 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 18:07:59 ntpd[814]: kernel time sync error 2307 16 Dec 18:08:17 ntpd[814]: kernel time sync status change 2107 16 Dec 21:13:28 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:22:12 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:28:30 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:32:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:33:54 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:36:43 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:44:27 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:51:25 ntpd[814]: synchronized to 64.125.78.85, stratum 1 16 Dec 21:55:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 23:15:18 ntpd[814]: kernel time sync error 2307 16 Dec 23:15:33 ntpd[814]: kernel time sync status change 2107 I don't know what 'kernel time sync error' and 'kernel time sync status change' mean, but I'm assuming that when ntpd switches from the GPS to one of the other internet servers that it's loosing sync. Thoughts? Please post the contents of: /etc/ntp.conf apollo$ cat /etc/ntp.conf (comments omitted) restrict 127.0.0.1 server 127.127.20.0 minpoll 4 prefer fudge 127.127.20.0 flag3 1 server tick.ucla.eduiburst server nist1-sj.WiTime.net iburst server time.xmission.comiburst server ntp.your.org iburst driftfile /var/lib/ntp.drift logfile /var/log/ntp/ntp.log statsdir /var/log/ntp/ statistics loopstats peerstats sysstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen sysstats file sysstats type day enable filegen clockstats file clockstats type day enable -- Dennis Hilberg, Jr. timekeeper(at)dennishilberg(dot)com NTP Server Information: http://saturn.dennishilberg.com/ntp.php ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Thanks to everyone who replied to this thread. The server is running successfully. I had no problems recompiling and booting the kernel. If only the Linux kernel recompile process was as easy! The only issue I have is the GPS is loosing satellite sync periodically, whereas it rarely lost sync when it was hooked to the Linux box. Also, initially ntpd would stop using the GPS as the system peer shortly after startup, even though the GPS still had sync. I rebooted the system, thinking perhaps the links weren't created correctly, and that seems to have fixed that issue for now. I see a lot of this behavior in the ntp log: 16 Dec 12:06:21 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 12:06:21 ntpd[814]: kernel time sync status change 2101 16 Dec 12:07:04 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 12:07:04 ntpd[814]: kernel time sync status change 2107 16 Dec 15:30:05 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 15:34:26 ntpd[814]: kernel time sync error 2007 16 Dec 15:43:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 15:43:16 ntpd[814]: kernel time sync status change 2101 16 Dec 15:43:32 ntpd[814]: kernel time sync status change 2107 16 Dec 17:54:38 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 17:57:38 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 18:07:59 ntpd[814]: kernel time sync error 2307 16 Dec 18:08:17 ntpd[814]: kernel time sync status change 2107 16 Dec 21:13:28 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:22:12 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:28:30 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:32:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:33:54 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:36:43 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 21:44:27 ntpd[814]: synchronized to 164.67.62.194, stratum 1 16 Dec 21:51:25 ntpd[814]: synchronized to 64.125.78.85, stratum 1 16 Dec 21:55:16 ntpd[814]: synchronized to GPS_NMEA(0), stratum 0 16 Dec 23:15:18 ntpd[814]: kernel time sync error 2307 16 Dec 23:15:33 ntpd[814]: kernel time sync status change 2107 I don't know what 'kernel time sync error' and 'kernel time sync status change' mean, but I'm assuming that when ntpd switches from the GPS to one of the other internet servers that it's loosing sync. Thoughts? -- Dennis Hilberg, Jr. timekeeper(at)dennishilberg(dot)com NTP Server Information: http://saturn.dennishilberg.com/ntp.php ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
On Fri, 14 Dec 2007 11:12:00 -0800, Dennis Hilberg, Jr. [EMAIL PROTECTED] wrote: Hello, As the subject line suggests, I would like to set up FreeBSD 6.2 to use my Garmin GPS 18 LVC as a refclock. I've been following advice from David Taylor's web page on this subject http://www.david-taylor.myby.co.uk/ntp/FreeBSD-GPS-PPS.htm , although he used FreeBSD 5.4. I have a few questions regarding the configuration. I understand that 'options PPS_SYNC' needs to be added to the kernel config file, and that the kernel then needs to be recompiled. You may want to use FreeBSD 6.3, scheduled for release in about 10 days or FreeBSD 7.0 scheduled for release sometime mid January 2008. I vaguely recall some discussion circa May/June 2007 about there being some issues with PPS_SYNC and SMP kernel code in FBSD 6.2. I was preoccupied with other matters at the time, so I didn't really pay attention that much but, I seem to recall that the fix was not trivial and that they were talking about putting the fix into FBSD 6.3 and 7.0 rather than risk making 6.2 unstable as a whole. I am not sure whether or not the final decision included a fix for 6.2 However, he includes a comment from Harlan Stenn stating that 'include GENERIC', 'ident PPS-GENERIC', and 'options PPS_SYNC' need to be added to the file /usr/src/sys/i386/conf/PPS . You need to create a file in directory: /usr/src/sys/architecture/conf/ Where: architecture depends on what kind of hardware you have i386 = Intel, amd64 = AMD, etc. This file doesn't exist on my system. Do I need to create the file from scratch with those items in it, or is it something that is created after the kernel recompile? Yes, you create a kernel configuration file: /usr/src/sys/architecture/conf/filename Where: filename should be the same as kernel ident within eg.: If the contents of your kernel configuration file is: # # Generic kernel configuration with PPS_SYNC option # include GENERIC ident PPS-GENERIC options PPS_SYNC then your kernel configuration filename should be: PPS-GENERIC eg.: /usr/src/sys/architecture/conf/PPS-GENERIC To compile your kernel, log-in as root and issue the following commands: cd /usr/src make buildkernel KERNCONF=filename Where: filename is the name of your kernel configuration file eg: make buildkernel KERNCONF=PPS-GENERIC If kernel compiles without errors, install kernel: make installkernel KERNCONF=filename Where: filename is the name of your kernel configuration file After kernel install, reboot into new kernel: shutdown -r now If new kernel fails to boot: Strike SPACE BAR during bootstrap countdown Select option: 6 - Escape to loader prompt At loader prompt, issue commands: unload boot kernel.old Commands for post-install clean up: cd /usr/obj chflags -R noschg * rm -rf * cd /usr/src make clean You now have a FreeBSD kernel configured for a PPS reference clock. I emailed David Taylor with these questions regarding the configuration, and he replied that he can't quite remember exactly how he configured his system, and if that PPS file needed to be created from scratch or not. So he directed me to the newsgroup. If someone could give me a complete list of steps that need to be taken to configure FreeBSD to use the GPS 18 LVC, or point me to some documentation on the matter, I would greatly appreciate it. I'm new to FreeBSD and don't know my way around. In addition to configuring the kernel as described above, you will also have to configure a serial port by adding the following lines to /etc/devfs.conf: # # Set up serial port for general purpose call-out # Reference: devfs.conf(5) # own cuadx root:wheel permcuadx 0660 own cuadx.init root:wheel permcuadx.init 0660 own cuadx.lock root:wheel permcuadx.lock 0660 Where: x in cuadx = 0 (zero) for COM1, x = 1 (one) for COM2 You will also have to include a link statement in /etc/devfs.conf to link the serial port configured above to the device name the driver expects. Assuming you would be using driver Type 20 and the documentation is correct, the statement would be: linkcuadx gpsu Where: x in cuadx = 0 (zero) for COM1, or 1 (one) for COM2 u in gpsu = u in 127.127.20.u = unit number where unit number is described in documentation for Type 20 driver: http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver20.html and in the man page: ntp.conf(5) After done configuring /etc/devfs.conf, reboot the system for the changes to take effect: shutdown -r now STANDARD DISCLAIMERS APPLY: Use at your own risk, I'm not responsible for what you do, etc. Information herein is based on very few notes and many recollections, some perhaps faulty, of what I did under FreeBSD-7.0-BETA2 running on a cranky old laptop for a proof-of-concept project. FreeBSD 7.0 is now at BETA4, my cranky
Re: [ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
On Sat, 15 Dec 2007 12:37:41 -0600, [EMAIL PROTECTED] (Hal Murray) wrote: options PPS_SYNC Would somebody connected with the FreeBSD people please suggest that they update http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html to include PPS_SYNC An opportunity presents itself right here: http://www.freebsd.org/send-pr.html It might be appropriate to include it (commented out) in GENERIC too. Thanks. -- These are my opinions, not necessarily my employer's. I hate spam. ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
[ntp:questions] Configuring FreeBSD 6.2 for use with Garmin GPS 18 LVC
Hello, As the subject line suggests, I would like to set up FreeBSD 6.2 to use my Garmin GPS 18 LVC as a refclock. I've been following advice from David Taylor's web page on this subject http://www.david-taylor.myby.co.uk/ntp/FreeBSD-GPS-PPS.htm , although he used FreeBSD 5.4. I have a few questions regarding the configuration. I understand that 'options PPS_SYNC' needs to be added to the kernel config file, and that the kernel then needs to be recompiled. However, he includes a comment from Harlan Stenn stating that 'include GENERIC', 'ident PPS-GENERIC', and 'options PPS_SYNC' need to be added to the file /usr/src/sys/i386/conf/PPS . This file doesn't exist on my system. Do I need to create the file from scratch with those items in it, or is it something that is created after the kernel recompile? I emailed David Taylor with these questions regarding the configuration, and he replied that he can't quite remember exactly how he configured his system, and if that PPS file needed to be created from scratch or not. So he directed me to the newsgroup. If someone could give me a complete list of steps that need to be taken to configure FreeBSD to use the GPS 18 LVC, or point me to some documentation on the matter, I would greatly appreciate it. I'm new to FreeBSD and don't know my way around. Thanks! -- Dennis Hilberg, Jr. timekeeper(at)dennishilberg(dot)com NTP Server Information: http://saturn.dennishilberg.com/ntp.php ___ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
