l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
August 5: Social gathering
Next Installfest:
TBD
Latest News:
Jul. 4: July, August and September: Security, Photography and Programming for Kids
Page last updated:
2004 Aug 29 15:56

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Help: my c and e keys don't work anymore.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.