Date: Fri, 05 Nov 1999 15:50:11 GMT From: Marty Cawthon <mrc@ChipChat.com> To: freebsd-stable@freebsd.org Subject: PPS Timing Interface and ONCORE GPS Clock / NTPD Message-ID: <19991105155011X.mrc@ChipChat.com>
next in thread | raw e-mail | index | archive | help
SUMMARY: ONCORE GPS Clock source for NTPD on FreeBSD was working with 3.3-Stable (Oct 8 1999). With 3.3-Stable (Nov 4 1999) NTPD fails with a 'time_pps_setparams: Inappropriate ioctl for device' message. It seems that '/dev/pps' may have been changed to '/dev/lppps0' REFERENCE: http://phk.freebsd.dk/ntp/ DISCUSSION: I had a GPS Clock working with FreeBSD 3.3-Stable as described at http://phk.freebsd.dk/ntp/ Using FreeBSD 3.3-Stable (as of Oct 8 1999) I had this working. NTPD would execute and diagnostic messages from the 'ONCORE' GPS receiver would appear on STDOUT. I recently upgraded to 3.3-Stable (Nov 4 1999). Now the NPTD program exits with a message: #ntpd -d -d <some messages cut> getnetnum given 127.127.30.0, got 127.127.30.0 (7f7f1e00) poll_update: at 0 127.127.30.0 poll 6 next 63 refclock_open: fd 8 modem status 7 refclock_ioctl: fd 8 flags 20 time_pps_setparams: Inappropriate ioctl for device So it seems that there is trouble with 'time_pps_setparams'. I checked 'dmesg' to see if the pps device appears: $dmesg | grep pps lppps0: <Pulse per second Timing Interface> on ppbus 0 This 'lppps0' device (3 p's) looks strange to me. I tried changing the name of /dev/pps to be /dev/lppps0 but to no avail. It seems that something may have changed in 3.3-Stable between Oct 8 and Nov 4 with respect to the pps device. Perhaps somebody can provide a pointer for me with respect to this problem. Marty Cawthon ChipChat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991105155011X.mrc>