From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4
Date: Fri, 10 Nov 2006 23:08:44 -0700 [thread overview]
Message-ID: <20061111060844.GA2350@localhost.localdomain> (raw)
In-Reply-To: <20061111052339.GA7962@lava-net.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'd guess your problem is either with echo none
>/proc/speakup/synth_name, with modprobe -r, or with both. I know I've
reported problems here in the past about the kernel going bye-bye when
echoing none to synth_name, and when modprobing speakup
modules. Others have reported modprobe issues here as well, so your
report isn't the first, it just serves to confirm that a problem does
in fact exist in certain configurations, but not in others, as I've
also mentioned in the past.
As for why you don't get speech, I would have to guess you don't have
software speech configured properly, or are again loading speakup
modules before starting speech-dispatcher/speechd-up, causing things
to act strange.
Greg
On Sat, Nov 11, 2006 at 12:23:39AM -0500, Igor Gueths wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi all. I just completed installing LFS on my laptop; this includes Gcc-4.1.1, and Glibc-2.5. I restored a known good configuration from backup that was working perfectly on my previous
> Slackware system, which was running Linux-2.6.17.1. I have noticed two things so far; for one thing, I can't hear anything when I start Speech-dispatcher and Speechd-up with Espeak-1.16. Also,
> for some reason when I go to stop Dispatcher and Speechd-up, Speechd-up doesn't terminate properly. When I killall speechd-up, I get the following:
- --
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.5 (GNU/Linux)
iD8DBQFFVWjs7s9z/XlyUyARAoLRAKDablOmniJbkxXr7ioQl2ccw57rxwCgnHIW
BJnAi8w/1rosmMT0+9bv7Z8=
=RTKs
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Gregory Nowak [this message]
` Igor Gueths
` Gregory Nowak
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=20061111060844.GA2350@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).