Keymap problem maybe?

Keymap problem maybe?

[Cheryl Homiak]

When I originally compiled my 2.4.5 kernel with speakup patched in using
cvs, I chose my synthesizer in make config and also chose "y" for the
speakup keymap as default.  My keyboard worked fine, nothing unusual.
However, when my console-tools package was upgraded, I got the message
"looking for keymap to install: none".  I wondered about that but didn't
do anything about it since the keyboard was working.  However, I have now
also done a 2.4.5 kernel without speakup, for using emacspeak by itself,
for experimenting with festival, etc.  When I booted with this new kernel,
I immediately discovered that my "alt" key isn't working correctly.  This
is evidenced by the fact that I have to use escape instead of alt in
emacspeak to enter a command.  Also I don't appear to be able to change
consoles with alt-function keys.  Do I have to somehow install another
keymap?  And do I have to do something more about the speakup keymap,
since console-tools isn't finding any keymap?  I also had speakup and
non-speakup versions of 2.2.19 kernel and never had this problem before.

                              Cheryl

Re: Keymap problem maybe?

[Frank Carmickle]

On Thu, 28 Jun 2001, Cheryl Homiak wrote:

> When I originally compiled my 2.4.5 kernel with speakup patched in using
> cvs, I chose my synthesizer in make config and also chose "y" for the
> speakup keymap as default.  My keyboard worked fine, nothing unusual.
> However, when my console-tools package was upgraded, I got the message
> "looking for keymap to install: none".  I wondered about that but didn't
> do anything about it since the keyboard was working.  However, I have now
> also done a 2.4.5 kernel without speakup, for using emacspeak by itself,
> for experimenting with festival, etc.  When I booted with this new kernel,
> I immediately discovered that my "alt" key isn't working correctly.  This
> is evidenced by the fact that I have to use escape instead of alt in
> emacspeak to enter a command.  Also I don't appear to be able to change
> consoles with alt-function keys.  Do I have to somehow install another
> keymap?  And do I have to do something more about the speakup keymap,
> since console-tools isn't finding any keymap?  I also had speakup and
> non-speakup versions of 2.2.19 kernel and never had this problem before.
 
Ok!  Well you had us all boggled until I carefully read your message
again!  If you make clean and recompile you should get a happy alt
key.  What happened was that speakup's keymap was undefined but no code
changed so the make process thought that the default keymap was up to
date.  So make clean and then rock&roll with the compile.

-- 
     Frank Carmickle
phone:     412 761-9568
email:     frankiec@dryrose.com

Re: Keymap problem maybe?

[Cheryl Homiak]

On Fri, 29 Jun 2001, Frank Carmickle wrote:
  If you make clean and recompile you should get a happy alt
> key.  What happened was that speakup's keymap was undefined but no code
> changed so the make process thought that the default keymap was up to
> date.  So make clean and then rock&roll with the compile.


I'm going to try your suggestion, but this doesn't totally make sense to
me.  For one thing, console-tools wasn't finding a keymap before I did a
recompile so do I have to do make clean and recompile the speakup kernel
code too?  Also, I didn't do the no-speech kernel from the same tree as
the speakup kernel.  I re-unpacked the 2.4.5.tar.gz file and did my
no-speech compile from that, and I re-linked the new source tree with
/usr/src/linux before compiling and made sure it was in no way linked with
the original source I had done with speakup compiled in.  Will let you
know if the process you suggested helps, but I'm puzzled as to why it
should be necessary.

                              Cheryl

Re: Keymap problem maybe?

[Frank Carmickle]

Cheryl!

Oh boy!  Now you've really got me stumped.  I thought we were talking
about the same tree.  OK!  I am completely unsure of what the console-tools
packages is trying to do or is doing.  You may have a speakupmap loading
which could cause this behavior with the alt key.  To be honest I don't
think your going to figure this out with out a little trial and
error.  What you need to do is find a regular usmap and invoke it with
loadkeys.  Finding a regular usmap may prove to be an interesting task on
your system.  Tommy currently has the standard usmap being the
speakupmap.  I hope that in future releases we can have a separate
speakupmap.  That would make this a bunch less confusing.  You need to be
really careful with this keymap stuff or you could really hose your
machine pretty good.  So I say start by backing up the keymap that's being
loaded.  Unfortunately this isn't the easiest thing in the world to figure
out.  If you have a look at /etc/init.d/keymap.sh you may be able to get
an idea for what is happening.  Unfortunately I don't have a system here
that is loading a keymap.  /etc/init.d/keymap.sh in my case actually does
a dumpkeys from the kernel for some odd reason.  Oh but yes this might
actually be a good thing to try!  When you have the nonspeakup kernel
running do a 'dumpkeys >nonspeakupmap.map'.  Probably just keeping this
file in roots homedir /root isn't a bad place for it.  Then do a 'loadkeys
<nonspeakupmap.map'.  If you don't get a working alt key at that point
then I would be extremely surprised!  

Now how to fix this long term I am unsure at this point.  Let's just see
if this works to start with.

HTH

-- 
     Frank Carmickle
phone:     412 761-9568
email:     frankiec@dryrose.com