FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 10-29-2009, 03:42 PM
"Stefan G. Weichinger"
 
Default Lenovo USB Keyboard

Got myself a Lenovo keyboard ...

a "ThinkPlus Enhanced Performance USB Keyboard"

wow, it looked much better online than it feels now ... *sigh*

I want to use that keyboard with Gnome (2.26 right now).

I googled how to use the multimedia-keys already, seems as if I have to
face some serious key-logging and hacking around to get those working
(no, nothing usable on that funny CD).

Some of them work (volume, internet-keys to the left), only the 7 keys
on top miss. I don't actually NEED them, but as I PAID them .... you
know ... ;-)

--

Just before I start hacking myself, I want to ask you if maybe someone
has already gone through this and is willing to share ...?

Sorry if I sound lazy, actually I am already getting a bit tired of
hacking stuff like that everytime I get a new piece of hardware.

--> for reference:

# cat /proc/bus/input/devices

[...]

I: Bus=0003 Vendor=04b3 Product=301b Version=0110
N: Name="Lite-On Technology USB Productivity Option Keyboard( has the
hub in # 1 )"
P: Phys=usb-0000:00:1d.1-1.1/input0
S: Sysfs=/class/input/input1
U: Uniq=
H: Handlers=kbd event1
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=04b3 Product=301b Version=0110
N: Name="Lite-On Technology USB Productivity Option Keyboard( has the
hub in # 1 )"
P: Phys=usb-0000:00:1d.1-1.1/input1
S: Sysfs=/class/input/input2
U: Uniq=
H: Handlers=kbd event2
B: EV=13
B: KEY=ff 2000000 3878d8000001 e000000000000 0
B: MSC=10

[...]

The part in my xorg.conf (googled that one):


Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Keyboard1" "SendCoreEvents"
InputDevice "Mouse0" "CorePointer"
EndSection

Section "InputDevice"

# generated from default
Identifier "Keyboard0"
Driver "evdev"
Option "Device" "/dev/input/event1"
EndSection

Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event2"
EndSection


--


Thanks a lot for any help on this, Stefan
 
Old 10-29-2009, 04:28 PM
Albert Hopkins
 
Default Lenovo USB Keyboard

On Thu, 2009-10-29 at 17:42 +0100, Stefan G. Weichinger wrote:
> Got myself a Lenovo keyboard ...
>
> a "ThinkPlus Enhanced Performance USB Keyboard"
>
> wow, it looked much better online than it feels now ... *sigh*
>
> I want to use that keyboard with Gnome (2.26 right now).
>
> I googled how to use the multimedia-keys already, seems as if I have
> to
> face some serious key-logging and hacking around to get those working
> (no, nothing usable on that funny CD).

Most of the time with GNOME they work out of the box.

I too use a keyboard that has all those glitzy keys on them. I rarely
use them however. I usually map them to other CTRL-ALT-ALNUM-like
shortcuts because then if I ever switch keyboards all my shortcuts will
still work and the keys are (for the most part) always in the same
location. But anyway, most of them just work except for the zoom in/out
keys. I haven't seen any X events for them yet.

GNOME has a settings for keyboard shortcuts. Usually you just have to
assign an even to a key if it's not already assigned.

I use the evdev managed keyboard. It seems to work much better than the
pre-defined layouts. And also I can easily switch keyboards and have
stuff "just work".

> Some of them work (volume, internet-keys to the left), only the 7 keys
> on top miss. I don't actually NEED them, but as I PAID them .... you
> know ... ;-)
>
> --
>
> Just before I start hacking myself, I want to ask you if maybe someone
> has already gone through this and is willing to share ...?
>
> Sorry if I sound lazy, actually I am already getting a bit tired of
> hacking stuff like that everytime I get a new piece of hardware.

Have you tried using the evdev driver?
 
Old 10-29-2009, 04:37 PM
"Stefan G. Weichinger"
 
Default Lenovo USB Keyboard

Albert Hopkins schrieb:

> GNOME has a settings for keyboard shortcuts. Usually you just have to
> assign an even to a key if it's not already assigned.

Sure, I tried that but those keys don't generate an event there (within
gnome-keybinding-properties).

> I use the evdev managed keyboard. It seems to work much better than the
> pre-defined layouts. And also I can easily switch keyboards and have
> stuff "just work".

That's what I assumed as well.

> Have you tried using the evdev driver?

My xorg.conf looks like I do, correct?

Xorg.0.log irritates me a bit --->

(**) Option "CoreKeyboard"
(**) Keyboard0: always reports core events
(**) Keyboard0: Device: "/dev/input/event1"
(II) Keyboard0: Found keys
(II) Keyboard0: Configuring as keyboard
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Option "SendCoreEvents"
(**) Keyboard1: always reports core events
(**) Keyboard1: Device: "/dev/input/event2"
(II) Keyboard1: Found 12 mouse buttons
(II) Keyboard1: Found keys
(II) Keyboard1: Configuring as keyboard
(**) Keyboard1: YAxisMapping: buttons 4 and 5
(**) Keyboard1: EmulateWheelButton: 4, EmulateWheelInertia: 10,
EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Lite-On Technology USB Productivity
Option Keyboard( has the hub in # 1 )
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): always reports core events
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Device: "/dev/input/event2"
(WW) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): device file already in use. Ignoring.
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "Lite-On Technology USB Productivity
Option Keyboard( has the hub in # 1 )"
(EE) config/hal: NewInputDeviceRequest failed (8)
(II) config/hal: Adding input device Lite-On Technology USB Productivity
Option Keyboard( has the hub in # 1 )
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): always reports core events
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Device: "/dev/input/event1"
(WW) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): device file already in use. Ignoring.
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "Lite-On Technology USB Productivity
Option Keyboard( has the hub in # 1 )"
(EE) config/hal: NewInputDeviceRequest failed (8)


*sigh*

thanks, greets, Stefan
 
Old 10-29-2009, 05:58 PM
Albert Hopkins
 
Default Lenovo USB Keyboard

I'm going to guess that the keyboard driver or something is interfering
with the evdev driver? Or you don't have proper evdev support in the
kernel? Or is your xorg.conf telling X to use a different driver?

I don't have access to a Gentoo machine right now, but when I look at a
similar machine (same exact keyboard though). I get this:

$ egrep -i '(key|evdev)' /var/log/Xorg.0.log
(II) Cannot locate a core keyboard device.
(==) intel(0): video overlay key set to 0x101fe
(II) Initializing built-in extension XKEYBOARD
(II) LoadModule: "evdev"
(II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
(II) ThinkPad Extra Buttons: Found keys
(II) ThinkPad Extra Buttons: Configuring as keyboard
(II) XINPUT: Adding extended input device "ThinkPad Extra
Buttons" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(II) Microsft Microsoft Wireless Desktop Receiver 3.1: Found keys
(II) Microsft Microsoft Wireless Desktop Receiver 3.1: Configuring as
keyboard
(II) XINPUT: Adding extended input device "Microsft Microsoft Wireless
Desktop Receiver 3.1" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event4"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2
keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(II) Microsft Microsoft Wireless Desktop Receiver 3.1: Found keys
(II) Microsft Microsoft Wireless Desktop Receiver 3.1: Configuring as
keyboard
(II) XINPUT: Adding extended input device "Microsft Microsoft Wireless
Desktop Receiver 3.1" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(II) Sleep Button: Found keys
(II) Sleep Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Sleep Button" (type:
KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(II) Video Bus: Found keys
(II) Video Bus: Configuring as keyboard
(II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type:
KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"

Not that it is XINPUT that is driving my keyboard, not Keyboard1. So
I'm guessing it's the X config.

Then again, it might be gpm. Are you using gpm? Maybe it's grabbing
the keyboard and not letting X have it.
 
Old 10-30-2009, 08:21 AM
"Stefan G. Weichinger"
 
Default Lenovo USB Keyboard

Albert Hopkins schrieb:
> I'm going to guess that the keyboard driver or something is interfering
> with the evdev driver? Or you don't have proper evdev support in the
> kernel? Or is your xorg.conf telling X to use a different driver?
>
> I don't have access to a Gentoo machine right now, but when I look at a
> similar machine (same exact keyboard though). I get this:
>
> $ egrep -i '(key|evdev)' /var/log/Xorg.0.log
> (II) Cannot locate a core keyboard device.
> (==) intel(0): video overlay key set to 0x101fe
> (II) Initializing built-in extension XKEYBOARD
> (II) LoadModule: "evdev"
> (II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so
> (II) Module evdev: vendor="X.Org Foundation"
> (II) ThinkPad Extra Buttons: Found keys
> (II) ThinkPad Extra Buttons: Configuring as keyboard
> (II) XINPUT: Adding extended input device "ThinkPad Extra
> Buttons" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "evdev"
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Found keys
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Configuring as
> keyboard
> (II) XINPUT: Adding extended input device "Microsft Microsoft Wireless
> Desktop Receiver 3.1" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (II) config/hal: Adding input device AT Translated Set 2 keyboard
> (**) AT Translated Set 2 keyboard: always reports core events
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4"
> (II) AT Translated Set 2 keyboard: Found keys
> (II) AT Translated Set 2 keyboard: Configuring as keyboard
> (II) XINPUT: Adding extended input device "AT Translated Set 2
> keyboard" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Found keys
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Configuring as
> keyboard
> (II) XINPUT: Adding extended input device "Microsft Microsoft Wireless
> Desktop Receiver 3.1" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (II) Sleep Button: Found keys
> (II) Sleep Button: Configuring as keyboard
> (II) XINPUT: Adding extended input device "Sleep Button" (type:
> KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "evdev"
> (II) Video Bus: Found keys
> (II) Video Bus: Configuring as keyboard
> (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "evdev"
> (II) Power Button: Found keys
> (II) Power Button: Configuring as keyboard
> (II) XINPUT: Adding extended input device "Power Button" (type:
> KEYBOARD)
> (**) Option "xkb_rules" "evdev"
> (**) Option "xkb_model" "evdev"
>
> Not that it is XINPUT that is driving my keyboard, not Keyboard1. So
> I'm guessing it's the X config.

Might be. Do you have any keyboard section in xorg.conf?
I assume I could get rid of xorg.conf at all but whenever I tried that
my X11 didn't start up anymore ...

> Then again, it might be gpm. Are you using gpm? Maybe it's grabbing
> the keyboard and not letting X have it.

No gpm running.

Stefan
 
Old 10-30-2009, 10:58 AM
Albert Hopkins
 
Default Lenovo USB Keyboard

On Fri, 2009-10-30 at 10:21 +0100, Stefan G. Weichinger wrote:
> > Not that it is XINPUT that is driving my keyboard, not Keyboard1.
> So
> > I'm guessing it's the X config.
>
> Might be. Do you have any keyboard section in xorg.conf?
> I assume I could get rid of xorg.conf at all but whenever I tried that
> my X11 didn't start up anymore ...

I'm using evdev with hal. I'm told if you use this combination you
shouldn't have any input devices in xorg.conf. In fact I don't even
have an xorg.conf in either my Gentoo or Fedora machines and they both
work fine. YMMV.

Ok, I just plugged a Logitech KB into my laptop. It has glitzy keys but
not as many (just multimedia, zoom, calculator and power/lock. Again,
all the keys "just work" except for zooms and also the "Media Center"
key and the "Music" key seem to both map to the same keypress
(XF86Tools), but I'm not one to use that button. I did lie in my
previous email though. I *do* use the volume keys but that's about it.
Anyway, when I plugged in the USB keyboard this is what got appended to
Xorg.0.log:

(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event12"
(**) Logitech USB Receiver: Device: "/dev/input/event12"
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as keyboard
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type:
KEYBOARD)
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type:
KEYBOARD)
(**) Option "xkb_rules" "evdev"

(**) Option "xkb_model"(**) Option "xkb_model" "evdev"

(**) Option "xkb_layout"(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event13"
(II) Logitech USB Receiver: Found 12 mouse buttons
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Found relative axes
(II) Logitech USB Receiver: Found x and y relative axes
(II) Logitech USB Receiver: Found absolute axes
(II) Logitech USB Receiver: Found absolute axes
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as mouse
(II) Logitech USB Receiver: Configuring as keyboard
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia:
10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type:
KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"

(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) acceleration profile 0
(II) Logitech USB Receiver: initialized for relative axes.
(WW) Logitech USB Receiver: ignoring absolute axes.

Well, it's interesting that it shows EmulateWheelButton because there's
nothing on the keyboard physically that appears to do that. But anyway,
"just works"

I have INPUT_DEVICES="evdev keyboard synaptics mouse" in make.conf and
in the GNOME keyboard preferences I just have "Evdev-managed keyboard".
For kernel config I have:

$ zgrep EVDEV /proc/config.gz
CONFIG_INPUT_EVDEV=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
# CONFIG_USB_PWC_INPUT_EVDEV is not set

HTH,
-a
 
Old 10-30-2009, 05:36 PM
"Stefan G. Weichinger"
 
Default Lenovo USB Keyboard

Albert Hopkins schrieb:

> I'm using evdev with hal. I'm told if you use this combination you
> shouldn't have any input devices in xorg.conf. In fact I don't even
> have an xorg.conf in either my Gentoo or Fedora machines and they both
> work fine. YMMV.

Nice for you. I just gave that a try and removed xorg.conf ... but I run
two monitors on a Nvidia-card so to define their resolutions and
positions I had to generate a config ... and that in turn also contains
input-sections. Removing those only still did not give me working mm-keys.

> Well, it's interesting that it shows EmulateWheelButton because there's
> nothing on the keyboard physically that appears to do that. But anyway,
> "just works"

I have that EmulateWheelButton (for the keyboard) as well ...

> I have INPUT_DEVICES="evdev keyboard synaptics mouse" in make.conf and
> in the GNOME keyboard preferences I just have "Evdev-managed keyboard".
> For kernel config I have:
>
> $ zgrep EVDEV /proc/config.gz
> CONFIG_INPUT_EVDEV=y
> CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
> # CONFIG_USB_PWC_INPUT_EVDEV is not set

Thanks a lot for your helpful infos.

--


Mine looks quite OK now as well:


(II) config/hal: Adding input device Lite-On Technology USB Productivity
Option Keyboard( has the hub in # 1 )
(II) LoadModule: "evdev"
(II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 2.2.5
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): always reports core events
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Device: "/dev/input/event2"
(II) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Found 12 mouse buttons
(II) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Found keys
(II) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Configuring as keyboard
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): YAxisMapping: buttons 4 and 5
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): EmulateWheelButton: 4, EmulateWheelInertia: 10,
EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Lite-On Technology USB
Productivity Option Keyboard( has the hub in # 1 )" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Lite-On Technology USB Productivity
Option Keyboard( has the hub in # 1 )
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): always reports core events
(**) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Device: "/dev/input/event1"
(II) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Found keys
(II) Lite-On Technology USB Productivity Option Keyboard( has the hub in
# 1 ): Configuring as keyboard
(II) XINPUT: Adding extended input device "Lite-On Technology USB
Productivity Option Keyboard( has the hub in # 1 )" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "de"
(II) config/hal: Adding input device Logitech USB-PS/2 Optical Mouse
(**) Logitech USB-PS/2 Optical Mouse: always reports core events
(**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event0"
(II) Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
(II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
(II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
(II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
(**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical
Mouse" (type: MOUSE)
(**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
(**) Logitech USB-PS/2 Optical Mouse: (accel) filter chain progression: 2.00
(**) Logitech USB-PS/2 Optical Mouse: (accel) filter stage 0: 20.00 ms
(**) Logitech USB-PS/2 Optical Mouse: (accel) set acceleration profile 0
(II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.


---> No more errors or warnings ... and "evdev" is used ... OK.

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.

Thanks anyway for help, Stefan
 
Old 11-03-2009, 09:23 AM
"Stefan G. Weichinger"
 
Default Lenovo USB Keyboard

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 ....

thanks, Stefan
 
Old 11-04-2009, 09:38 PM
Willie Wong
 
Default Lenovo USB Keyboard

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
 
Old 11-05-2009, 09:26 PM
Mick
 
Default Lenovo USB Keyboard

On Wednesday 04 November 2009 22:38:40 Willie Wong wrote:
> 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).

You could try xbindkeys -k or even use xev and look for the keycode amidst the
data that comes up on the terminal (but avoid moving the mouse at the same
time).
--
Regards,
Mick
 

Thread Tools




All times are GMT. The time now is 07:33 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org