Different keymaps (??) on my ttys

Denys Vlasenko vda.linux at googlemail.com
Thu Nov 15 17:00:03 UTC 2007


On Thursday 15 November 2007 04:20, Alexander Griesser wrote:
> Denys Vlasenko wrote:
> >> The really strange thing is, that I tried to use the ASCII key code
> >> trick (activate Numlock, press ALT + 035, the decimal ASCII code for
> >> '#') and it gets interpreted as Backspace too.
> >
> > Looks like keymap is messed up on tty2,3,4...
>
> Yes.
>
> > I think you need to spend an hout or two learning
> > how exactly your startup scripts initialize ttys.
>
> Well, it took me an hour or two to write them so I know
> exactly what happens and maybe that's the problem, because
> I did always run the `loadkmap` command on tty1 only.

I saw a similar problem with font loading. Loading font once
worked on text-mode VTs, but on framebuffer console based VTs
I needed to do it on each VT. Which makes more sense anyway -
VTs are supposed to be independent devices, right?

> But that always worked and as said above, I can't say for
> sure when it stopped working.

Maybe "shared keymap" misfeature was fixed in the kernel.

> >> How can I generate the binary kmap files needed by loadkmap?
> >
> > I must confess that I am still using non-busyboxed keymap loading
> > (I use kbd-1.12):
>
> Coward ;)
> Is loadkmap broken currently or can anyone tell me how to use it?
>
> How do I create `loadkmap` compatible keymap files?

Sorry can't help there.
--
vda



More information about the busybox mailing list