1 |
At Thu, 17 Dec 2009 15:34:51 -0800 walt <w41ter@×××××.com> wrote: |
2 |
|
3 |
> On 12/17/2009 01:23 PM, Allan Gottlieb wrote: |
4 |
> |
5 |
>> |
6 |
>> I do have two InputDevice sections in xorg.conf about the mouse, but my |
7 |
>> ServerLayout only mentions one. I attach both my log and xorg.conf |
8 |
>> below. |
9 |
> |
10 |
> If you are using evdev (and you are) you should delete (or comment out) |
11 |
> anything to do with Input from your xorg.conf, e.g. these sections: |
12 |
> |
13 |
> Section "InputDevice" |
14 |
> Identifier "Keyboard0" |
15 |
> Driver "kbd" |
16 |
> EndSection |
17 |
> |
18 |
> Section "InputDevice" |
19 |
> Identifier "Mouse0" |
20 |
> Driver "mouse" |
21 |
> Option "Protocol" "auto" |
22 |
> Option "Device" "/dev/input/mice" |
23 |
> Option "ZAxisMapping" "4 5 6 7" |
24 |
> EndSection |
25 |
> |
26 |
> and also remove/comment these lines from ServerLayout: |
27 |
> InputDevice "Mouse0" "CorePointer" |
28 |
> InputDevice "Keyboard0" "CoreKeyboard" |
29 |
> |
30 |
> The evdev driver is intended to replace *all* of that stuff. |
31 |
|
32 |
Yes, but those lines are effectively "commented out". |
33 |
I have three ServerLayout sections but only the first counts (see |
34 |
excerpt from the xorg.conf man page below). The first ServerLayout |
35 |
section (the "active one") references the logitech mouse and not mouse0 |
36 |
so the mouse driver is not loaded at all. |
37 |
|
38 |
I do specify the keyboard, but that is working fine. |
39 |
|
40 |
> BTW, I remember having a section like this in my xorg.conf, but |
41 |
> I don't have it any longer and I don't think you really need it: |
42 |
> Section "InputDevice" |
43 |
> Identifier "Logitech MX1000" |
44 |
> Driver "evdev" |
45 |
> Option "Device" "/dev/input/event2" |
46 |
> EndSection |
47 |
> |
48 |
> I think that the evdev driver is loaded by default now, so you |
49 |
> don't need to mention it in xorg.conf. |
50 |
> |
51 |
> Caveat: I needed to add /etc/hal/fdi/policy/10-x11-logitech.fdi |
52 |
> to replace two lines in my xorg.conf because my mouse has four |
53 |
> buttons and no wheel. You obviously don't have that problem, so |
54 |
> I think your mouse should Just Work without any extra fdi files. |
55 |
|
56 |
I do not use the hal stuff. I was scared off by the horror stories |
57 |
reported here. Perhaps this summer I will give it a go. |
58 |
|
59 |
thanks again for helping, |
60 |
allan |
61 |
|
62 |
SERVERLAYOUT SECTION |
63 |
The config file may have multiple ServerLayout sections. A |
64 |
"server layout" represents the binding of one or more screens |
65 |
(Screen sections) and one or more input devices (InputDevice |
66 |
sections) to form a complete configuration. In multi-head |
67 |
configurations, it also specifies the relative layout of the |
68 |
heads. A ServerLayout section is considered "active" if it is |
69 |
referenced by the -layout command line option or by an Option |
70 |
"DefaultServerLayout" entry in the ServerFlags section (the |
71 |
former takes precedence over the latter). If those options are |
72 |
not used, the first ServerLayout section found in the config file |
73 |
is con- sidered the active one. If no ServerLayout sections are |
74 |
present, the single active screen and two active (core) input |
75 |
devices are selected as described in the relevant sections above. |