1 |
Randy Barlow posted on Wed, 14 Nov 2012 17:06:54 -0500 as excerpted: |
2 |
|
3 |
> On Wed, 14 Nov 2012 16:45:27 -0500, Frank Peters |
4 |
> <frank.peters@×××××××.net> wrote: |
5 |
>> For the moment, at least, my solution will be to stop and then restart |
6 |
>> X. |
7 |
> |
8 |
> If I may, I suggest that you try the evdev solution that some others |
9 |
> have pointed out. The package is xf86-input-evdev, and it replaced your |
10 |
> mouse and keyboard drivers as one unified driver. I believe it may |
11 |
> require adjusting your xorg.conf since you have a custom one. |
12 |
> |
13 |
> According to [0], which admittedly did not cite a source (and I'm lazy |
14 |
> so I didn't do much searching), the evdev driver obsoletes the keyboard |
15 |
> and mouse driver. I seem to recall that there was a Gentoo news or |
16 |
> something about this a while back too, saying that keyboard and mouse |
17 |
> were obsolete, |
18 |
> but I again am lazy and haven't even attempted to find that :) |
19 |
> |
20 |
> [0] http://en.gentoo-wiki.com/wiki/X.Org/Mouse |
21 |
|
22 |
Yes, evdev is the standard replacement for both the X keyboard and mouse |
23 |
drivers. There's a couple things to note, however: |
24 |
|
25 |
* There's a kernel option that must be turned on as well. If it's not, |
26 |
the evdev driver won't find the devices to work with (CONFIG_INPUT_EVDEV, |
27 |
listed as "Event interface" under device drivers, input device support, |
28 |
generic input layer). |
29 |
|
30 |
* If you run gpm for text console mouse support, you still need the |
31 |
kernel's mouse interface (CONFIG_INPUT_MOUSEDEV, providing |
32 |
/dev/input/mice and /dev/input/mouseX) turned on. Otherwise you can turn |
33 |
it off. It doesn't interfere with evdev. |
34 |
|
35 |
* If you run special purpose hardware like touchpads (the syntouch |
36 |
driver), you can still use those instead if you wish. However, evdev |
37 |
should work for the vast majority of cases, and can be used for most |
38 |
special purpose including touchpad devices as well, except it doesn't |
39 |
have all the extra touchpad (or other hardware) specific configuration |
40 |
options. |
41 |
|
42 |
|
43 |
* An additional more general point about xorg.conf. As others have |
44 |
suggested, it's rarely needed now, except for specifying "unusual" |
45 |
configurations such as the orientation of multiple monitors if you're |
46 |
using them, non-default drivers and/or driver options (the syntouch |
47 |
driver, or mouse accel options, for instance), etc. And for that, |
48 |
multiple individual *.conf files in /etc/X11/xorg.conf.d/, each with a |
49 |
section or more with its non-default options, works better for many than |
50 |
a single monolithic xorg.conf file does. |
51 |
|
52 |
Here, I have four such *.conf files, one with the "Device" section for my |
53 |
graphics card (with as I said a few non-default settings), one for my |
54 |
"InputClass" sections (trackball accel settings on my main machine, |
55 |
syntouch settings on my netbook, an Option "Ignore" section for the HDMI |
56 |
audio on my graphics card and another for the /dev/input/mouseX and mice |
57 |
devices to quiet the X logs a bit, etc), one with "Monitor" sections to |
58 |
setup their positioning for my multiple monitors on my main machine and |
59 |
activate the additional modes section, and one with that "Modes" section |
60 |
with extra modes for non-default resolutions. They're named accordingly, |
61 |
so I can edit just the one I want if I want to change something, without |
62 |
even looking at the others. |
63 |
|
64 |
-- |
65 |
Duncan - List replies preferred. No HTML msgs. |
66 |
"Every nonfree program has a lord, a master -- |
67 |
and if you use the program, he is your master." Richard Stallman |