public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "ace" <ace@talkingirc.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Problems with Software Speech
Date: Mon, 18 Jun 2007 15:21:19 -0400	[thread overview]
Message-ID: <7E46937879814D8CBFB7CDA77A3B22B8@Michelle> (raw)

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 



             reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 ace [this message]
 ` Gregory Nowak
   ` 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=7E46937879814D8CBFB7CDA77A3B22B8@Michelle \
    --to=ace@talkingirc.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).