FS#5257 - xf86-input-evdev 1.1.2-1 fails on symlinked mouse
Attached to Project:
Arch Linux
Opened by Marcel (ferkulat) - Saturday, 19 August 2006, 23:20 GMT
Last edited by Alexander Baldeck (kth5) - Wednesday, 05 September 2007, 09:34 GMT
Opened by Marcel (ferkulat) - Saturday, 19 August 2006, 23:20 GMT
Last edited by Alexander Baldeck (kth5) - Wednesday, 05 September 2007, 09:34 GMT
|
Details
Identifier "Mouse1"
Driver "evdev" Option "Device" "/dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse" The lines above worked in my xorg.conf before update. After updateting the package, I have to check on which event my mouse is bound, Option "Device" "/dev/input/event2" otherwise startx will exit with an error. Since the mouse is an usb-type, the event for the mouse changes by plugging devices in different order. |
This task depends upon
Closed by Alexander Baldeck (kth5)
Wednesday, 05 September 2007, 09:34 GMT
Reason for closing: Not a bug
Wednesday, 05 September 2007, 09:34 GMT
Reason for closing: Not a bug
[...]
(II) evdev brain: Rescanning devices (1).
(**) Option "CorePointer"
(**) Mouse1-isa0060/serio0/input0: Core Pointer
(**) Option "CorePointer"
(**) Mouse1-isa0060/serio3/input0: Core Pointer
(II) Mouse1-isa0060/serio3/input0: Found 4 absolute axes.
(II) Mouse1-isa0060/serio3/input0: Configuring as pointer.
(**) Mouse1-isa0060/serio3/input0: Configuring in Absolute mode.
(**) Mouse1-isa0060/serio3/input0: AbsoluteScreen: 0.
(II) Mouse1-isa0060/serio3/input0: Found 0 relative axes.
(II) Mouse1-isa0060/serio3/input0: Configuring as pointer.
(**) Mouse1-isa0060/serio3/input0: Configuring 2 relative axes.
(II) Mouse1-isa0060/serio3/input0: Found 79 mouse buttons
(II) Mouse1-isa0060/serio3/input0: Configured 79 mouse buttons
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:10.0-1/input0: Core Pointer
(II) Mouse1-usb-0000:00:10.0-1/input0: Found 4 relative axes.
(II) Mouse1-usb-0000:00:10.0-1/input0: Configuring as pointer.
(**) Mouse1-usb-0000:00:10.0-1/input0: HWHEELRelativeAxisButtons: 6 7.
(**) Mouse1-usb-0000:00:10.0-1/input0: WHEELRelativeAxisButtons: 4 5.
(II) Mouse1-usb-0000:00:10.0-1/input0: Found 16 mouse buttons
(II) Mouse1-usb-0000:00:10.0-1/input0: Configured 20 mouse buttons
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:10.0-2/input0: Core Pointer
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:10.0-2/input1: Core Pointer
(II) Mouse1-usb-0000:00:10.0-2/input1: Found 76 mouse buttons
(II) Mouse1-usb-0000:00:10.0-2/input1: Configured 76 mouse buttons
(**) Option "CorePointer"
(**) Mouse1-isa0061/input0: Core Pointer
(EE) Mouse1-isa0061/input0: Don't know how to use device.
(II) UnloadModule: "evdev"
(EE) PreInit failed for input device "Mouse1"
(i found out the hard way you can't do this with wacom devices, as it uses the wacom driver, not the evdev driver, even though it's accessing the event devices. wacom will let you use symlinks, though.)
Shitty design decision in my opinion.
You don't HAVE to use the Name, it's just the simplest for most cases I think. You can also go by vendor and product IDs, or by Phys (which matches a USB port I believe).
Phys is the _only_ one that works for me :(