Date: Wed, 9 Mar 2005 22:33:15 -0500 (EST) From: Aaron Dudek <adudek@sprint.net> To: Dejan Lesjak <dejan.lesjak@ijs.si> Cc: freebsd-sparc64@freebsd.org Subject: Re: Problems with X.. Message-ID: <Pine.GSO.4.61.0503092227010.2693@raistlin.sprintlink.net>
next in thread | raw e-mail | index | archive | help
> > 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 > > > > ------------------------------------------------------------------- > > Indeed it uses pc101 model. I kind of assumed it would use sun type5 model, > and didn't even consider suggesting using one of pc models, go figure :) > > > > > 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.... > > Judging by what you get from xev, this would be K related. Any special > settings in kcontrol (Regional & Accesibility -> Keyboard Layout)? > > > 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? > > Yes, these are expected cedes from those keys. I don't know why K remaps them > or something though. > > > Thanks again! > > No no no, Thank you! By now I would probably be recreating keymaps on sun > keyboards from scratch if you haven't pointed out the model that gets used by > default on sparc keyboards on FreeBSD :) > > > Dejan I have also ran into success with patch-bsd_KbdMap.c.2 and using the PC104 keyboard. Initial testing looks good. Now my only issue is trying to increase the screen resolution as nothing I put into the xorg.conf file seems to work, but at least the keyboard works:) Section "Monitor" #DisplaySize 390 290 # mm Identifier "Monitor0" VendorName "SUN" ModelName "567" HorizSync 31.5 - 100.0 VertRefresh 40.0 - 150.0 Option "DPMS" Modeline "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync EndSection Section "Monitor" #DisplaySize 390 290 # mm Identifier "Monitor0" VendorName "SUN" ModelName "567" HorizSync 31.5 - 100.0 VertRefresh 40.0 - 150.0 Option "DPMS" Modeline "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync EndSection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.61.0503092227010.2693>