Date: Sun, 7 Mar 1999 18:05:10 +0100 From: Pierre Beyssac <pb@fasterix.freenix.org> To: Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG Subject: Re: NTP nanokernel support (experimental) Message-ID: <19990307180510.A1220@fasterix.frmug.fr.net> In-Reply-To: <19990306200053.B30895@keltia.freenix.fr>; from Ollivier Robert on Sat, Mar 06, 1999 at 08:00:53PM %2B0100 References: <19990306164238.A29897@keltia.freenix.fr> <14112.920744164@critter.freebsd.dk> <19990306200053.B30895@keltia.freenix.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 06, 1999 at 08:00:53PM +0100, Ollivier Robert wrote:
> The two outputs I sent were with 4.0.90f. When I run 4.0.92c, ntpd is not
> able to get any accurate data from the device whereas 4.0.90f does.
>
> I get lots of these in /var/log/messages and it doesn't sync at all.
> -=-=-
> Mar 6 14:02:25 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 3 bits
> Mar 6 14:02:29 tara ntpd[7600]: parse: convert_rawdcf: INCOMPLETE DATA - time code only has 2 bits
It's typical from bad parity setting on your serial port.
Try a stty on that port; I bet it will show that PARENB is set.
Unset it and things should go back to normal.
> Maybe it is a problem with 4.0.92c...
Yes, it's a problem with most of the ntpd 4.0.9x series. There's
absolutely no reason why you should enable PARENB for a raw DCF77
driver; yet that's what ntpd's configure does, at least under
FreeBSD.
I sent a bug report to the ntpd team a while ago but haven't heard
from them.
--
Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org
{Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990307180510.A1220>