walt wrote:
...
If you have an unusual mouse, as I do, you will need to create a
new fdi file in /etc/hal/fdi/policy/ to get it working properly.
Oops, forgot to mention /usr/bin/lshal, which will tell you what
hald thinks it knows about your hardware.
As one more example, here is what lshal says about my logitech
mouse *after* I added my /etc/hal/fdi/policy/10-x11-logitech.fdi:
udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input'
info.capabilities = {'input', 'input.mouse'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port'
(string)
info.product = 'ImExPS/2 Logitech Explorer Mouse' (string)
info.subsystem = 'input' (string)
info.udi =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input'
(string)
input.device = '/dev/input/event4' (string)
input.originating_device =
'/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port' (string)
input.product = 'ImExPS/2 Logitech Explorer Mouse' (string)
input.x11_driver = 'evdev' (string)
input.x11_options.EmulateWheel = 'true' (string) <*** my new fdi file added
this line ****
input.x11_options.EmulateWheelButton = '8' (string) <*** and this line, but
nothing else ****
linux.device_file = '/dev/input/event4' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio1/input/input4/event4'
(string)
HTF the average user is supposed to figure all this out for himself
is beyond me. I'm thankful for the expert help I got.
