public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Trouble with speech dispatcher.
Date: Wed, 17 May 2006 16:41:06 -0700	[thread overview]
Message-ID: <20060517234106.GA31492@localhost.localdomain> (raw)
In-Reply-To: <20060517232344.GA11339@lnx3.holmesgrown.com>

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

I believe I reported on this a while back when describing the kernel
panics I got when trying to switch between bns, dtlk, and
sftsyn. Unless something has changed since that report, (and I don't
know if it has, since I haven't upgraded speakup since then yet), then
you need to modprobe sftsyn by hand, at least that's something that I
needed to do.

Greg


On Wed, May 17, 2006 at 04:23:46PM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> I think I'm on to something.  I'm sorking this machine by remote ssh
> session so can't be totally sure but What I see so far is the sftsyn
> module is not being auto loaded when echoing "sftsyn" to
> /proc/speakup/synth_name.  That used to work.  when I echoed "sftsyn" to
> /proc..., the value did not stick; as soon as I modprobed
> speakup_sftsyn, then the /proc variable got updated.  Is this change by
> design? do we have to explicitely modprobe speakup modules now or am I
> missing something some place.  I don't recall seeing keyhelp in there
> either but that's for another discussion:).  if it is by design, I'll
> just add the modprobe line into my rc.speakup script and it'll be all
> good.
> 

- -- 
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.3 (GNU/Linux)

iD8DBQFEa7SS7s9z/XlyUyARAjh5AKCnXFNuLhh2h4KtiqbQYaR7HBh2LACfWi0N
749xudhyZF3zh4j9vhvmNqA=
=F0H9
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Satyam
 ` Tomas Cerha
 ` Willem van der Walt
 ` Hynek Hanke
   ` Steve Holmes
     ` Michael Whapples
       ` Steve Holmes
         ` Hynek Hanke
           ` Steve Holmes
             ` Gregory Nowak [this message]
               ` Steve Holmes
                 ` Gary Cramblitt
                   ` Sean M McMahon
                     ` Steve Holmes
                     ` Hynek Hanke
                 ` Gregory Nowak
                   ` Steve Holmes
                     ` Gregory Nowak
                 ` A synthesizer analogy Jonathan Duddington
             ` Trouble with speech dispatcher Sean M McMahon
   ` Satyam
     ` 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=20060517234106.GA31492@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).