[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: XFree86 update question


I did my home work, and still get bitten by this keymapping problem.

I added append="keyboard_sends_linux_keycodes=1" in my yaboot.conf, and now
I get the XFree86 to play nice and give me the right keymapping.  The only
trouble is that the keymapping for the console before X starts is now wrong.

I know this since I have netenv installed, and it won't work correctly.
Actually, while booting if I hit keys, I can see that they don't map
correctly as they output to the console.

Same story with virtual consoles after X started. Keymapping is all screwed
up inside them too (so no way to find out what keys under this mapping I
should enter to go back to X.)

It seems that the append="keyboard_sends_linux_keycodes=1" option has fixed
the problem with XF86, it's just that now that the console has a broken
keymapping. Is it one or the other?

I have a kernel-image-2.4.8-powerpc needed for the iBook 2001 because of
aty128fb support (as mentioned earlier with my do-quiesce screen mail)
My other email mentioned a problem both compiling 2.4.8 and 2.4.9 from
kernel-sources so I am kinda stock with the binary image only.

Is the keyboard USB on the new iBook 2001? It looks like it, since the
keymapping isn't broken at boot time until USB gets loaded and replaces OF

If someone can give me a pointer, I would sincerely appreciate.


on 9/12/01 4:05 PM, Ethan Benson at erbenson@alaska.net wrote:

> On Wed, Sep 12, 2001 at 08:31:20PM +0200, Michael Schmitz wrote:
>> On Wed, 12 Sep 2001, Laurent de Segur wrote:
>>> ...and since most people don't read them anyway, expect great chaos on this
>>> list when the sucker is released.
>> That was clear from the beginning. It was predictable the moment the
>> Powers That Be decided to force everyone to switch over to Linux keycodes
>> now, not wait until release. Nothing that creative use of procmail
>> couldn't fix :-)
> look at it this way, the input layer we switched to AFTER release, we
> broke debian stable.  this time were doing it right; in woody before
> its considered stable.
> and people who refuse to rtfm can be ignored and blackholed with
> procmail yes, and they deserve it.
>> Make no mistake: the new input layer is the cleaner of both options, and
>> having a common set of keytables for both ADB and USB keyboards also makes
>> things easier in the long run. Plus we better hash this out now and come
>> up with a few solutions for the transition. I just resent breaking
>> backwards compatibility, that's all.
> there was no way to do this transition magically, the current method
> is as good as it can be, the keymap is corrected and the kernel sysctl
> switched, the user EXPLICITY WARNED that they MUST take action to fix
> thier broken kernel, the action is trivial:
> 1) apt-get install kernel-image-2.2.19-pmac
> 2) add append="keyboard_sends_linux_keycodes=1" to /etc/yaboot.conf
> finally major releases of debian usually do have some sort of breakage
> that requires user intervention, or specific action to deal with, just
> look at the sparc upgrade from slink to potato.  you MUST read the
> release notes, if you don't you deserve what you get: a broken upgrade
> and being killfiled on all the mailing lists.

Reply to: