From: Charles Crawford <ccrawford@Starpower.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Help! The Dectalk PC is hosing my clock!
Date: Sun, 2 May 2004 15:07:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0405021506260.7057-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0405020923580.14987@homerun.midsouth.rr.com>
I was using the dectalk PC for awhile in a computer last fall.
It worked fine with Redhat 9 and I don't recall any clock problems. I
don't remember the Kernel version but probably 2.4.
On Sun, 2 May 2004,
Adam Myrow wrote:
> Well, after getting the Dectalk PC2 driver working with Speakup, I never
> expected this. When I'm actively using the Dectalk PC, my clock starts
> wondering into the sunset. For example, by the end of the day yesterday,
> it was about 3 minutes slow. Today, as a test, I set it and then ran a
> loop of having ntpdate query the time from time.nist.gov every 60 seconds.
> I had it set to query without setting the clock, so I could see how far it
> was drifting. The offsets over just 3 minutes are alarming!
>
> 6.317230 seconds slow in minute one, 11.267927 seconds slow after 2
> minutes, 16.887154 seconds slow after minute 3, and so on. If I leave the
> computer idle, with ntpd running to constantly adjust the time, it becomes
> stable, so it's clearly something that the Dectalk PC is doing. Has
> anybody else had this problem? For that matter, is anybody even using the
> Dectalk PC driver besides me?
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
-- Charlie Crawford
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Adam Myrow
` shaun Oliver
` Hart Larry
` Adam Myrow
` Charles Crawford [this message]
` Adam Myrow
` Charles Crawford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0405021506260.7057-100000@localhost.localdomain \
--to=ccrawford@starpower.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).