From: "Kerry Hoath" <kerry@gotss.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: another attempt to use speakup
Date: Fri, 16 Jan 2009 15:47:37 +0900 [thread overview]
Message-ID: <6ACDBC948D1847568E54C1F732EF59F7@bouncy> (raw)
In-Reply-To: <2B1302BADE8243EF999ED915FA61E556@paperweight>
I seem to recall in newer speakup that you separate speakup and synth with a
period
speakup.synth=dectlk
reguarding your building of modules under ubuntu 8.10;
there is nothing running on that port that might upset the dectalk?
Note that speakup will not function inside x, you will need to switch to a
text console with whatever the key sequence is for this.
left control, left alt f1 seems to spring to mind.
Speakup talked when the system was going down because X windows exited and
messages were coming up on the text console.
Speakup will not talk in gnome terminal, x-terminal or anything that is GUI
or when the screen is in graphics mode.
It talks at a text login prompt, and in applications run on a text console.
Sorry if you allready knew all this but perhaps that helps a bit.
Just because you modprobe speakup in a gnome terminal does not mean the
machine will start talking until you switch to a text console.
If I modprobe speakup modules over a telnet session; the box in question
won't talk till I hit keys on its keyboard in the text console.
Regards, Kerry.
----- Original Message -----
From: "Bruce Noblick" <brunobrook@columbus.rr.com>
To: "speakup info" <speakup@braille.uwo.ca>
Sent: Friday, January 16, 2009 2:59 PM
Subject: another attempt to use speakup
> Hello all,
>
> I have pulled much of what I have done here from threads on this list but
> then I took a few leaps of faith on my own to get to a goal that has only
> very recently come into focus. I will now explain.
>
> I started with Ubuntu 8.04 and just recently upgraded to 8.10.
> Then I opened a shell session with gnome-terminal.
> Then I tried a variant on Kerry's instructions to get speakup working. I
> built speakup as suggested, successfully. Since I am using a DECTalk, I
> skipped the espeakup and did the modprobe and specified speakup_dectlk
> instead of speakup_soft.
> It told me that it worked.
> But then it was silent until I shut the computer down.
> Then it talked while the computer was going down.
> I had hoped that it would come up talking , even if only up to the login
> prompt, But it didn't.
> Then I connected using ssh and had similar results when I did the modprobe
> command.
> Then I saw the thread from just a few days ago about grml. I downloaded
> and created the CD, found and read over the cheat sheet and attempted to
> boot with it and specified grml speakup_synth=dectlk.
> I couldn't get that to work.
> All I am trying to do now is get something to work with speakup.
> I like the idea of a live CD That would allow me to get the best of the
> command line interface when I want it while allowing me to have the gnome
> environment.
> I feel like I am close to it but I am apparently missing one or more
> steps.
> Any thoughts are welcome.
>
> Thanks!
>
> Bruce Noblick
>
>
>
> _______________________________________________
> 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: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Bruce Noblick
` Kerry Hoath [this message]
` Janina Sajka
` Christopher Moore
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=6ACDBC948D1847568E54C1F732EF59F7@bouncy \
--to=kerry@gotss.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).