Oh, I forgot to post the errors X generates at startup: The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Multiple names for keycode 211 > Using <I211>, ignoring <AB11> expected keysym, got XF86AudioEject: line 2232 of inet Errors from xkbcomp are not fatal to the X server
Liviu On Mon, Aug 25, 2008 at 10:24 PM, Liviu Andronic <[EMAIL PROTECTED]> wrote: > Dear Gentoo users, > > I have installed the latest stable hal-0.5.11-r1 and hal-info-20080508 > yesterday, and I give up: i cannot configure the keyboard layout as it > was previously in xorg.conf, and i cannot use the left-hand shift (the > latter is the annoying part). Here's what i have: > > /etc/X11/xorg.conf > Section "InputDevice" > Identifier "Keyboard0" > Driver "keyboard" > Option "CoreKeyboard" > Option "XkbRules" "xorg" > Option "XkbModel" "pc105" > Option "XkbLayout" "gb,fr,ru,ro" > Option "XkbOptions" "grp:alt_shift_toggle" > Option "XkbVariant" ",,winkeys,std" > EndSection > > Trying > Driver "evdev" > would make X not start any more. I tried playing with > /usr/share/hal/fdi/policy/10osvendor/10-keymap.fdi to no avail. It > seems to me that X uses evdev, no matter what I try. Also, I have only > en_US as layout and "left shift" launches xfce's help, although as a > shortcut key F1 is disabled here. I also disabled my .Xmodmap. > > Can anyone suggest how to revert to my xorg.conf configuration, and to > make "left shift" a "proper" modifier key, again? Thank you, > Liviu > > > > On Sun, Aug 3, 2008 at 9:31 AM, Daniel Pielmeier > <[EMAIL PROTECTED]> wrote: >>> This is the symptom I see when I try "evdev" driver and am using a MS >>> Natural Pro keyboard. Briefly the keyboard is handled as two USB >>> devices. The keys that work are on the first device, the ones that >>> don't on the second device. Following gentoo-wiki howtos it looks like >>> you have to hack the kernel. At that point I simply reverted to using >>> the "kbd" driver. Maybe some year evdev will mature... >>> >>> Quick check, look in your xorg.conf "ServerLayout" section, identify >>> which keyboard InputDevice, then check to see which driver it is using. >>> >
