speakup status was Re: now playing live.

[jwantz at hpcc2.hpcc.noaa.gov]

Hi Janina,
I had the same problem and I cured it by using Kirk's latest keymap 
which you can find in /usr/src/linux/drivers/char/speakup.  It's called 
speakupmap.map.  Gnu zip it and rename it to speakup.kmap.gz.  Then move 
it to /lib/kbd/keymap/i386/qwerty            and loadkeys speakup.  That 
should take care of Redhat at least.

     Jim Wantz
On Mon, 11 Mar 2002, Dawes, Stephen 
wrote:

> Janina,
> I ran into a similar problem with compiling Kernel 2.4.17. With the help of Gene, we determined the problem to be that I was pointing to the wrong keymap. I was having the problem on a Redhat box, which I believe to be the distribution that you use. 
> 
> To fix my problem, I did 2 things.
> 1. comment out the keymap in the keyboard file, I believe the path is /etc/sysconfig/keyboard 
> 2. in the setup program, you just type setup at the command prompt when logged in as root, turn off keytables.
> 
> Hope this helps.
> 
> 
> Steve Dawes
> PH:  (403) 268-5527. 
> Mailto:  sdawes at gov.calgary.ab.ca 
> 
> 
> 
> -----Original Message-----
> From: Janina Sajka [mailto:janina at afb.net]
> Sent: 2002 March 11 7:06 AM
> To: speakup at braille.uwo.ca
> Subject: Re: speakup status was Re: now playing live.
> 
> 
> Hey, Kirk:
> 
> I wonder if the problem I ran into has anything to do with speakup's new 
> changes, or the 2.4.18 kernel?
> 
> Yesterday afternoon I used cvs to patch a freshly downloaded 2.4.18. There 
> were no errors, but when I booted my numeric keypad was very messed up. 
> Screen review was sporadic--and seemed only to work, if it worked at all, 
> with numlock off. When numlock was on, pressing the number keys on the 
> numeric yielded numbers, but it yielded the wrong numbers, e.g. when I 
> pressed 4, I heard 7. These numbers also became part of my command line.
> 
> Needless to say, I left 2.4.18 for my older reliable kernel! <grin>
>  
> On 11 Mar 2002, Kirk Reiser wrote:
> 
> > Speakup newest changes in cvs include numlock support, the caplock
> > beep and I can't remember what else.  I am not planning another
> > official release for awhile.  I want to get the driver interface
> > finished before I do.
> > 
> >   Kirk
> > 
> > 
> 
>