public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: getting started with speakup out of git
Date: Tue, 8 Jul 2008 14:17:41 +0200 (SAST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807081413500.21452@localhost.localdomain> (raw)
In-Reply-To: <20080708115814.GA3561@debian-hp.lan>

Not sure I'll answer all of your questions, but I would say to start the 
synth in the kernel you should echo the correct name to 
/sys/speakup/modules/parameters/synth_name or whatever the correct new 
path is.
There are many ways of starting modules automaticly on startup.
Distributions usually have a /etc/modules.conf or modprobe.conf file where 
it can be done.
What I use specificly for speech is the rc.local file.  Just put your 
modprobe in their.


On Tue, 8 Jul 2008, Daniel Dalton wrote:

> Hi,
> 
> I applied speakup to a kernel out of debian sid (2.6.25-6) I believe it
> was.
> 
> First, uname -a only says 2.6.25 it doesn't mention -6. But here are my
> speakup problems:
> 
> - Using speechd-up (soft synth) I get crashes every 5 minutes or so.
> - When speakup is talking away numpad enter doesn't shut it up. I must
> do insert numpad enter and then turn it back on.
> - Sometimes speakup won't respond, eg. in mutt and I must kill
> speechd-up to shut it up and then restart speechd-up to get speakup
> going again.
> Anyone know how I can fix these?
> 
> The next thing I was wondering: How do I load synths that are built in
> the kernel? eg. not modules?
> And just out of curiosity, how would one start a synth built as a module
> automatically?
> So at boot up say just before the log in screen?
> 
> Thanks for any help,
> 
> -- 
> Daniel Dalton
> 
> http://members.iinet.net.au/~ddalton/
> <d.dalton@iinet.net.au>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.


  reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Daniel Dalton
 ` Willem van der Walt [this message]
 ` Samuel Thibault
   ` Daniel Dalton
   ` Daniel Dalton
     ` Samuel Thibault
       ` Daniel Dalton
         ` Samuel Thibault
   ` William Hubbs
     ` Samuel Thibault
       ` Samuel Thibault
         ` Daniel Dalton
           ` Samuel Thibault
             ` Daniel Dalton

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=Pine.LNX.4.64.0807081413500.21452@localhost.localdomain \
    --to=wvdwalt@csir.co.za \
    --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).