public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: speakup@braille.uwo.ca
Subject: Re: soft synth not working at all
Date: Fri, 2 May 2008 21:41:28 -0500	[thread overview]
Message-ID: <20080503024128.GB28572@linux1> (raw)
In-Reply-To: <18459.52197.502856.94627@ccs.covici.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi John,

This will switch between synths that are already loaded or built in, but
it will not load a synth module.  You still need to either have the
module built in or use modprobe to load it first.

On Fri, May 02, 2008 at 10:20:21PM -0400, John covici wrote:
> What about echoing soft to  /sys/module/speakup/parameters/synth ?  Is
> that supposed to work -- I gathered from the logs that it was supposed
> to work now.
> 
> on Friday 05/02/2008 William Hubbs(williamh@gentoo.org) wrote
>  > -----BEGIN PGP SIGNED MESSAGE-----
>  > Hash: SHA1
>  > 
>  > Hi John,
>  > 
>  > 
>  > > Hi.  I am using a git pull of speakup from April 13 and kernel
>  > > 2.6.24-gentoo-r5 and the software speech is not working at all.  I
>  > > have speakout builtin and soft as a module, but either echoing soft to
>  > > /sys/module/speakup/parameters/synth or modprobing the module
>  > > speakup_soft loads the module, but mothing else happens.  Also,
>  > > speechd-up says its trying to open the device in the old way and it
>  > > then says it can't find /dev/softsynth .
>  > 
>  > Are you passing the start parameter to the module when you load it?  If
>  > you are using /etc/modules.autoload.d/kernel-2.6 to load the soft synth
>  > module, the line should look like:
>  > 
>  > speakup_soft start=1
>  > 
>  > Or, if you are loading it manually,
>  > 
>  > modprobe speakup_soft start=1
>  > 
>  > Then go ahead and run speechd-up.
>  > 
>  > 
>  > - -- 
>  > William Hubbs
>  > gentoo accessibility team lead
>  > williamh@gentoo.org
>  > -----BEGIN PGP SIGNATURE-----
>  > Version: GnuPG v2.0.9 (GNU/Linux)
>  > 
>  > iEYEARECAAYFAkgbr2wACgkQblQW9DDEZTh6HgCaAptWF7YB8190BDOfRz9Z5/S2
>  > qbkAnjhKqjxu/UnGIOx9t8lig+tikKq0
>  > =1ymU
>  > -----END PGP SIGNATURE-----
>  > 
>  > _______________________________________________
>  > Speakup mailing list
>  > Speakup@braille.uwo.ca
>  > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> -- 
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
> 
>          John Covici
>          covici@ccs.covici.com
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkgb0NgACgkQblQW9DDEZTi2mgCfQfkU/DH54g+t9tT6/wODpLnE
vwYAn3UUFP5LxqOQnQtTjtncaBJfj59c
=aruz
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John covici
 ` William Hubbs
   ` John covici
     ` William Hubbs [this message]
       ` John covici

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=20080503024128.GB28572@linux1 \
    --to=williamh@gentoo.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).