[vox-tech] Help: my c and e keys don't work anymore.

[Bryan Richter]

On Sat, Jul 17, 2004 at 02:54:11PM -0700, Peter Jay Salzman wrote:
> 
> On Sat 17 Jul 04, 10:37 AM, Henry House
> > På lördag, 17 juli 2004, skrev Peter Jay Salzman:
> > > 
> > >    KeyRelease event, serial 25, synthetic NO, window 0xc00001,
> > >        root 0x58, subw 0xc00002, time 368034, (45,50), root:(49,408),
> > >        state 0x0, keycode 26 (keysym 0x0, NoSymbol), same_screen YES,
> > >        XLookupString gives 0 bytes:  ""
> > > 
> > >    KeyPress event, serial 25, synthetic NO, window 0xc00001,
> > >        root 0x58, subw 0xc00002, time 368342, (45,50), root:(49,408),
> > >        state 0x0, keycode 27 (keysym 0x72, r), same_screen YES,
> > >        XLookupString gives 1 bytes:  "r"
> > 
> > It looks like your keysyms are bogus. Here is what the the C and E keys yield
> > on one of my systems (Debian stable i386):
> > 
> > KeyRelease event, serial 22, synthetic NO, window 0x800001,^M
> >     root 0x2e, subw 0x0, time 3458574946, (128,73), root:(868,101),^M
> >     state 0x0, keycode 54 (keysym 0x63, c), same_screen YES,^M
> >     XLookupString gives 1 characters:  "c"^M
> > ^M  
> > KeyRelease event, serial 22, synthetic NO, window 0x800001,^M
> >     root 0x2e, subw 0x0, time 3458575046, (128,73), root:(868,101),^M
> >     state 0x0, keycode 26 (keysym 0x65, e), same_screen YES,^M
> >     XLookupString gives 1 characters:  "e"^M
> > ^M  
> > 

Pete, you're at least getting the same keycodes. That confirms that your
hardware is ok. :) 

>    The XKEYBOARD keymap compiler (xkbcomp) reports:
>    > Error:            No Symbols named "microsoft" in the include file
>    > "pc/us"
>    >                   Exiting
>    >                   Abandoning symbols file "default"
>    Errors from xkbcomp are not fatal to the X server
> 
> The keyboard stanza of my XF86Config file is:
> 
>    Section "InputDevice"
>       Identifier  "Generic Keyboard"
>       Driver      "keyboard"
>       Option      "CoreKeyboard"
>       Option      "XkbRules"   "xfree86"
>       Option      "XkbModel"   "pc104"
>       Option      "XkbLayout"  "us"
>       Option      "XkbVariant" "microsoft"
>    EndSection
> 

Try taking out the XkbVariant line? What does that do for you, anyway?
If you have a microsoft natural keyboard, I would think you'd be better off
specifying it in the XkbModel line. This would give you

Section "InputDevice"
    Identifier  "Microsoft Natural"
    Driver      "keyboard"
    Option      "CoreKeyboard"
    Option      "XkbRules"   "xfree86"
    Option      "XkbModel"   "microsoft"
    Option      "XkbLayout"  "us"
EndSection

(change server layout to reflect identifier name change, if you choose
to change it like I did. :) )

-Bryan