Keyboard is a Sun Type 6: There is no Type 6, so you specify a Type 5 in XF86Config Here is the relevant portion of XF86Config: Option "XkbRules" "xfree" Option "XkbModel" "sun" Option "XkbLayout" "us" Option "XkbCompat" "compat/complete" Option "XkbTypes" "types/complete" Option "XkbKeycodes" "sun(type5)" Option "XkbGeometry" "sun(type5)" Option "XkbSymbols" "sun/us(sun5)" Option "CoreKeyboard" With xfree-4.2.1.ebuild, The keyboard worked fine. Upgrading to 4.2.1-r1 resulted in some incorrect mappings. Pressing 'l' displayed 'b' in X, and pressing ',' displayed a 'v'. The console mappings are correct. Upgrading to 4.2.1-r2, with the same XF86Config, fixes the mappings
Question for 'the_deuce': Are you in a position to try the 'glxgears' with the working version of 4.2.1-r2 you have? I saw the same keyboard mapping problems, and they were initially present with 4.2.1-r2. But for me, with 4.2.1-r2 glxgears ran as expected once I got it started. And, in 4.2.1-r2, the keyboard mappings seem to be correct now. But glxgears no longer shows gears (it runs and reports performance correctly, though). I am trying to figure out if this is a new xfree-4.2.1-r2 problem, or if in going back and forth between xfree versions, I have mangled something.
I just ran glxgears, and it worked fine (gears and fps displayed). However, I, and others, had a similar problem on the PC with ATI Radeon graphics cards and XFree. glxgears displayed a black box without gears but showed the fps. The problem was that the CLFAGS optimizations were too high when compiling Xfree. However, that was with an older ebuild of xfree. Here is the forum thread: http://forums.gentoo.org/viewtopic.php?t=17087 Here are the flags I used on the Sparc Platform: CFLAGS="-mcpu=v8 -mtune=v9 -O2 -pipe -fomit-fram-pointer" The v8/v9 is because a forum post mentioned problems with v9/v9 when compiling glibc.
Yes, indeed it's the '-mcpu=v9' that did it to me. When this is '-mcpu=v8' the glxgears program runs as expected with the same performance as with xf-4.2.1 (which on this system is 539 FPS). So, the keyboard mappings in 4.2.1-r2 which showed up initially seem to be taken care of. I think, though, when this is re-released for sparc, the ebuild script should take care to insure that '-mcpu=v9' is not left in the CFLAGS (or maybe there should be a general warning until gcc gets fixed? I haven't found the original forum post refered to...)
Added the following to Xfree 4.2.1-r1 and Xfree 4.2.1-r2 # Sparc support ... replace-flags "-mcpu=ultrasparc" "-mcpu=v8" replace-flags "-mcpu=v9" "-mcpu=v8" Then changed the keywords from -sparc to sparc
The l->b bug and ','->v mapping seems to still be an issue in Xfree 4.3-r2 .. I'm using an Ultra 1 with a Type 5 keyboard.
apparently popped up in 4.3.0-r2 as well
Jason, help!
I just tried this on an Ultra 1 with a fresh install of xfree-4.3.0-r2 and the key mappings worked just fine. Evan, could you post your XF86Config to the bug?
Evan, please attach your XF86Config file.
The sun is at work, and I'm on vacation .. however ... I pasted it to the forums .. let me find it from there ... Sun Ultra 1 box, Type 5 keyboard Section "ServerLayout" Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" Option "HandleSpecialKeys" "Always" EndSection Section "Files" RgbPath "/usr/X11R6/lib/X11/rgb" ModulePath "/usr/X11R6/lib/modules" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "extmod" Load "dri" Load "dbe" Load "record" Load "xtrap" Load "glx" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "Keyboard" Option "CoreKeyboard" # Option "XkbKeycodes" "sun(type5)" # Option "XkbTypes" "default" # Option "XkbSymbols" "sun/us(sun5)" # Option "XkbGeometry" "sun" # Option "XkbRules" "xfree86" # Option "XkbModel" "sun" # Option "XkbLayout" "sun/us" Option "XkbRules" "sun" Option "XkbModel" "type5" Option "XkbLayout" "us" EndSection The rest is truncated as it shouldn't matter, and the commented out lines are just different things I was trying to make things work - but only made things worse.
Hi Evan, The only difference between your config and mine is I have a slightly different layout type Option "XkbLayout" "en_US" See if that works for you.
I upgraded to 4.3.0-r2. I now have a type 5c keyboard. These lines, which worked correctly in 4.2.1-r2 Option "XkbRules" "xfree" Option "XkbModel" "sun" Option "XkbLayout" "us" Option "XkbCompat" "compat/complete" Option "XkbTypes" "types/complete" Option "XkbKeycodes" "sun(type5)" Option "XkbGeometry" "sun(type5)" Option "XkbSymbols" "sun/us(sun5)" Option "CoreKeyboard" Result is a shift with someother stuff broken ( w->q e->w ) Next I tried: Option "XkbRules" "sun" Option "XkbModel" "type5" Option "XkbLayout" "us" or Option "XkbLayout" "en_US" Result is l->b and ,->v like in the 4.2.1-r1, but everything else seems to work. With: XkbRules "sun" XkbModel "type5" XkbLayout "us" XkbCompat "compat/complete" XkbTypes "types/complete" XkbKeycodes "sun(type5)" XkbGeometry "sun(type5)" XkbSymbols "sun/us(sun5)" The result was the shift again. (X reports that sun/us can't be found) Then I tried to do a bunch of stuff, but it didn't work. I emerged xkeycaps and that showed pressing the 'l' key as a 'b' and ',' as a 'v', but we already knew that. What was the difference between xfree-4.2.1-r1 and r2? Is that something we could add in here once again?
When you upgraded xfree to 4.3.0-r2, did you merge all the new X config files into their respective directories? Also have you tried removing X and it's config files and then reinstalling? I've been trying to replicate this but to no avail.
From the xfree Changelog: 09 Mar 2003; Seemant Kulleen <seemant@gentoo.org> xfree-4.3.0-r1.ebuild: added a patch for sparc keyboards from the xfree86 mailing list: http://www.mail-archive.com/devel%40xfree86.org/msg01156.html I believe I know what the problem is now. I think it is a simple case of ARCH="sparc64" instead of ARCH="sparc". My ARCH was sparc64, so the patch was not applied. I'm now recompiling xfree, and that will take a while. I'll report back when it finishes.
The keymapping problem is fixed by having ARCH="sparc".
closing -- sparc64 is not even a valid ARCH value I don't believe. if it is, then we need to either fix epatch or sparc team needs to give us some feedback.
Closing
