From: Jacob Schmude <jacobs@ncinter.net>
To: speakup@braille.uwo.ca
Subject: Re: Speakup V0.09 & new kernel 2.2.16...no talkie
Date: Sat, 1 Jul 2000 17:26:03 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0007011724190.878-100000@jscp> (raw)
In-Reply-To: <20000701183614.170.qmail@dalek.dhs.org>
Hi
Add speakup_ser=1 to the kernel command line. This will force
speakup to look on ttyS1. My guess is that it's finding that modem and
attempting to use it as a synth. Of course, no response from the modem, so
no speech.
On Sat, 1 Jul 2000, Buddy Brannan wrote:
> Hey y'all,
>
> Well, because somehow I managed to screw up my previous kernel source tree
> (patching to 2.2.16 and then Speakup, it didn't go very well, but it's
> probably because I forgot I did something--or forgot to do something), I
> downloaded a new complete 2.2.16 tarball, untarred it, patched in Speakup
> V0.09A (Yes, I used the correct patch file), configured it--I lost my
> original old .config, so I started it over--installed it--rebooted--and no
> speech.
>
> I have the Accent SA on /dev/ttyS1 and wonder if it's not detecting there
> for some reason? I have a modem (external, switched on) on /dev/ttyS0...I
> haven't tried booting with the modem switched off. I think I shall try
> this. In any case, how do you force Speakup to use a particular serial
> port--I don't exactly recall.
>
> Thanks.
>
>
> --
> Buddy Brannan, KB5ELV | And if the ground yawned,
> Email: davros@ycardz.com | I'd step to the side and say,
> Phone: (972) 276-6360 | "Hey ground! I'm nobody's lunch!"
> Voice mail: (877) 791-5298 | --Eddie From Ohio
>
> _______________________________________________
> 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: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Buddy Brannan
` Kaare Dehard
` Jacob Schmude [this message]
` Buddy Brannan
` Jacob Schmude
` brent harding
` Gene Collins
` brent harding
` Gene Collins
` Buddy Brannan
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=Pine.LNX.4.21.0007011724190.878-100000@jscp \
--to=jacobs@ncinter.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).