From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: running speakup and software synth
Date: Fri, 10 Aug 2007 11:22:10 -0700 [thread overview]
Message-ID: <20070810182210.GA22777@localhost.localdomain> (raw)
In-Reply-To: <20070810162916.GD22729@hittsjunk.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kenny, or anyone else in the know, do you know of a reliable way to
test the whole speech-dispatcher/speechd-up setup before booting into
the new system? When playing with installing debian via
grml-debootstrap, I found the biggest uncertainty was if the software
speech in the new system works or not. As I found out after rebooting,
software speech didn't work, there was no data in the logs, and nobody
to read the screen for me, so that was the end of that
experiment. Yes, I did have a speakup-patched kernel installed, and
the system did boot, according to the other logs in /var/log of the
new system.
So, if one does an install of debian via debootstrap, is there a way
to test software speech in the chrooted system, before you actually
boot into it?
Greg
On Fri, Aug 10, 2007 at 11:29:16AM -0500, Kenny Hitt wrote:
> Hi.
>
> Do you get speech when you type
>
> spd-say "hello world"
>
> If so, then speech-dispatcher is working. If not, edit speech-dispatcher's config files until the spd-say command works.
> Once you have speech-dispatcher working, just
> sudo modprobe speakup_sftsyn
>
> Speakup will start talking.
> If you want speakup to load autimatically on boot, add the line
> speakup_sftsyn
>
> to /etc/modules.
>
> Be aware, you will have to press print screen everytime you boot and log into Gnome since speakup will try to read
> your X console. Since the print screen gets passed to Gnome, you will have to cancel the dialog.
>
> Kenny
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
- --
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.6 (GNU/Linux)
iD8DBQFGvKzS7s9z/XlyUyARAvCPAJ9D4C8TphxYgYcq/D+PkMV5yHWPYgCfaPBv
uHSWkbUTsFFyUQvHI5T6L9M=
=tcY/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
Cody Hurst
` Littlefield, Tyler
` Cody Hurst
` Gregory Nowak
` Cody Hurst
` Kenny Hitt
` Littlefield, Tyler
` John Heim
` Willem van der Walt
` Littlefield, Tyler
` Willem van der Walt
` Christopher Moore
` Kenny Hitt
` Cody Hurst
` Kenny Hitt
` Gregory Nowak [this message]
` Cody Hurst
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=20070810182210.GA22777@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).