From: Kenny Hitt <kenny@hittsjunk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup and serial synthesizers
Date: Mon, 9 May 2005 22:49:34 -0500 [thread overview]
Message-ID: <20050510034934.GA24696@blackbox> (raw)
In-Reply-To: <20050510024233.GZ21903@saidin.asmodean.net>
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Raul A. Gallegos
` Kenny Hitt [this message]
` David Csercsics
` Alex Snow
` Raul A. Gallegos
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=20050510034934.GA24696@blackbox \
--to=kenny@hittsjunk.net \
--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).