[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ntp-bugs
Subject:    [ntp:bugs] [Bug 282] New: clock type 2 invalid, tty device problem?
From:       bugzilla () ntp ! org
Date:       2004-02-20 16:43:29
Message-ID: 20040220164329.EA4BFD25A () maccarony ! ntp ! org
[Download RAW message or body]

http://bugzilla.ntp.org/show_bug.cgi?id=282

           Summary: clock type 2 invalid,  tty device problem?
           Product: ntp
           Version: 4.2.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: refclock - (other)
        AssignedTo: stenn@ntp.org
        ReportedBy: istullier@aacounty.org
                CC: bugs@ntp.org


Is there a problem with the code that handles the tty devices?  I have tried and
tried but could not get ntpd to recognize a type 2 clock.  I have had this clock
working on a different OS. I am able to connect to /dev/ttyS1 using minicom
where the clock is connected. The clock does respond properly.   Am I unaware of
some change or feature or interaction between npt 4+ and  linux 2.4.20-8?  I was
able build and get ntp 3.5.93e to connect to the clock on linux 2.4.20-8.  How
can I get more information on clock failure in syslog?  I have found that all
versions tested seem to startup Ok and run with the exception of the clock error
in the newer releases.  

Prior to upgrading to RedHat 9 (kernel 2.4.20-8), I had ntp 3.x  working on
RedHat 6.2 (kernel 2.2.x).  syslog output:
Feb 19 12:19:11 Homer ntpd[30062]: refclock_newpeer: clock type 2 invalid
while I am using:
Feb 19 12:19:11 Homer ntpd[30062]: ntpd 4.1.1c-rc1@1.836 Thu Feb 13 12:17:19 EST
2003 (1)

I tried ntp 4.2.0 from your ftp site with the same results:
Feb 20 09:45:42 Homer ntpd[9049]: ntpd 4.2.0@1.1161-r Fri Feb 20 08:37:39 EST
2004 (1)
Feb 20 09:45:42 Homer ntpd[9049]: precision = 1.000 usec
Feb 20 09:45:43 Homer ntpd[9049]: no IPv6 interfaces found
Feb 20 09:45:43 Homer ntpd[9049]: kernel time sync status 0040
Feb 20 09:45:43 Homer ntpd[9049]: Frequency format error in /etc/ntp.conf
Feb 20 09:45:43 Homer ntpd[9049]: refclock_newpeer: clock type 2 invalid
Feb 20 09:45:43 Homer ntpd[9049]: configuration of 127.127.2.0 failed

But I find an old version of ntp from you ftp site does work.
Feb 20 10:09:49 Homer xntpd[12932]: xntpd 3-5.93e Fri Feb 20 10:00:10 EST 2004 (1)
Feb 20 10:09:52 Homer xntpd[12932]: peer GPS_TRAK(0) event 'event_reach' (0x84)
status 'unreach, con
f, 1 event, event_reach' (0x8014)
Feb 20 10:10:56 Homer xntpd[12932]: synchronized to GPS_TRAK(0), stratum=0


exerpt from /etc/ntp.conf;
     restrict 127.127.2.0
#Trak GPS model 8821M
#       flag4 1 = turn on clock data logging Trak GPS 8821M
#       flag4 0 = turn off clock data logging Trak GPS 8821M
#server 127.127.2.0
server  127.127.2.0  minpoll 4 maxpoll 4
fudge   127.127.2.0 time1 0.024375



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
bugs mailing list
bugs@ntp.org
http://mailman.ntp.org/mailman/listinfo/bugs
[prev in list] [next in list] [prev in thread] [next in thread]