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 <landronimirc@gmail.com> 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
> <daniel.pielmeier@googlemail.com> 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.
>>>
>

> Can anyone suggest how to revert to my xorg.conf configuration, and to
> make "left shift" a "proper" modifier key, again? Thank you,
> Liviu
The easiest way probably is to disable input hotplugging:

Put the following line in Section "ServerFlags" in the xorg.conf:
Option "AutoAddDevices" "false"


- Sascha

Thank you a lot, Sascha.

On Tue, Aug 26, 2008 at 11:03 AM, Sascha Hlusiak <saschahlusiak@arcor.de> wrote:
> Put the following line in Section "ServerFlags" in the xorg.conf:
> Option "AutoAddDevices" "false"
>
This worked like a charm. Would another solution be to re-compile
xorg-server with -hal?

Liviu

Am Dienstag 26 August 2008 20:06:57 schrieb Liviu Andronic:
> Thank you a lot, Sascha.
>
> On Tue, Aug 26, 2008 at 11:03 AM, Sascha Hlusiak <saschahlusiak@arcor.de>
wrote:
> > Put the following line in Section "ServerFlags" in the xorg.conf:
> > Option "AutoAddDevices" "false"
>
> This worked like a charm. Would another solution be to re-compile
> xorg-server with -hal?
It would, but I find runtime-tuning much easier and transparent.
input-hotplugging really is a fine thing, if you get a little time to
configure it.

- Sascha

On Tue, Aug 26, 2008 at 8:15 PM, Sascha Hlusiak <saschahlusiak@arcor.de> wrote:
>> This worked like a charm. Would another solution be to re-compile
>> xorg-server with -hal?
> It would, but I find runtime-tuning much easier and transparent.
> input-hotplugging really is a fine thing, if you get a little time to
> configure it.
>
If readily available, could you please point to some example fdi files
(or appropriate documentation)?
Thank you,
Liviu

Am Dienstag 26 August 2008 23:09:37 schrieb Liviu Andronic:
> On Tue, Aug 26, 2008 at 8:15 PM, Sascha Hlusiak <saschahlusiak@arcor.de>
wrote:
> >> This worked like a charm. Would another solution be to re-compile
> >> xorg-server with -hal?
> >
> > It would, but I find runtime-tuning much easier and transparent.
> > input-hotplugging really is a fine thing, if you get a little time to
> > configure it.
>
> If readily available, could you please point to some example fdi files
> (or appropriate documentation)?
I suggest you leave the fdi file /usr/share/hal/... as it is and provide
changes locally in /etc. Attached is my /etc/hal/fdi/policy/10-keymap.fdi
file that I use to make it all German. Should be easily tweaked to your
needs. But don't touch Model and Rules, since that needs to be evdev
specific. You need to reload/restart hal after changing that file. And make
sure that the keyboard layout in xfce/gnome/kde is set to evdev, NOT pc105,
since that breaks the mapping again.


Good luck,

Sascha
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<merge key="input.xkb.model" type="string">evdev</merge>
<merge key="input.xkb.layout" type="string">de</merge>
<merge key="input.xkb.variant" type="string">nodeadkeys</merge>
</match>
</device>
</deviceinfo>