From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Problems with Software Speech
Date: Mon, 18 Jun 2007 12:28:26 -0700 [thread overview]
Message-ID: <20070618192826.GB16725@localhost.localdomain> (raw)
In-Reply-To: <7E46937879814D8CBFB7CDA77A3B22B8@Michelle>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It seems you may be running into a similar problem which I reported
happens when switching synths with the doubletalk pc driver built into
the kernel, and set as the default. Try starting the system with none
as the default synth, and then loading software speech, starting with
the sftsyn module. If that works like it's supposed to, then it looks
like the ltlk driver has issues as well.
Greg
On Mon, Jun 18, 2007 at 03:21:19PM -0400, ace wrote:
> Hi all
>
> I just spent the last two weeks building a LFS system then installing
> necessary packages from the BLFS book. Now, I am to the point of installing
> software speech. Speech-Dispatcher is installed, as is Speechd-Up. Espeak
> is my synth of choice. I also setup my kernel to compile sftsyn as a
> module. In the default synth field in the kernel, though, I have ltlk as
> that is my primary synth. I have verified that Speech-Dispatcher and
> Speechd-up are working because I performed the speechd-up probe test and it
> was spoken. The problem happens when I do modprobe speakup_sftsyn. The
> system simply freezes; no speech, no beeps, nothing. In fact, I'm forced to
> restart forcefully with the ower button. Where should I look to find
> whatever error may be occurring? If I need to get sighted assistance,
> that's not a problem.
>
> Thanks,
> Robby
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
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.6 (GNU/Linux)
iD8DBQFGdtza7s9z/XlyUyARAowVAJsG+gI++/HpsVLhbDvQDfHsLexjngCfUbHz
f42LsQPVqBrB0CYymgbaDxc=
=Bcwz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
ace
` Gregory Nowak [this message]
` ace
` Michael Whapples
` Jan Buchal
-- strict thread matches above, loose matches on Subject: below --
Problems with software speech Zachary Kline
` Farhan
[not found] ` <1173612197.31048.25.camel@layla>
` Michael Whapples
` Erik Heil
[not found] ` <1173632254.31048.139.camel@layla>
` Michael Whapples
` Alex Snow
` Zachary Kline
[not found] ` <1173640422.31048.168.camel@layla>
` Michael Whapples
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=20070618192826.GB16725@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).