From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fed1rmmtao10.cox.net ([68.230.241.29]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1FgVNI-0001rk-00 for ; Wed, 17 May 2006 19:24:16 -0400 Received: from lnx2.holmesgrown.com ([70.162.12.128]) by fed1rmmtao10.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060517232344.ODOQ18458.fed1rmmtao10.cox.net@lnx2.holmesgrown.com> for ; Wed, 17 May 2006 19:23:44 -0400 Received: from lnx3.holmesgrown.com ([192.168.1.5] ident=mail) by lnx2.holmesgrown.com with esmtp (Exim 4.10) id 1FgVMj-0003ci-00 for speakup@braille.uwo.ca; Wed, 17 May 2006 16:23:41 -0700 Received: from steve by lnx3.holmesgrown.com with local (Exim 4.20) id 1FgVMo-0002x3-1U for speakup@braille.uwo.ca; Wed, 17 May 2006 16:23:46 -0700 Date: Wed, 17 May 2006 16:23:46 -0700 From: Steve Holmes To: speakup@braille.uwo.ca Subject: Re: Trouble with speech dispatcher. Message-ID: <20060517232344.GA11339@lnx3.holmesgrown.com> Mail-Followup-To: speakup@braille.uwo.ca References: <20060517073516.GA10069@lnx3.holmesgrown.com> <20060517205123.GA10884@lnx3.holmesgrown.com> <1147900475.5510.18.camel@chopin> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1147900475.5510.18.camel@chopin> User-Agent: Mutt/1.5.6i Sender: "Steve Holmes,,," X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.8rc1 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2006 23:24:16 -0000 -----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. On Wed, May 17, 2006 at 11:14:34PM +0200, Hynek Hanke wrote: > Steve Holmes pí?e v St 17. 05. 2006 v 13:51 -0700: > > I used the same shell script I've always been using. The only thing > > that really changed was Speakup version; wonder if that could have > > anything to do with it? > > Possibly yes. > > > Maybe I'll have to go and try and run each of those steps manually with a second > > or two to spare between each. > > Yes. That would be useful. The only steps you need to do are: > 1) load speakup > 2) load the sftsyn module > 3) start speechd-up > Speech Dispatcher, Festival and other components have nothing to do with > this. It is entirely between speechd-up and Speakup. > > > I'm just baffled that it can't find /dev/softsynth when it is *REALLY THERE*. > > It doesn't say it can't find it. It can't open it. Maybe it is there but > it is not working for some reason. > > Yes, it is puzzling. I can't think of any reason why the system should > refuse to open it as is apparent from the log files you sent, supposing > sftsyn is loaded and the permissions are as you described. The best > next step would be to try manually and make sure the sftsyn module > gets fully loaded before speechd-up is started. > > Please let me know, > Hynek Hanke > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFEa7CAWSjv55S0LfERAwXKAKC/GHvZLrCJGE6PP5HDK57Mxl2jGQCfRiKL u8eZbwlpJuYgDnC6pXV6bDc= =3GJe -----END PGP SIGNATURE-----