speakup and serial synthesizers

speakup and serial synthesizers

[Raul A. Gallegos]

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

Is there a problem with the following or is this by design?

I have on my FC3 box, speakup and the Speak-out synthesizer on ttyS0.  I 
needed to use the speak-out on another box so I unplugged it from the 
box.  When I plugged it back in I get no speech when pressing enter on 
the keyboard.

I can log in and log out and remotely use the box so I know it's not 
locked up.  I thought my cord went bad so I tried it on another box and 
it worked fine.  I also did:

root# echo spkout > /proc/speakup/synth_name

Just in case I needed to re-echo the value but that did not work either.  
So my question is if the serial port somehow shuts off when the 
synthesizer is not connected?  If so, how would I turn it back on?  I'd 
like to do all this without having to reboot.

Thanks.

- -- 
Always borrow money from a pessimist; he doesn't expect to be paid back.
- -- Raul A. Gallegos - http://www.Asmodean.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCgB+Zqqqqyw8Or2IRAuYGAJ9OSPAGro7Gklgh/MAfMBhtqP7NFgCffLq4
PdaJjHMMbVgNyBNDt/rIHVY=
=cLUV
-----END PGP SIGNATURE-----

Re: speakup and serial synthesizers

[Kenny Hitt]

Hi.

Have you tried using modprobe -r to remove the speakup modules and then
modprobe to reload them?

I've found it best to change the default synth to none before
disconnecting a serial synth in speakup 2.0.

I have never been able to successfuly disconnect and reconnect a serial
synth like you could with speakup 1.5.

Hope this helps.
          Kenny
	  
On Mon, May 09, 2005 at 08:42:33PM -0600, Raul A. Gallegos wrote:
> Is there a problem with the following or is this by design?
> 
> I have on my FC3 box, speakup and the Speak-out synthesizer on ttyS0.  I 
> needed to use the speak-out on another box so I unplugged it from the 
> box.  When I plugged it back in I get no speech when pressing enter on 
> the keyboard.
> 
> I can log in and log out and remotely use the box so I know it's not 
> locked up.  I thought my cord went bad so I tried it on another box and 
> it worked fine.  I also did:
> 
> root# echo spkout > /proc/speakup/synth_name
> 
> Just in case I needed to re-echo the value but that did not work either.  
> So my question is if the serial port somehow shuts off when the 
> synthesizer is not connected?  If so, how would I turn it back on?  I'd 
> like to do all this without having to reboot.
> 
> Thanks.
> 
> -- 
> Always borrow money from a pessimist; he doesn't expect to be paid back.
> -- Raul A. Gallegos - http://www.Asmodean.net
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: speakup and serial synthesizers

[David Csercsics]

You scribbled:
>I've found it best to change the default synth to none before
>disconnecting a serial synth in speakup 2.0.
>
>I have never been able to successfuly disconnect and reconnect a serial
>synth like you could with speakup 1.5.
>

It works for me. All I do is hit the key to kill Speakup and take the
synth out and then I come back, plug the synth in and hit that key again
and it always tells me that it's alive. I have Speakup built into the
kernel usually though so that could make a difference.

Re: speakup and serial synthesizers

[Alex Snow]

[-- Attachment #1: msg.pgp --]
[-- Type: text/plain, Size: 1395 bytes --]

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

I see the same behavior with speakup 2.0. I can just disconnect my 
synth and reconnect it and it works. I don't even have to kill speakup 
before disconnecting it but sometimes I have to hit that key one or 
two times after I reconnect.
On Mon, May 09, 2005 at 10:35:49PM -0700, 
David Csercsics wrote:
> You scribbled:
> >I've found it best to change the default synth to none before
> >disconnecting a serial synth in speakup 2.0.
> >
> >I have never been able to successfuly disconnect and reconnect a serial
> >synth like you could with speakup 1.5.
> >
> 
> It works for me. All I do is hit the key to kill Speakup and take the
> synth out and then I come back, plug the synth in and hit that key again
> and it always tells me that it's alive. I have Speakup built into the
> kernel usually though so that could make a difference.
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
"Who is General Failure and why is he reading my hard disk?"
Microsoft spel chekar vor sail, worgs grate !!
	-- Felix von Leitner, leitner@inf.fu-berlin.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCgSgV9XVrM3ri110RAiO6AJ9zYZ5br+Zbf75/pL2a9SRwxZlGUACfR/ko
Mm1HCjxqkI0xPECKL8JWD9s=
=yXM/
-----END PGP SIGNATURE-----

Re: speakup and serial synthesizers

[Raul A. Gallegos]

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

Kenny Hitt said the following on Mon, May 09, 2005 at 10:49:34PM -0500:
> Have you tried using modprobe -r to remove the speakup modules and then
> modprobe to reload them?


I just did and it worked.  Thanks.

> I've found it best to change the default synth to none before
> disconnecting a serial synth in speakup 2.0.


I just tried this and it did not work.


- -- 
There is no sadder sight than a young pessimist.
- -- Raul A. Gallegos - http://www.Asmodean.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCgM60qqqqyw8Or2IRAi+nAJsEdiK5K9MxdZfogzjZodg0CXlLIQCdHBUQ
tQ+6yzDDpDEQA47KnEZkbuE=
=+MvD
-----END PGP SIGNATURE-----