public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Willie Wong <wwong@math.princeton.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Lenovo USB Keyboard
Date: Wed, 4 Nov 2009 17:38:40 -0500	[thread overview]
Message-ID: <20091104223840.GA29561@princeton.edu> (raw)
In-Reply-To: <4AF004BC.9050402@xunil.at>

On Tue, Nov 03, 2009 at 11:23:56AM +0100, Penguin Lover Stefan G. Weichinger squawked:
> Stefan G. Weichinger schrieb:
> 
> > I still get no output/event for those upper seven keys ... oh my.
> > At least I got a cleaned up xorg.conf for now ;-)
> > 
> > It ain't that important although I would like to see them working, it's
> > a bit hard to understand that issues like this don't just work as well.
> 
> Just to point that out: I am still interested in a solution if anyone ....

I have an Acer multimedia keyboard. I use xbindkeys to set the actions
related to multimedia keys. 

Below is a snip of my .xbindkeysrc

---------------------rc------------------
"amixer sset Headphone 1-"
   m:0x0 + c:174

"amixer sset Headphone 1+"
   m:0x0 + c:176

"amixer sset Headphone toggle"
   m:0x0 + c:160

"mpc stop"
   m:0x0 + c:164

"mpc toggle"
   m:0x0 + c:162

"mpc prev"
   m:0x0 + c:144

"mpc next"
   m:0x0 + c:153

"mpc repeat"
   m:0x4 + c:144

"mpc random"
   m:0x4 + c:153

"xscreensaver-command -lock"
   m:0x0 + c:223

"rxvt -T 'Mutt' -e /usr/bin/mutt"
   m:0x0 + c:236

"/usr/local/bin/crxvt -T 'cMutt' -e /usr/bin/mutt"
   m:0x4 + c:236

"/usr/local/bin/jrxvt -T 'jMutt' -e /usr/bin/mutt"
   m:0x8 + c:236
------------------------------end rc-------------------

As you can see, keycodes 174 annd 176 are volumes up and down, 
160 is the mute button, 164, 162 are stop and play/pause, 144 
and 153 are REW and FF, which I doubled up with meta keys to 
get other features. 223 is the "screen saver" key. And 236 is 
the "e-mail" key. 

I've quite forgotten how I found these keycodes. But some of them 
are quasi standard (I've seen the codes for volume and music player
work on other keyboards, including Dell laptops). 

On my old laptop I used to use a different solution: I think I mapped 
the appropriate keycodes to the XF86VolumeUp and similar keys and then 
mapped those key events using the WM. 

I can try to dig out the old config if you'd like. 

HTH, 

W
-- 
Marten: That's like rule number one of dating-if the lady tells you
    she wants to wait, you wait. Even if it means you get blueballed
    so hard your nuts travel into the future due to relativistic effects. 
Dora: Ah, the Hawking Libido Dilation Effect. Bane of frustrated young
    men and physicists alike.
Sortir en Pantoufles: up 1062 days, 21:17



  reply	other threads:[~2009-11-04 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 16:42 [gentoo-user] Lenovo USB Keyboard Stefan G. Weichinger
2009-10-29 17:28 ` Albert Hopkins
2009-10-29 17:37   ` Stefan G. Weichinger
2009-10-29 18:58     ` Albert Hopkins
2009-10-30  9:21       ` Stefan G. Weichinger
2009-10-30 11:58         ` Albert Hopkins
2009-10-30 18:36           ` Stefan G. Weichinger
2009-11-03 10:23             ` Stefan G. Weichinger
2009-11-04 22:38               ` Willie Wong [this message]
2009-11-05 22:26                 ` Mick
2009-11-06  8:14                   ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091104223840.GA29561@princeton.edu \
    --to=wwong@math.princeton.edu \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox