From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup mailing list <speakup@braille.uwo.ca>
Subject: Re: experience with speakup git of today tusing 2.6.25-gentoo-r5
Date: Sun, 29 Jun 2008 18:15:50 -0500 [thread overview]
Message-ID: <20080629231550.GA9502@linux1> (raw)
In-Reply-To: <18536.4683.548065.168363@ccs.covici.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, Jun 29, 2008 at 06:52:59PM -0400, John covici wrote:
> OK, so I tried the latest speakup git with kernel 2.6.25 gentoo
> sources and the following happened:
>
> I had speakout module built in and soft and dectalk express as
> modules. Now the first time I booted, I let it talk without pressing
> any keys and it eventually hung somewhere, i.e. lost speech and the
> system was dead or crashed.
Are you sure it was dead or crashed, or did you just lose speech? The
reason I ask is you might have come across the issue that happens when
we time out too many times waiting for the synth to tell us it can
receive more data -- after it times out so many times we assume that
someone has turned off the synth and put it in an unavailable status.
> Then I rebooted and for quite a while --
> unlike my present kernel which is 2.6.24-gentoo-r5 and a speakup git
> of about 2 month ago -- I could get no keyboard access for some time,
> although it did eventually appear. Then the system came up normally,
> except that I had an app which could not initialize a modem
> successfully for some reason, so I went back to the former kernel and
> speakup. The app is called bbbs which I use to control modem events.
> I suppose I could use cron, but this is much more convenient.
The modem issue sounds like it might be the "floating serial ports" issue
reported in Bugs.txt.
William
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkhoF6YACgkQblQW9DDEZTibaACgjj1u+NOwQfalKBgZLWPJY9t9
HR8AmgK6NL6TEW/Yb8msqv5oK9/4PS8a
=qqfx
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
John covici
` William Hubbs [this message]
` John covici
[not found] ` <Pine.LNX.4.64.0806302114200.3570@gube.gnpgvphfpbzzhavpngvbaf.arg>
` John covici
` luke
` William Hubbs
[not found] ` <20080629230330.GF5963@implementation>
` John covici
luke
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=20080629231550.GA9502@linux1 \
--to=w.d.hubbs@gmail.com \
--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).