From udovdh at xs4all.nl Sun Nov 3 14:13:29 2019 From: udovdh at xs4all.nl (Udo van den Heuvel) Date: Sun, 3 Nov 2019 14:13:29 +0100 Subject: [LinuxPPS] PPS not working: root cause? Message-ID: <4f578efa-e223-d021-da7d-9fb458a8a5cf@xs4all.nl> Hello, We see in /var/log/messages: REFCLOCK: refclock_ppsapi: time_pps_create: Operation not supported Our config: # gzip -dc /proc/config.gz |grep PPS CONFIG_PPS=y # CONFIG_PPS_DEBUG is not set CONFIG_NTP_PPS=y # PPS clients support CONFIG_PPS_CLIENT_KTIMER=m CONFIG_PPS_CLIENT_LDISC=y # CONFIG_PPS_CLIENT_PARPORT is not set # CONFIG_PPS_CLIENT_GPIO is not set # PPS generators support # gzip -dc /proc/config.gz |grep NO_HZ # CONFIG_NO_HZ_IDLE is not set # CONFIG_NO_HZ_FULL is not set # CONFIG_NO_HZ is not set The issue happens on a system with RT kernel and one with vanilla kernel.org. Why is PPS configurable and compilable yet does it not function at runtime? Any ideas? Please post! Udo From udovdh at xs4all.nl Sun Nov 3 17:18:02 2019 From: udovdh at xs4all.nl (Udo van den Heuvel) Date: Sun, 3 Nov 2019 17:18:02 +0100 Subject: [LinuxPPS] PPS not working: root cause? In-Reply-To: <4f578efa-e223-d021-da7d-9fb458a8a5cf@xs4all.nl> References: <4f578efa-e223-d021-da7d-9fb458a8a5cf@xs4all.nl> Message-ID: On 03-11-2019 14:13, Udo van den Heuvel wrote: > Why is PPS configurable and compilable yet does it not function at runtime? > > Any ideas? Please post! ntpd run outside of the chroot does not have an issue. ntpd in the chroot does have this issue. We found out that the major number of the pps0 device had changed. In /dev it was 253, in the chroot dev it was 252 (which had worked...). So we recreated pps0 in the chroot with the correct number and things started to work... Udo