I tried to symlink acts1 to /dev/ttS4 and later I tried to /dev/modem. Where I can configure the baudrate?
I'll try to use minicom, I was using KPP to dial to NIST and test my line. Thet fact that I'm in Brazil is important? Thanks, Diego On Thu, Jan 8, 2009 at 6:39 AM, Uwe Klein <[email protected]>wrote: > Diego Ramos wrote: > > It almost worked!!! > > > > After I disabled the AppArmor, looks like the ntp daemon tries to start > the > > modem, but give me the error: *acts: no modem*. I have the symlink > > /dev/acts1 to /dev/modem > > > > Here's my debug: > > > newpeer: 127.0.0.1->127.127.18.1 mode 3 vers 4 poll 6 10 flags 0x21 0x1 > ttl > ............ > > acts: setup ATB1&C0&D2E0L1M1Q0V1 > > refclock_transmit: at 1 127.127.18.1 > .......... > > > > addto_syslog: acts: no modem > > > > acts: 4124 (6 3) 7 Q0V1ATH > > acts: 4124 (6 3) 2 OK > > refclock_setup fd 4 modem status: 0x4126 > > refclock_ioctl: fd 4 flags 0xa4 > > acts: setup ATB1&C0&D2E0L1M1Q0V1 > > addto_syslog: acts: no modem > > > > acts: 4124 (6 3) 7 Q0V1ATH > > acts: 4124 (6 3) 2 OK > > That's a bit over my head. > Hmm, the symlinks go like this?: > /dev/acts1 to -> /dev/modem -> /dev/ttyS4 > > got the correct tty, baudrate? > > can you access the clock via minicom or cu? > ( the setup string seems to implicate that > the clock behaves similar to a hayes modem (AT style commands) > ) > > > Got the "proper" cable ? > > uwe > > > _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
