| 1 |
On 12/12/2009 03:14 PM, Mick wrote: |
| 2 |
|
| 3 |
> ... |
| 4 |
> I have had mouse, keyboard and synaptics along with evdev in my |
| 5 |
> INPUT_DEVICES and have emerged relative drivers. I am now going to |
| 6 |
> remove them and see what gives. |
| 7 |
|
| 8 |
I know nothing about the synaptics driver, so be careful about deleting |
| 9 |
it. Maybe rename it instead of deleting it? |
| 10 |
|
| 11 |
> |
| 12 |
> I am not clear which /etc/hal/fdi/policy/* files I should have in |
| 13 |
> there ... any ideas? |
| 14 |
|
| 15 |
That depends on what hardware you have -- a lot of the stuff that once |
| 16 |
went into xorg.conf can be put in an fdi file now. |
| 17 |
|
| 18 |
Here is an example: I have an unusual mouse with four buttons and no |
| 19 |
wheel, and I use one extra button to simulate a mouse wheel: |
| 20 |
|
| 21 |
$cat /etc/hal/fdi/policy/10-x11-logitech.fdi |
| 22 |
<?xml version="1.0" encoding="ISO-8859-1"?> |
| 23 |
<deviceinfo version="0.2"> |
| 24 |
<device> |
| 25 |
<match key="info.product" contains="ImExPS/2"> |
| 26 |
<merge key="input.x11_options.EmulateWheel" type="string">true</merge> |
| 27 |
<merge key="input.x11_options.EmulateWheelButton" type="string">8</merge> |
| 28 |
</match> |
| 29 |
</device> |
| 30 |
</deviceinfo> |
| 31 |
|
| 32 |
The two lines with "input.x11_options" used to be in my xorg.conf in the |
| 33 |
Input section. Those lines do the same thing now that I've moved them into |
| 34 |
an fdi file. |
Archives