[LinuxPPS] Which patch to use?

Jordan Hayes jmhayes at speakeasy.net
Tue May 13 01:39:00 CEST 2008


>> `-- pps1
>
> why pps0 and pps1?
> remove ktimer before doing ppsctl.

Ok, I got ktimer out of the way.  Now it looks like this:

# tree /sys/class/pps
/sys/class/pps
`-- pps0
    |-- assert
    |-- clear
    |-- dev
    |-- device -> ../../../devices/pnp0/00:07
    |-- echo
    |-- mode
    |-- name
    |-- path
    |-- power
    |   `-- wakeup
    |-- subsystem -> ../../../class/pps
    `-- uevent

Which looks right.  Also there's this:

# dmesg | grep PPS
LinuxPPS API ver. 1 registered
new PPS source serial0 at ID 0

The 'new PPS source' message comes after I "ppsctl /dev/ttyS0 enable"

So that looks good, too.

Then when I start ntpd, I get this:

ntpd[2213]: refclock_nmea: found GPS source "/dev/gps0"
ntpd[2213]: refclock_nmea: try alternate PPS device "/dev/pps0"
ntpd[2213]: refclock_nmea: found PPS source "/dev/pps0"
ntpd[2213]: refclock_nmea: time_pps_kcbind failed: Operation not 
supported

Which all looks great.

But ...

# ntpq -p
     remote  refid   st t when poll reach  delay  offset jitter
===============================================================
 GPS_NMEA(0)  .GPS.   0 l    -   16    0   0.000  0.000   0.002

So close! :-)

/var/log/ntpstats/clockstats shows $GPRMC sentences ...

Any ideas?

Thanks,

/jordan 




More information about the LinuxPPS mailing list