[ntp:questions] DCF77 Problem

Rob nomail at example.com
Tue Feb 24 17:31:29 UTC 2009

Rob van der Putten <rob at sput.nl> wrote:
> Hi there
> Rob wrote:
>> Most likely some stupid program has changed the settings of the COM port.
>> (especially the baudrate)
>> For example, in SuSE Linux when you are so unfortunate to click on the
>> "hardware information" icon in YaST, everything is messed up in the process
>> of detecting what is attached to your serial ports.
> There is no qui on this box. It's a server.

So do a "stty -a </dev/refclock-0" the next time it is messed up again.

Then you should get this output:

speed 50 baud; rows 0; columns 0; line = 0;
intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>;
eol = <undef>; eol2 = <undef>; swtch = <undef>; start = <undef>; stop = <undef>;
susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>;
flush = <undef>; min = 1; time = 0;
parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff
-iuclc -ixany -imaxbel -iutf8
-opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
-isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt
-echoctl -echoke

If not, something has messed up your port.  Your task to find out what
it is.

More information about the questions mailing list