Re: I sometimes lose 'q' key in profit of 'a' using mac-fr3 keymap...
I have solved the problem !
I used the files from http://www.linux-france.org/article/materiel/mac/clavier_rpm3.html
This is a rpm, I used alien to debianize it.
Beware, to use it, you must compile a kernel with 'new input layer' support
(CONFIG_INPUT_KEYBDEV Yes, CONFIG_INPUT_EVDEV Yes).
I used benh kernel ('rsync -avz penguinppc.org::linux-2.4-benh .')
Keyboard on Titanium PB is an adb keyboard. You must compile with adb
support (CONFIG_ADB Yes, CONFIG_INPUT_ADBHID Yes).
Beware, you must set CONFIG_MAC_ADBKEYCODES to NO in the kernel compile
config,
because the keymap is set to use Linux key codes, not adb.
rem : Switching to linux keycodes dinamically by setting
/proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
doesn't work. (I think it's because the ckeymap is loaded very early in the
boot process)
Then you can copy /usr/lib/kbd/keymaps/mac/azerty/mac-fr-ext_new.kmap.gz to
/etc/console/boottime.kmap.gz.
And it works !!!!
Le mer, 02 mai 2001 10:54:50, Geert Uytterhoeven a écrit :
> On Wed, 2 May 2001, Michael Schmitz wrote:
> > > I had the same problem. If I remember right, the keyboard
> configuration
> > > script loads the keymap from /usr/share/keymaps, then regenerates it
> > > in /etc/console-tools. The problem is that it is regenerated wrong:
> the
> > > setting for the q key is not written. Note the suspicious fact that
> q has
> > > keycode 0. This is clearly a bug in one of the console tools, one
> that
> >
> > keycode 0 is illegal on x86 (you'll find a long flame war on this topic
> in
> > the l-k archives). You could change the kernel to remap keycode 0 to
> some
> > spare keycode, and adjust the keymap to match. Or you could continue
> the
> > 'keycode 0 is a valid keycode on some architectures so please fix
> > console-tools' argument.
> > Seeing how common sense (WRT to making incompatible changes and all)
> often
> > loses, I'd go for the first option.
>
> According to Andriew Brouwer there is a severe security problem with
> using
> keycode 0, since it's reserved to mean something special somewhere in the
> keyboard ioctls.
>
> Note that Amiga still uses keycode 0. It's hard to break backwards
> compatibility here...
>
> Don't know how `keycode 0' is related to the new input subsystem though.
> Perhaps that would solve the whole problem completely.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> P.S. Sorry, can't find Andries mail right now, so you have to ask him
> yourself if you can't find out.
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
> geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker.
> But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
>
>
Reply to: