ByteME

The Keyboard

The keyboard is marked on the rear as a Logetech Access Keyboard, it features special buttons labled E-Mail, Messenger/SMS, Webcam, Media, My Home and Search as well as volume up+down buttons a mute button, a user button and the function keys all have two functions with a Flock key providing access to the extended functions.

Kernel config

Well not actual kernel configuration but out of the box on my system I got kernel messages about unknown scancodes, so it is first necessary to use xmodmap to tell the system what the scancodes are and give them a usable name. I created a file called .Xmodmap in my home directory (~/) with the following contents :-

#.Xmodmap, keycodes for a Logitech Access Keyboard
keycode 144 = logitech_rew
keycode 145 = logitech_sms
keycode 146 = logitech_webcam
keycode 147 = logitech_itouch
keycode 148 = logitech_shopping
keycode 153 = logitech_fwd
keycode 160 = logitech_mute
keycode 162 = logitech_playpause
keycode 164 = logitech_stop
keycode 174 = logitech_voldown
keycode 176 = logitech_volup
keycode 178 = logitech_myhome
keycode 223 = logitech_user
keycode 229 = logitech_search
keycode 230 = logitech_favorites
keycode 233 = logitech_go
keycode 234 = logitech_arrow
keycode 236 = logitech_email
keycode 237 = logitech_media

It is necessary to get xmodmap to run this and the best place I decided for this was in my ~/.xsession file. Please not .xsession .xprofile etc vary from distribution, to be really sure what gets run you need to look at /etc/X11/XSession which is the parent script. Also note that the XSession script was a bit broke on my system and I had to fix it before it would run my ~/.xsession files. My ~/.xsession had this extra line to load the keymap

if [ -f $HOME/.Xmodmap ]; then
    /usr/X11R6/bin/xmodmap $HOME/.Xmodmap
fi

Now the kernel understands the keymaps and X will now use the keys by their logetech_ name so it is easy to do things with them.

KDE KHotkeys

Normally you would edit the setup for khot keys through the kde khotkeys configuration dialogues but for reference it is easier to print the config file. This file exists in your home directory and may well have other stuff in it but the logetech specific stuff that I use is below. The location on my system was ~/.kde/share/config/khotkeysrc :-

[Data_2]
DataCount=13
Name=Logitech MM KB

[Data_2_1]
Comment=Search the Internet.
Name=Search the Internet

[Data_2_10]
Comment=Launch the mail client.
Enabled=true
Name=Mail Client
Type=COMMAND_URL_SHORTCUT_ACTION_DATA

[Data_2_10Actions]
ActionsCount=1

[Data_2_10Actions0]
CommandURL=/usr/bin/kontact-mail.sh
Type=COMMAND_URL

[Data_2_10Conditions]
Comment=
ConditionsCount=0

[Data_2_10Triggers]
Comment=Simple_action
TriggersCount=1

[Data_2_10Triggers0]
Key=Logitech_email
Type=SHORTCUT

[Data_2_11]
Comment=
Enabled=true
Name=Play
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_2_11Actions]
ActionsCount=1

[Data_2_11Actions0]
Arguments=
Call=playPause
RemoteApp=juk
RemoteObj=Player
Type=DCOP

[Data_2_11Conditions]
Comment=
ConditionsCount=0

[Data_2_11Triggers]
Comment=Simple_action
TriggersCount=1

[Data_2_11Triggers0]
Key=Logitech_playpause
Type=SHORTCUT

[Data_2_12]
Comment=
Enabled=true
Name=Prev Track
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_2_12Actions]
ActionsCount=1

[Data_2_12Actions0]
Arguments=
Call=back
RemoteApp=juk
RemoteObj=Player
Type=DCOP

[Data_2_12Conditions]
Comment=
ConditionsCount=0

[Data_2_12Triggers]
Comment=Simple_action
TriggersCount=1

[Data_2_12Triggers0]
Key=Logitech_rew
Type=SHORTCUT

[Data_2_13]
Comment=
Enabled=true
Name=Next Track
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_2_13Actions]
ActionsCount=1

[Data_2_13Actions0]
Arguments=
Call=forward
RemoteApp=juk
RemoteObj=Player
Type=DCOP

[Data_2_13Conditions]
Comment=
ConditionsCount=0

[Data_2_13Triggers]
Comment=Simple_action
TriggersCount=1

[Data_2_13Triggers0]
Key=Logitech_fwd
Type=SHORTCUT

[Data_2_1Actions0]
CommandURL=/usr/bin/konqueror http://www.google.co.uk

[Data_2_1Triggers0]
Key=Logitech_search

[Data_2_2]
Comment=Launch the Internet browser.
Name=Internet browser

[Data_2_2Actions0]
CommandURL=/usr/bin/konqueror

[Data_2_2Triggers0]
Key=Logitech_myhome

[Data_2_3]
Comment=
Name=Mute

[Data_2_3Actions0]
CommandURL=

[Data_2_3Triggers0]
Key=Logitech_mute

[Data_2_4]
Comment=
Name=Stop
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_2_4Actions0]
Arguments=
Call=stop
CommandURL[$d]
RemoteApp=juk
RemoteObj=Player
Type=DCOP

[Data_2_4Triggers0]
Key=Logitech_stop

[Data_2_5]
Comment=
Name=StartTV

[Data_2_5Actions0]
CommandURL=mplayer /dev/video0

[Data_2_5Triggers0]
Key=Logitech_media

[Data_2_6]
Comment=Decrease the volume.
Name=Decrease Volume
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_2_6Actions0]
Arguments=1
Call=decreaseVolume
CommandURL[$d]
RemoteApp=kmix
RemoteObj=Mixer0
Type=DCOP

[Data_2_6Triggers0]
Key=Logitech_voldown

[Data_2_7]
Comment=
Name=IMClient
Type=DCOP_SHORTCUT_ACTION_DATA

[Data_2_7Actions0]
Arguments=
Call=
CommandURL[$d]
RemoteApp=
RemoteObj=
Type=DCOP

[Data_2_7Triggers]
TriggersCount=0

[Data_2_7Triggers0]
Key[$d]
Type[$d]

[Data_2_8Triggers0]
Key=Logitech_volup

[Data_2_9]
Comment=Launch the screensaver to protect the session.
Name=Lock the screen
Type=COMMAND_URL_SHORTCUT_ACTION_DATA

[Data_2_9Actions0]
Arguments[$d]
Call[$d]
CommandURL=/usr/bin/kdesktop_lock --forcelock
RemoteApp[$d]
RemoteObj[$d]
Type=COMMAND_URL

[Data_2_9Triggers0]
Key=Logitech_user

Notes: The volume and mute buttons use DCOP calls to access KMix that must be running. The web browser is set to konqueror, The media key starts mplayer for me and looks at /dev/video0 that is my tv capture card and the music keys use DCOP calls to access kjuk.