On Fri, Sep 25, 2009 at 1:11 PM, Keith Lofstrom <[email protected]> wrote: > On Fri, Sep 25, 2009 at 12:41:12AM -0700, Larry Williams wrote: >> Has anyone been able to get all the keys on a multimedia keyboard to produce >> scancodes or events? I have an HP 5187-7583 with five destination keys >> (search, HP club, Internet, Info, Email), two eject buttons, a Burn CD/DVD >> button, multimedia controls and volume controls. Three of the destination >> keys don't produce a scancode or keycode, neither do the eject or burn >> keys. I've used xev and showkey, and it's as if I'm not pressing a button. > > You may also want to try a couple of Javascript event handlers: > > http://unixpapa.com/js/testkey.html > http://sawmac.com/missing/javascript/tutorials/examples/chapter06/events.html > > I suspect Tony is right, you will need to fiddle with the BIOS to see > those events show up, but those webpages are another way to look at them. > > Myself, I'm looking for something that will log keyboard/mouse events > with timecodes to a file, so I can evaluate various USB devices that > pretend to be keyboards. Some of these devices emit out long strings > of characters. Perhaps someone can suggest a tool that would help > both of us, or I should hack on showkey to make what I want. > > Keith > > -- > Keith Lofstrom [email protected] Voice (503)-520-1993 > KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon" > Design Contracting in Bipolar and CMOS - Analog, Digital, and Scan ICs > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug >
A little more research shows a lot of chatter about this on the nets. (keys: multimedia keys dead evdev) It seems to be related to X and the evdev driver, which started being used for keyboards along and about Hardy, I think. Much of the chatter reports the behavior as a bug, but a lot of the bugs say 'closed', assuming or indicating that newer releases fixed the problem. You might check your xorg.conf for the keyboard entry. If it says the driver is 'evdev', you might try changing it to 'kbd', which was one of the simpler suggestions floating around. - tony _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
