Re: XFree86 update question
Adam C Powell IV wrote:
>
> This is all a lot less important given this morning's events, but it is
> nice to have X working so I can use a graphival browser, etc. Thanks
> Michel!
You're welcome, and you're right that this is relatively unimportant. Let me
express my deepest shock and sympathy.
> Michel Dänzer wrote:
>
> >On Tue, 2001-09-11 at 00:08, Adam C Powell IV wrote:
> >
> >[ broken keymap with XFree86 4.1.0 ]
> >
> >> I tried both "macintosh" and "pc101" in dpkg-reconfigure
> >>xserver-xfree86, both of which should give the correct mappings for the
> >>new input layer (which I've been using since it first arrived in
> >>kernel-image-2.2.18pre21-pmac), right?
> >
> >"macintosh" should for a Mac keyboard, the "pcxxx" XkbModels are for PC
> >keyboards.
> >
> Right, but macintosh and pc101 caused exactly the same pattern of
> breakage, just about the same mappings ("`1234" -> "merty") as far as I
> could tell.
The maps are basically the same except for some special keys.
> >>Ethan Benson wrote:
> >>
> >>>switch the kernel to use linux keycodes.
> >>>
> >>Done that (long since).
> >>
> >Are you sure? /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
> >doesn't exist or contains 1?
> >
> As we say in New York, "Akhaa!" The file exists and contains zero.
> Replacing it with one solved the problem.
>
> But wait, didn't we all switch to Linux keycodes way back in December
> when 2.2.18pre21 hit potato?
No, we switched to the new input layer. ADB keyodes were still the default up
to the current 2.2.19 kernel image.
> We had to use Linux keycodes for button emulation, shouldn't that have meant
> that we were using Linux keycodes?
No, mouse button emulation always takes Linux keycodes.
> And is it not a bug that with zero in that /proc entry, the kernel uses
> two different keymaps for the two functions (button emulation and normal
> keyboard use)?
I guess it makes sense not to bloat the mouse emulation by having to deal with
several sets of keycodes.
> Not that this means anything, nor that I'm any expert, but if I was this
> confused, how about a newbie?
All the more reason to switch to Linux keycodes completely IMHO.
> Should there be some kind of auto-detection of HID and
> keyboard_sends_linux_keycodes in the .config and/or .postinst of the
> xserver, to detect and advise or correct such a situation?
Not a bad idea, Branden?
> Or are we all comfortable with just letting lots of users
> get frustrated and confused, as with last December's change?
Of course not.
The bottom line is: This won't be a problem for fresh woody installs as they
will use Linux keycodes from the start. The tricky part is to make upgrades as
smooth as possible, the big chunk of which has been done in console-data.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
Reply to: