Results 1 to 3 of 3
Everytime X loads the mouse cursor is frozen, so I have to drop to command line and edit xorg.conf device line. Here's the mouse section:
Code:
Section "InputDevice"
# generated ...
- 07-05-2009 #1Just Joined!
- Join Date
- Oct 2005
- Posts
- 20
Event number changes everytime X loads
Everytime X loads the mouse cursor is frozen, so I have to drop to command line and edit xorg.conf device line. Here's the mouse section:
Sometimes it's event2 or event4 or whatever. This is happening because I have other event devices that bump my mouse out of control.Code:Section "InputDevice" # generated from default Identifier "Mouse0" Driver "evdev" Option "Protocol" "PS/2" Option "Device" "/dev/input/event5" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5 6 7" Option "Buttons" "7" EndSection
Is there a way to force my mouse to use a specific event number? Or is there another solution?
- 07-07-2009 #2Just Joined!
- Join Date
- May 2006
- Location
- San Jose, CA
- Posts
- 67
Here is how the mouse section is in my xorg
What other devices are conflicting with the mouse? Are you loading/running any special drivers for your mouse.. other than the ones that come with the kernel? I am not quite sure what the issue is.. you could see if you have a /dev/input/mice or /dev/psaux.. and see if changing to that helps.Code:Section "InputDevice" Identifier "PS/2 Mouse" Driver "mouse" Option "Protocol" "auto" Option "ZAxisMapping" "4 5" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "true" Option "Emulate3Timeout" "70" Option "SendCoreEvents" "true" EndSection Section "InputDevice" Identifier "USB Mouse" Driver "mouse" Option "Device" "/dev/input/mice" Option "SendCoreEvents" "true" Option "Protocol" "IMPS/2" Option "ZAxisMapping" "4 5" Option "Buttons" "5" EndSection
- 07-08-2009 #3Just Joined!
- Join Date
- Oct 2005
- Posts
- 20
Well, the evdev driver (Event Device driver) is a driver that works with joysticks and other input devices. I have joysticks that stick themselves before or after in the que or whatever evdev does to decide what number each device gets. This is what I'm wondering, if there's a way to decide for evdev which physical device attaches to which block device in /dev.
With evdev you use event# not /dev/mouse or whatever.
I'm guessing that sometime during the boot cycle evdev makes this decision. If I was to take a stab at this that fixing it would require knowledge of recoding the driver itself.
Code:cat /proc/bus/input/devices I: Bus=0019 Vendor=0000 Product=0002 Version=0000 N: Name="Power Button (FF)" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/class/input/input0 U: Uniq= H: Handlers=kbd event0 B: EV=3 B: KEY=10000000000000 0 I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button (CM)" P: Phys=PNP0C0C/button/input0 S: Sysfs=/class/input/input1 U: Uniq= H: Handlers=kbd event1 B: EV=3 B: KEY=10000000000000 0 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-0000:00:1a.0-2/input0 S: Sysfs=/class/input/input2 U: Uniq= H: Handlers=kbd event2 B: EV=120013 B: KEY=1000000000007 ff800000000007ff febeffdff3cfffff fffffffffffffffe B: MSC=10 B: LED=107 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-0000:00:1a.0-2/input1 S: Sysfs=/class/input/input3 U: Uniq= H: Handlers=kbd event3 B: EV=10001f B: KEY=837fff002c3027 bf00444400000000 1 10f848a27c007 ff7f7bfad9415fff febeffdfffefffff fffffffffffffffe B: REL=40 B: ABS=100000000 B: MSC=10 I: Bus=0003 Vendor=1532 Product=0101 Version=1001 N: Name="Razer Razer Copperhead Laser Mouse" P: Phys=usb-0000:00:1a.1-1/input0 S: Sysfs=/class/input/input4 U: Uniq= H: Handlers=mouse0 event4 B: EV=17 B: KEY=ff0000 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=1532 Product=0101 Version=1001 N: Name="Razer Razer Copperhead Laser Mouse" P: Phys=usb-0000:00:1a.1-1/input1 S: Sysfs=/class/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=100013 B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe B: MSC=10 I: Bus=0003 Vendor=06a3 Product=0464 Version=0100 N: Name="Saitek Cyborg USB Stick" P: Phys=usb-0000:00:1d.0-1/input0 S: Sysfs=/class/input/input6 U: Uniq= H: Handlers=event6 js0 B: EV=1b B: KEY=fff00000000 0 0 0 0 B: ABS=30027 B: MSC=10


Reply With Quote