The answer was staring me in the face all afternoon....   That's what I get 
for actually trying to get real work done...  getting distracted from really 
really important things like figuring out how to tweak a keyboard just 
because... :)

Here's the steps I did:

1. Run the "xev" command, and find the keycodes for each of the extended 
buttons.  (In my case, I have "www", "@", "zz", "star", "power" buttons.)
2. Edit or create a file in your home directory called ".xmodmaprc" (without 
quotes of course).  This file contains the names that will be associated with 
the keycodes.  Mine looks like this:

keycode 178 = F14
keycode 236 = F15
keycode 223 = F16
keycode 227 = F17
keycode 222 = F18

(yeah, I skipped F13 - it's unlucky don't you know...)

3. Run the command "xmodmap ~/.xmodmaprc" (without quotes).
This is the command that was staring me in the face all day, while I left one 
of the links open that Jarrod posted earlier - 
http://www.4momo.de/artikel__show_db__other__104.htm.  I had followed the 
instructions to the point of creating the .xmodmaprc file, but missed the 
next line indicating the xmodmap command.... <sighs>  Then left it to work on 
real stuff...

4. Go into KDE Control Center (or the Gnome equivalent), and find the place to 
setup keyboard shortcuts (under Regional & Accessibility --> Keyboard 
Shortcuts for me).  When you try to map one of the extended keys to an 
action, you will see the name you gave that key in the .xmodmaprc file.  

5. Apply your changes and test your buttons - It's great to be able to open 
Konsole now at a key press.. (not that it was THAT hard beforehand...)

THE CATCH - you have to either manually run the xmodmap command each time you 
boot up, or change your keyboard layout, or you'll need to find a way to get 
this to run automagically everytime you log in.  Maybe putting it in 
the .bashrc or .bash_profile files in your home folder?  (Haven't tried this 
yet, so don't know for sure - anyone want to comment?).  One added bonus of 
doing this is that different users can have different settings for the 
keyboard at the same box.  OR you can make this global and add the xmodmap 
command to the /etc/profile file - just make sure the .xmodmaprc file is 
someplace suitable with appropriate permissions.

If anyone knows a better method, than the one I described, please correct 
me...  I can take it.. honest.. :)

Thanks everyone for putting up with my struggles today....

Shawn


On Monday 07 November 2005 23:55, Shawn wrote:
> Hmmm... I have a bunch of files in that symbols directory, but not an
> "inet" file.  So, I checked out the "us" file - which is the default as I
> understand things.  Found a section for the function keys, so added some
> extra functions (FK13 - Fk17).  And I already have a .xmodmaprc file from a
> previous attempt, that should allow me to map these Function keys to the
> actions I want...
>
> I'll check it in the morning after I reboot, it's almost time for bed...
>
> Thanks for the tip.
>
> Shawn
>
> On Monday 07 November 2005 23:22, Jon Storry wrote:
> > I think the file that you want to look at is if you haven't already is
> > /etc/X11/xkb/symbols/inet  look at some of the other keyboards layouts
> > and copy whats there.
> >
> > if you add another layout be sure to update the
> > ../xkb/rules/xfree86.lst and .xml file
> >
> > As for the "keys <ae02>" stuff,  the "ae02" describes the column and
> > row of the key as it is located on the keyboard, but I cant remember
> > how it works.
> >
> > Hope this helps, I haven't really looked at this stuff in a while
> >
> > Jon
> >
> > On 11/7/05, Shawn <[EMAIL PROTECTED]> wrote:
> > > Limited success....
> > >
> > > I tried messing around with some of the files hinted at in the various
> > > links posted in this thread, with no luck.  I installed lineak and
> > > xmodmap, and even looked at modifying the X.org xkb definition files
> > > (chickened out - don't understand the format yet).  None of this seemed
> > > to help, but this *could* be because I'm on a Gentoo box which by
> > > default is pretty customized....
> > >
> > > But I did look into selecting a different keyboard layout via KDE's
> > > control center (Regional & Accessibility / Keyboard Layout).  Thus far
> > > I've had the best luck with the Logitech iTouch Internet Navigator
> > > Keyboard layout - I can get 3 of the 5 extra buttons working so far...
> > > (set the layout, apply changes, then go to the Keyboard shortcuts
> > > section, and the Command Shortcuts tab, then assigned these buttons to
> > > Konqueror, Kontact, and OO.o Wordprocessor)
> > >
> > > Anyone know the layout of the keymap definition files?  I can figure
> > > out the numeric value part (keycode), and the name, but I don't know
> > > what the <AAAA> type characters are for - hex values for the keycode?
> > >
> > > Shawn
> > >
> > > On Monday 07 November 2005 18:05, Gustin Johnson wrote:
> > > > More urls to browse:
> > > > http://lineak.sourceforge.net/
> > > > http://gentoo-wiki.com/HOWTO_Mouse_Nav_Buttons
> > > > http://www.linux-gamers.net/modules/wfsection/article.php?articleid=4
> > > >6
> > > >
> > > > I also used xev to capture the keycodes (they appear in dmesg, so you
> > > > can tail -f syslog to see what is happening).
> > > >
> > > > I have all the buttons on my logitech mx510 working.  Also, the media
> > > > keys on my laptop worked "out of the box" by choosing the Dell
> > > > Inspiron keyboard layout from the KDE control panel (the Compaq
> > > > laptop keyboard layout only partially worked.. and I have a compaq
> > > > presario).
> > > >
> > > > My own experiences have been a mix of good and bad.  I was not able
> > > > to get the lineak stuff working in kde (the kde gui front end) so I
> > > > ended up going the script route, which fortunatly for everyone is
> > > > well documented (you don't need to know how to write scripts, though
> > > > as always, it is never a bad thing to learn).  Some distros may be
> > > > more point and click, but even though the klinea stuff was not
> > > > working under kubuntu, I was able to get all the functionality
> > > > working with less effort than expected.
> > > >
> > > > It looks like the main page for lineak is down, but you should be
> > > > able to get the important stuff from this link:
> > > > http://lineak.sourceforge.net/index.php?nav=showdoc
> > > >
> > > > Cheers
> > > >
> > > > Jarrod Major wrote:
> > > > > On Monday 07 November 2005 12:42 pm, Jarrod Major wrote:
> > > > >>On Monday 07 November 2005 12:15 pm, Jarrod Major wrote:
> > > > >>>This is actually a topic I am interested in as well. I have a
> > > > >>> Logitech Internet Keyboard that has a bunch of extra keys as
> > > > >>> well. While I am not necessarily looking to map them to exactly
> > > > >>> what they are labelled as it might be cool to map them to some
> > > > >>> other commonly used actions.
> > > > >
> > > > > http://www.win.tue.nl/~aeb/linux/kbd/scancodes-5.html
> > > > >
> > > > > This site may list your keyboard and give you some hints as to how
> > > > > to map it. My keyboard is listed but I'm not sure what to do with
> > > > > the info yet.
> > > > >
> > > > >
> > > > > -------------------------------------------------------------------
> > > > >-- ---
> > > > >
> > > > > _______________________________________________
> > > > > clug-talk mailing list
> > > > > [email protected]
> > > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> > > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> > > > > **Please remove these lines when replying
> > > >
> > > > _______________________________________________
> > > > clug-talk mailing list
> > > > [email protected]
> > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> > > > **Please remove these lines when replying
> > >
> > > _______________________________________________
> > > clug-talk mailing list
> > > [email protected]
> > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> > > **Please remove these lines when replying
> >
> > _______________________________________________
> > clug-talk mailing list
> > [email protected]
> > http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> > Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> > **Please remove these lines when replying

Attachment: pgpKfUV7ysPTt.pgp
Description: PGP signature

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to