I *NEVER* got this to work with Speakup. When I did a "say -d" I get this: daemon mode: No such device Also, which order should I do the below commands? should I load speakup_softsynth first followed by "say" (when fixed) or visa versa? Also, I kept getting my speakout when I quite deliberately specified speakup_sftsyn. In fact, see the abreviated lsmod listing below. Module Size Used by Not tainted speakup_spkout 1928 0 (autoclean) (unused) speakup_sftsyn 2352 0 (autoclean) [speakup_spkout] speakupmain 42516 0 [speakup_spkout speakup_sftsyn] nls_cp437 4316 2 (autoclean) vfat 9580 2 (autoclean) fat 30392 0 (autoclean) [vfat] What I find interesting here is This lsmod listing was captured while using the speakup_spkout (speakout synth). Dunno why sftsyn would be in the loop at all. On Sat, Dec 20, 2003 at 10:22:46AM -0800, David Csercsics wrote: > There > is a binary called say which gets created in the current directory after > you type make. Just copy that to somewhere in your path. If you're going > to use tuxtalk with speakup you will need to make the softsynth device: > mknod /dev/softsynth c 10 26 Then you'll just load the speakup_sftsyn > module and starrt tuxtalk with: say -d You'll lose the console that you > start tuxtalk on as tuxtalk will not go into the backgroup and if you > try say -d & it doesn't work as expected. Also once the module is loaded > be careful unloading it it locked my box up solid yesterday. -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown
