Evdev 1.1.2: Using evdev with the following configuration: > Section "InputDevice" > Identifier "Mouse0" > Driver "evdev" > Option "Dev Name" "Logitech USB RECEIVER" # cat /proc/bus/input/devices > EndSection Produces the following error on my system: > (II) evdev brain: Rescanning devices (1). > (**) Option "CorePointer" > (**) Mouse0-isa0061/input0: Core Pointer > (EE) Mouse0-isa0061/input0: Don't know how to use device. X promptly dies for lack of a mouse. > atrus@agaeris:~$ uname -a > Linux agaeris 2.6.17.6 #1 PREEMPT Sun Jul 16 01:13:27 MDT 2006 i686 GNU/Linux /proc/bus/input/devices: > I: Bus=0010 Vendor=001f Product=0001 Version=0100 > N: Name="PC Speaker" > P: Phys=isa0061/input0 > S: Sysfs=/class/input/input0 > H: Handlers=kbd event0 > B: EV=40001 > B: SND=6 > > I: Bus=0003 Vendor=046d Product=c50e Version=2510 > N: Name="Logitech USB RECEIVER" > P: Phys=usb-0000:00:07.2-1.3/input0 > S: Sysfs=/class/input/input1 > H: Handlers=mouse0 event1 > B: EV=7 > B: KEY=ffff0000 0 0 0 0 0 0 0 0 > B: REL=143 > > I: Bus=0003 Vendor=046d Product=c30a Version=1500 > N: Name="Logitech Logitech USB Keyboard" > P: Phys=usb-0000:00:07.2-1.4/input0 > S: Sysfs=/class/input/input2 > H: Handlers=kbd event2 > B: EV=120003 > B: KEY=10000 7 ff800000 7ff febeffdf ffefffff ffffffff fffffffe > B: LED=1f > > I: Bus=0003 Vendor=046d Product=c30a Version=1500 > N: Name="Logitech Logitech USB Keyboard" > P: Phys=usb-0000:00:07.2-1.4/input1 > S: Sysfs=/class/input/input3 > H: Handlers=kbd mouse1 event3 > B: EV=7 > B: KEY=ffffffff ffffffff f80 40000 601878 d801d108 1e0000 0 0 0 > B: REL=103 > > I: Bus=0003 Vendor=047d Product=102a Version=0100 > N: Name="Kensington Kensington USB/PS2 Wheel Mouse" > P: Phys=usb-0000:00:0d.0-2/input0 > S: Sysfs=/class/input/input4 > H: Handlers=mouse2 event4 > B: EV=7 > B: KEY=70000 0 0 0 0 0 0 0 0 > B: REL=103
User error, 'Dev Name' is not a valid option, 'Name' will do what you want. Zephaniah E. Hull.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.