Alright, so getting tired of having to deal with it, I remapped everything. It took a while and keep reloading my Xmodmap file to get what I needed. At least it works :D
On Sat, Dec 6, 2008 at 6:20 PM, Will Siddall <[EMAIL PROTECTED]> wrote: > Right, but I'm not using KDE, I'm using Gnome. I've tried using an > Evdev-managed keyboard, and I've tried using a generic pc105... all with no > luck. Plus, I've already upgraded to 1.5.3-3. > > > On Sat, Dec 6, 2008 at 6:14 PM, Jan de Groot <[EMAIL PROTECTED]> wrote: > >> On Sat, 2008-12-06 at 17:45 -0400, Will Siddall wrote: >> > Hey all, I say I'm pretty comfortable with everything in arch now, but >> > this keyboard issue is starting to drive me nuts. Not too long ago, >> > the change from using kbd to evdev was made and ever since then, my >> > keyboard is all messed up. I can still use my keyboard, but specific >> > keys are changed around. >> > >> > Looking around, everyone is refering to issues with KDEMod, but I'm >> > using Gnome and using the Evdev-Managed Keyboard. I specified in my >> > 10-keymap.fdi rule file the proper settings and updated my xorg.conf >> > with no change. >> > >> > The real issue I have is my arrow keys don't work anymore (except for >> > the up arrow is giving me the ScreenCap window) and using xev, the >> > keys are bringing back keycodes for other events. Which is making it >> > REALLY hard to work with vi and just working with the command line in >> > general. >> > >> > Am I actually going to have to re-key all my keycodes by hand? or is >> > there a way to find out what's going on and properly set my key >> > events? >> >> Upgrade to xorg-server 1.5.3-3 and set your keyboard in KDE to "evdev >> managed keyboard" or something similiar. Setting it to a specific other >> model that matches your keyboard will mess up keybindings when using >> evdev. >> >> >
