On 03-11-2019 14:36, Achim Gratz via devel wrote: > configuration, like so: > > CONFIG_NO_HZ_COMMON=y > CONFIG_NO_HZ_IDLE=y > # CONFIG_NO_HZ_FULL is not set > CONFIG_NO_HZ=y
I do not understand why NO_HZ is necessary or even usable without conflict witgh PPS such as CONFIG_NO_HZ_COMMON. > CONFIG_PPS=y > # CONFIG_PPS_DEBUG is not set > # PPS clients support > # CONFIG_PPS_CLIENT_KTIMER is not set > CONFIG_PPS_CLIENT_LDISC=m > CONFIG_PPS_CLIENT_PARPORT=m > CONFIG_PPS_CLIENT_GPIO=m > # PPS generators support Except for the GPIO client that is what is in use here. > Once you have that working correctly you can try to enable hardpps, How? >> Yet we still see: >> REFCLOCK: refclock_ppsapi: time_pps_create: Operation not supported > > So does the PPS device exist and does it generate events? # ppstest /dev/pps0 trying PPS source "/dev/pps0" found PPS source "/dev/pps0" ok, found 1 source(s), now start fetching data... source 0 - assert 1572791560.772062581, sequence: 62 - clear 1572791559.972049895, sequence: 62 source 0 - assert 1572791560.772062581, sequence: 62 - clear 1572791560.972135103, sequence: 63 source 0 - assert 1572791561.772070058, sequence: 63 - clear 1572791560.972135103, sequence: 63 source 0 - assert 1572791561.772070058, sequence: 63 - clear 1572791561.972073160, sequence: 64 source 0 - assert 1572791562.772077047, sequence: 64 - clear 1572791561.972073160, sequence: 64 source 0 - assert 1572791562.772077047, sequence: 64 - clear 1572791562.972080079, sequence: 65 source 0 - assert 1572791563.772082569, sequence: 65 - clear 1572791562.972080079, sequence: 65 > If it's > coming in via a serial device, have you started an ldattach to enable > the PPS line discipline? Yes, that makes the /dev/pps0 device appear. We start ntpd after this step. If it is a link to the actual device (as usual > /dev/gpspps0 -> /dev/pps0), does it point to the correct device? Are > the permissions on the device correct? Sure, in the chroot (!) the devices (created with mknod) are owned by ntp: # ls -l /chroot/ntpd/dev/ total 0 lrwxrwxrwx 1 root root 5 Mar 9 2018 gps0 -> ttyS0 lrwxrwxrwx 1 root root 4 Mar 9 2018 gpspps0 -> pps0 srw-rw-rw- 1 root root 0 Nov 3 13:29 log crw-r--r-- 1 ntp ntp 1, 3 Mar 9 2018 null crw-r--r-- 1 ntp ntp 252, 0 Mar 9 2018 pps0 crw-r--r-- 1 ntp ntp 4, 64 Mar 9 2018 ttyS0 If I run ntpd outside of the chroot the error dopes not appear and PPS works. So we take another look at the chroot... Udo _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel