At Thu, 17 Dec 2009 15:34:51 -0800 walt <w41...@gmail.com> wrote:
> On 12/17/2009 01:23 PM, Allan Gottlieb wrote:
>
>>
>> I do have two InputDevice sections in xorg.conf about the mouse, but my
>> ServerLayout only mentions one. I attach both my log and xorg.conf
>> below.
>
> If you are using evdev (and you are) you should delete (or comment out)
> anything to do with Input from your xorg.conf, e.g. these sections:
>
> Section "InputDevice"
> Identifier "Keyboard0"
> Driver "kbd"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "auto"
> Option "Device" "/dev/input/mice"
> Option "ZAxisMapping" "4 5 6 7"
> EndSection
>
> and also remove/comment these lines from ServerLayout:
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
>
> The evdev driver is intended to replace *all* of that stuff.
Yes, but those lines are effectively "commented out".
I have three ServerLayout sections but only the first counts (see
excerpt from the xorg.conf man page below). The first ServerLayout
section (the "active one") references the logitech mouse and not mouse0
so the mouse driver is not loaded at all.
I do specify the keyboard, but that is working fine.
> BTW, I remember having a section like this in my xorg.conf, but
> I don't have it any longer and I don't think you really need it:
> Section "InputDevice"
> Identifier "Logitech MX1000"
> Driver "evdev"
> Option "Device" "/dev/input/event2"
> EndSection
>
> I think that the evdev driver is loaded by default now, so you
> don't need to mention it in xorg.conf.
>
> Caveat: I needed to add /etc/hal/fdi/policy/10-x11-logitech.fdi
> to replace two lines in my xorg.conf because my mouse has four
> buttons and no wheel. You obviously don't have that problem, so
> I think your mouse should Just Work without any extra fdi files.
I do not use the hal stuff. I was scared off by the horror stories
reported here. Perhaps this summer I will give it a go.
thanks again for helping,
allan
SERVERLAYOUT SECTION
The config file may have multiple ServerLayout sections. A
"server layout" represents the binding of one or more screens
(Screen sections) and one or more input devices (InputDevice
sections) to form a complete configuration. In multi-head
configurations, it also specifies the relative layout of the
heads. A ServerLayout section is considered "active" if it is
referenced by the -layout command line option or by an Option
"DefaultServerLayout" entry in the ServerFlags section (the
former takes precedence over the latter). If those options are
not used, the first ServerLayout section found in the config file
is con- sidered the active one. If no ServerLayout sections are
present, the single active screen and two active (core) input
devices are selected as described in the relevant sections above.
