From: "Ahmed" <ahmed@ahmed63.wanadoo.co.uk>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Possibly Related to Keypad Issue
Date: Tue, 2 Nov 2004 09:32:36 -0000 [thread overview]
Message-ID: <003501c4c0be$e3c87160$2c074254@admin> (raw)
In-Reply-To: <20041102062527.GB1303@lnx3.holmesgrown.com>
test
----- Original Message -----
From: "Steve Holmes" <steve@holmesgrown.com>
To: <speakup@braille.uwo.ca>
Sent: Tuesday, November 02, 2004 6:25 AM
Subject: Re: Possibly Related to Keypad Issue
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> This reminds me of a problem I had some while back when I had some
> interrupt conflicts on my '486 with IDE controlers. Be sure you
> aren't getting any messages that say something like, "Loss of
> interrupt streaming" or something to that effect. I also ran into
> some extreme sluggishnes recently when I started getting some strange
> communication errors with my hard drive but then that mess was
> accompanied with a bunch of I/O errors and having to re-tune my file
> system amazingly, I didn't lose a single file during that crisis.
> Since then, I haven't had any more problems. But I digressed; it
> sounds like some kind of hardware issue to me. When you press a key,
> you cause speakup to send a "shut up" command to the synth. I don't
> remember what kind of synth you're using but if it is serial by
> chance, there could be some possible collision on the serial line. Be
> sure and verify your communications parameters on your synth; I
> believe Speakup uses hardware handshaking in all synths except for the
> old Dectalk.
>
> HTH.
>
> On Sat, Oct 30, 2004 at 12:45:43AM -0700, Zachary wrote:
> > Hi,
> > I have been a bit more successful in attempting to use the unresponsive
> > keypad. Not much, not enough to work, but a bit.
> > I have noticed the following message, which I suspect may have something
to
> > do with the problem, being sent to my Dectalk Express on /dev/ser0:
> > Timeout Flush
> > Possibly this is related to the distribution itself, not the problem. I
> > don't know, at this point I just want something that works.
> > Basically what happens is that when I boot up an installation cd, the
> > program speaks fine. Reads all kernel messages, etc.
> > However, I press a key, any key, and things fall apart. The keypad and
> > entire keyboard becomes sluggish, unusably so. I cannot do anything and
> > expect a response. The speakup program seems to be extremely slow. It
> > acknowledges every action, eventually. But it takes it's time about it.
> > Any help is greatly appreciated,
> > Zack
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
>
> - --
> HolmesGrown Solutions
> The best solutions for the best price!
> http://ld.net/?holmesgrown
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFBhyhXWSjv55S0LfERAhpWAJ9K0T5lTGtW0cGmd7/fGlAp+olnawCdGOH5
> ETnTpkcKaRkoUma8Asr8Rw0=
> =R/vC
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary
` Steve Holmes
` Ahmed [this message]
` Sean McMahon
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='003501c4c0be$e3c87160$2c074254@admin' \
--to=ahmed@ahmed63.wanadoo.co.uk \
--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).