From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup_dectlk module under 2.6.26-1-686 on Debian Sid
Date: Sun, 28 Sep 2008 11:51:22 -0700 [thread overview]
Message-ID: <20080928185122.GA8857@localhost.localdomain> (raw)
In-Reply-To: <48DF5D0F.7010900@baechler.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Sep 28, 2008 at 03:31:43AM -0700, Tony Baechler wrote:
> Hi,
>
> I didn't look at the above url, but I do use a DEC Express and I did
> burn and test the 1.1 beta 20 CD, at least I think it was beta 20. I
> had no problem with getting speech to work, but there was definitely
> sluggish behavior when using the screen review keys. I'm guessing that
> there was a delay of about a second from when I hit a key to when I got
> speech. I don't have that problem with Debian using various kernels on
> different machines.
Hmmm, ok, guess it's a sysresccd bug in that case then. Yes, the
report we have matches what you describe. The report we have states
however that everything is fine, until shortly after entering runlevel
3, which is when the sluggish behavior starts, but those are all the
details we have, and we'd need to know exactly when after entering
runlevel 3 this starts to happen, so we can try to figure out what is
causing the problem. Would you be willing to help debug this?
> On the other hand, I had the same behavior with a
> Doubletalk LT and the same System Rescue CD, so I think it's a problem
> with the CD itself. I also had no problem with grml 1.1rc1 using both
> synths on different processors, although software speech abruptly
> stopped on a machine I was using. On Debian, I am using my custom
> 2.6.24 kernel and the 2.6.25-2-686 kernel package. I haven't upgraded
> to 2.6.26 yet. With the Shane Etch CD using 2.6.18, I also noticed a
> slight delay in getting speech feedback but I figured that was because I
> was running from CD.
Ok, I tested with a doubletalk pc, and a bns, and didn't see this
issue with either synth under 1.1.0, and the 1.1.1 betas. Looks like
the problem is with more synths than just the dectalk in that case,
but I certainly haven't been able to reproduce it here with the
hardware I have to work with. Do you mind if I add the info you
provided to the speakup-info page, so we have a wider documentation of
the issue?
Greg
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkjf0ioACgkQ7s9z/XlyUyCzIgCfShIttoJvFOm0w8lq+rHSVHex
H+gAn1vLUxNuq2dY3JWtSdvx1ctR7b6H
=F3uT
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Erik Heil
` William F. Acker WB2FLW +1-303-722-7209
` Erik Heil
` Gregory Nowak
` Tony Baechler
` Gregory Nowak [this message]
` Tony Baechler
` Gregory Nowak
` Tyler Spivey
` luke
` Gregory Nowak
` Tony Baechler
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=20080928185122.GA8857@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).