public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* Two keymaps for two kernels
@  Cheryl Homiak
   ` Saqib Shaikh
  0 siblings, 1 reply; 7+ messages in thread
From: Cheryl Homiak @  UTC (permalink / raw)
  To: speakup

My keymap problem seems to have resolved itself; the right keymap seems to
be loading now with each kernel--at least the alt key is working in the
no-speech kernel that I load to use emacspeak alone.  My theory is that
something in one of the debian updates/upgrades fixed the problem.  You
especially might want to try it again, Saqib, if you've been doing regular
"apt-get update" and "apt-get upgrade" for your system.

                              Cheryl



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Two keymaps for two kernels
   Two keymaps for two kernels Cheryl Homiak
@  ` Saqib Shaikh
  0 siblings, 0 replies; 7+ messages in thread
From: Saqib Shaikh @  UTC (permalink / raw)
  To: speakup

thanks, could you please go over how you accomplished this? at the moment i
have /vmlinuz, /vmlinuz.speakup, and /boot/system.map. If I now add
/boot/speakup.map how do i go about telling linux which keymap is for which
kernel etc? thanks, saqib

----- Original Message -----
From: "Cheryl Homiak" <chomiak@worldfront.com>
To: "speakup" <speakup@braille.uwo.ca>
Sent: Saturday, July 07, 2001 6:49 AM
Subject: Two keymaps for two kernels


> My keymap problem seems to have resolved itself; the right keymap seems to
> be loading now with each kernel--at least the alt key is working in the
> no-speech kernel that I load to use emacspeak alone.  My theory is that
> something in one of the debian updates/upgrades fixed the problem.  You
> especially might want to try it again, Saqib, if you've been doing regular
> "apt-get update" and "apt-get upgrade" for your system.
>
>                               Cheryl
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



^ permalink raw reply	[flat|nested] 7+ messages in thread

* two keymaps for two kernels
@  Saqib Shaikh
  0 siblings, 0 replies; 7+ messages in thread
From: Saqib Shaikh @  UTC (permalink / raw)
  To: speakup

[-- Attachment #1: Type: text/plain, Size: 217 bytes --]

hi,
does anyone know how you can use two different keymaps for two kernels? so that i can have a talking kernel with the speakup modified keymap and a nontalking kernel in which the numpad is free?
thanks, saqib


[-- Attachment #2: Type: text/html, Size: 634 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: two keymaps for two kernels
   ` Gregory Nowak
@    ` Cheryl Homiak
  0 siblings, 0 replies; 7+ messages in thread
From: Cheryl Homiak @  UTC (permalink / raw)
  To: speakup

On Mon, 2 Jul 2001, Gregory Nowak wrote:

> Hi,
>
> I think that the easiest thing to do
> would be to simply compile
> the nontalking kernel from
> a fresh source tree without speakup patched

In this case, at least in debian, that doesn't matter; we seem to be stuck
with whichever keymap was installed, be it speakup or another kernel.  I'm
sure there is a way around this, and will let somebody know if I find it
first.  I don't know what Saquib did but I did compile from a fresh kernel
tree without speaqkup compiled in.                              Cheryl



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: two keymaps for two kernels
   Saqib Shaikh
   ` Cheryl Homiak
@  ` Gregory Nowak
     ` Cheryl Homiak
  1 sibling, 1 reply; 7+ messages in thread
From: Gregory Nowak @  UTC (permalink / raw)
  To: speakup

Hi,

I think that the easiest thing to do
would be to simply compile
the nontalking kernel from
a fresh source tree without speakup patched in.
Greg


On Mon, Jul 02, 2001 at 05:06:19PM +0100, Saqib Shaikh wrote:
> hi all,
> 
> i use two kernels for emacspeak and for speakup. now, i think that when i use the standard nontalking kernel i am stuck with the speakup keymap. how can i use a standard keymap for the normal kernel and a speakup.map for the talking kernel?
> 
> thanks, saqib
> 


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: two keymaps for two kernels
   Saqib Shaikh
@  ` Cheryl Homiak
   ` Gregory Nowak
  1 sibling, 0 replies; 7+ messages in thread
From: Cheryl Homiak @  UTC (permalink / raw)
  To: speakup

This seems to be the same problem I am having.  If you are using debian,
it appears that the way console-common and console-tools now function is
causing this problem.  If you don't get an answer here, you might try
taking it to a debian list.  I actually did succeed in loading a keymap to
use with just emacspeak, but of course when I rebooted into my
speakup-using kernel the emacspeak-using kernel keymap loaded and I had to
find a speakup keymap to reload.  It seems to me that in the past the
keymap was loaded for whatever kernel you booted but now that has changed.

                              Cheryl



^ permalink raw reply	[flat|nested] 7+ messages in thread

* two keymaps for two kernels
@  Saqib Shaikh
   ` Cheryl Homiak
   ` Gregory Nowak
  0 siblings, 2 replies; 7+ messages in thread
From: Saqib Shaikh @  UTC (permalink / raw)
  To: speakup

[-- Attachment #1: Type: text/plain, Size: 272 bytes --]

hi all,

i use two kernels for emacspeak and for speakup. now, i think that when i use the standard nontalking kernel i am stuck with the speakup keymap. how can i use a standard keymap for the normal kernel and a speakup.map for the talking kernel?

thanks, saqib


[-- Attachment #2: Type: text/html, Size: 785 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 Two keymaps for two kernels Cheryl Homiak
 ` Saqib Shaikh
  -- strict thread matches above, loose matches on Subject: below --
 two " Saqib Shaikh
 Saqib Shaikh
 ` Cheryl Homiak
 ` Gregory Nowak
   ` Cheryl Homiak

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).