[pkg-ntp-maintainers] Bug#785665: Bug#785665: ntp: support for atom driver not included

Robin Laing MeSat at TelusPlanet.net
Mon Apr 24 02:11:08 UTC 2017


On Sun, 17 Jan 2016 13:21:18 +0900 Hideki Yamane <henrich at debian.or.jp> 
wrote:
> On Sat, 16 Jan 2016 14:51:44 +0100
> Kurt Roeckx <kurt at roeckx.be> wrote:
> > Maybe the point is that PPS is currently not supported, and that's
> > really all that needs to be fixed?
> 
>  It's better to support if it doesn't have any side effect, IMHO.
>  And I don't have any idea for it, it's good to ask upstream developers.
> 
> -- 
> Regards,
> 
>  Hideki Yamane     henrich @ debian.or.jp/org
>  http://wiki.debian.org/HidekiYamane
> 
> 

Hello,  I have just been playing with the latest Raspian lite to setup a 
few GPS time servers.  We use quite a few for remote time servers due to 
cost and size.

Present kernel supports pps by module and can be tested with ppstools to 
confirm pps operation.  On the third system being created, I thought I 
would do some testing of the ntp configurations to see if I really need 
to compile the ntp software myself for pps support.  After testing all 
the recommended ntp directives from ntp.org, I have come to the 
conclusion that atom support is required to get pps to work.

Remove the Raspian version of NTP and then compile the source.

To test this, I compiled the ntp source my self.

	./configure --enable-linuxcaps --with-NMEA --with-ATOM

	make

	sudo make install

After compiling the source and then modifying /etc/init.d/ntp to point 
to the correct software, start ntp with the correct ntp.conf file 
settings, pps works as it is supposed to.

PPS is enabled by changing /boot/config.txt to tell the Pi which GPIO 
pin and adding in the pps kernel module.

With pps support now a kernel module, it would be advisable to add ATOM 
support within ntp so users don't have to recompile ntp to continue 
support when upgrades occur.


Robin Laing



More information about the pkg-ntp-maintainers mailing list