From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: "Speakup List" <speakup@speech.braille.uwo.ca>
Subject: /proc/speakup and keymap problems with Speakup-0.10A
Date: Tue, 26 Jun 2001 23:57:36 +0200 [thread overview]
Message-ID: <000a01c0fe8b$278dd650$0100a8c0@cybertsar> (raw)
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hello, listers!
I am trying to compile Speakup-0.10A from the website against the 2.4.2-2 kernel that comes with Redhat7.1. Yes, this is true that I get several "failed hunks", but the new kernel compiles and installs successfully.
Now, when I boot up, I get speech, but
1. No Speakup keymap is loaded, so I am unable to use any of the Speakup's keystrokes;
2. The entries in the /proc/speakup tree do not return any value nor do they accept any. Therefore, I am also unalbe to change parameters of my synthesizer, which is Doubletalk LT.
Do any of you have an idea of how I can approach the troubleshooting process? I am sure that Bill Acker and other Redhatters went through this already.
I'd appreciate any advice.
Best,
Victor
[-- Attachment #2: Type: text/html, Size: 1422 bytes --]
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000a01c0fe8b$278dd650$0100a8c0@cybertsar' \
--to=tsar@sylaba.poznan.pl \
--cc=speakup@braille.uwo.ca \
--cc=speakup@speech.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).