Date: Tue, 8 Mar 2005 19:33:18 -0500 From: "Michael G. Jung" <mikej@confluenttech.com> To: "Dejan Lesjak" <dejan.lesjak@ijs.si> Cc: freebsd-sparc64@freebsd.org Subject: RE: Problems with X.. Message-ID: <9D7F0DF3FB16D41184010050DA90E00001C874CE@neo.confluentasp.local>
next in thread | raw e-mail | index | archive | help
-----Original Message----- From: Dejan Lesjak [mailto:dejan.lesjak@ijs.si] Sent: Tue 3/8/2005 6:31 PM To: Michael G. Jung Cc: freebsd-sparc64@freebsd.org; mmuthmann@gmx.net Subject: Re: Problems with X.. Dejan: On Wednesday 09 of March 2005 00:20, Michael G. Jung wrote: > Here is the entire log --- sorry if confusion about US / non-US > [snip] > (**) |-->Input Device "Keyboard0" > (**) Option "XkbRules" "xorg" > (**) XKB: rules: "xorg" > (**) Option "XkbModel" "pc104" > (**) XKB: model: "pc104" > (**) Option "XkbLayout" "us" > (**) XKB: layout: "us" [snip] > (==) Keyboard: CustomKeycode disabled > (**) Option "CoreKeyboard" > (**) Keyboard0: Core Keyboard > (**) Option "Protocol" "standard" > (**) Keyboard0: Protocol: standard > (**) Option "AutoRepeat" "500 30" > (**) Keyboard0: XkbRules: "xorg" > (**) Option "XkbModel" "pc104" > (**) Keyboard0: XkbModel: "pc104" > (**) Option "XkbLayout" "us" > (**) Keyboard0: XkbLayout: "us" > (**) Option "CustomKeycodes" "off" > (**) Keyboard0: CustomKeycodes disabled > (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) > (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) Mmmm, interesting... so you are using pc104 as keyboard model as opposed to type5 which IIRC Matthias Muthmann is using (and which is the one I would pick up FWIW, it seems a logic choice). Was the config file (xorg.conf.new) obtained via 'X -configure'? If this works, then we should probably document somewhere that pc104 is to be used for sparc keyboards... Anyway I'm glad this works and thanks for the testing :) Ok, let me clarify - I put in the config file ( it was probed without these values ) Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" in the configuration generated from X -configure during my bouts trying to get X working. (some weeks ago)..... I just re-ran "X -configure" and only modified my mouse for serial use... it probed keyboard type pc101 - which works also... Here is the bit of X.log I think you would be interested in - this is from "X -configure" with your single patch as of this evening. (**) Keyboard0: Core Keyboard (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc101" (**) Keyboard0: XkbModel: "pc101" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) the keyboard section created from "X -configure" now is Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection ------------------------------------------------------------------- I do have one strange behaviour I've noticed in K - this may be a K issue.... In KWord shift of 0-9 displays drop-down-menus.... Hmmmmm.... Shift 0-9 keys work fine in xterm and vi and display ~!@#$%.... etc. as expected. Here is some more xev sequences using keyboard "pc101" layout "us" note that 0-9, a-z, A-Z, PG/UP, keypad shifted and unshifted seem ok, function key F1 still brings up KHELP.......... This is the output for SHIFT-1 above the letter Q KeyPress event, serial 23, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 907418, (53,34), root:(549,54), state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: KeyPress event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 908178, (53,34), root:(549,54), state 0x11, keycode 10 (keysym 0x21, exclam), same_screen YES, XLookupString gives 1 bytes: (21) "!" KeyRelease event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 908322, (53,34), root:(549,54), state 0x11, keycode 10 (keysym 0x21, exclam), same_screen YES, XLookupString gives 1 bytes: (21) "!" KeyRelease event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 908734, (53,34), root:(549,54), state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: This is the output for SHIFT-2 above the letter W KeyPress event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 919331, (53,34), root:(549,54), state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: KeyPress event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 920043, (53,34), root:(549,54), state 0x11, keycode 11 (keysym 0x40, at), same_screen YES, XLookupString gives 1 bytes: (40) "@" KeyRelease event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 920147, (53,34), root:(549,54), state 0x11, keycode 11 (keysym 0x40, at), same_screen YES, XLookupString gives 1 bytes: (40) "@" KeyRelease event, serial 26, synthetic NO, window 0x1000001, root 0x34, subw 0x1000002, time 920345, (53,34), root:(549,54), state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: Do these scan codes look correct? Thanks again!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D7F0DF3FB16D41184010050DA90E00001C874CE>