[SOLVED]Mouse Doesn't Work in X

[0x001A4]

I'm having a problem with my USB mouse. It's a Razer Imperator and I've seen a couple other posts regarding people having trouble with this mouse. None of them had a solution.

When Xorg starts, I just can't move the mouse at all. Here is my Xorg log pertaining to this device:

Code: Select all

[    16.637] (II) config/udev: Adding input device Razer Razer Imperator (/dev/input/event2)
[    16.637] (**) Razer Razer Imperator: Applying InputClass "evdev pointer catchall"
[    16.637] (II) Using input driver 'evdev' for 'Razer Razer Imperator'
[    16.637] (**) Razer Razer Imperator: always reports core events
[    16.637] (**) evdev: Razer Razer Imperator: Device: "/dev/input/event2"
[    16.637] (--) evdev: Razer Razer Imperator: Vendor 0x1532 Product 0x17
[    16.637] (--) evdev: Razer Razer Imperator: Found 11 mouse buttons
[    16.637] (--) evdev: Razer Razer Imperator: Found scroll wheel(s)
[    16.637] (--) evdev: Razer Razer Imperator: Found relative axes
[    16.637] (--) evdev: Razer Razer Imperator: Found x and y relative axes
[    16.637] (II) evdev: Razer Razer Imperator: Configuring as mouse
[    16.637] (II) evdev: Razer Razer Imperator: Adding scrollwheel support
[    16.637] (**) evdev: Razer Razer Imperator: YAxisMapping: buttons 4 and 5
[    16.637] (**) evdev: Razer Razer Imperator: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    16.637] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2/event2"
[    16.637] (II) XINPUT: Adding extended input device "Razer Razer Imperator" (type: MOUSE, id 8)
[    16.638] (II) evdev: Razer Razer Imperator: initialized for relative axes.
[    16.638] (**) Razer Razer Imperator: (accel) keeping acceleration scheme 1
[    16.638] (**) Razer Razer Imperator: (accel) acceleration profile 0
[    16.638] (**) Razer Razer Imperator: (accel) acceleration factor: 2.000
[    16.638] (**) Razer Razer Imperator: (accel) acceleration threshold: 4
[    16.638] (II) config/udev: Adding input device Razer Razer Imperator (/dev/input/mouse0)
[    16.638] (II) No input driver specified, ignoring this device.
[    16.638] (II) This device may have been added with another device file.
[    16.638] (II) config/udev: Adding input device Razer Razer Imperator (/dev/input/event3)
[    16.638] (**) Razer Razer Imperator: Ignoring device from InputClass "Razer Imperator Keyboard"

And my Xorg.conf:

Code: Select all

Section "InputClass"
    Identifier "Razer Imperator Keyboard"
    MatchDevicePath "/dev/input/event3"
    MatchIsKeyboard "On"
    Option "Ignore" "On"
EndSection

For some reason, this mouse is seen as a mouse and as a keyboard. I read in a similar post to try and ignore the keyboard portion. That is working but it hasnt fixed the problem. Even if I remove that section, the mouse doesn't work.

Not sure what the problem could be because the mouse works in the Ubunutu live cd I used to install Gentoo. Any help is appreciated.

[stratcloud]

This is a pretty common issue. There are some posts regarding this : http://forums.gentoo.org/viewtopic-t-936970.html

[PaulBredbury]

None of them had a solution.

It works for this guy.

[0x001A4]

I found the solution in this post http://forums.gentoo.org/viewtopic-t-91 ... art-0.html

I was getting this repeatedly in my dmesg

Code: Select all

[ 1170.018057] usb 2-1.7: reset full-speed USB device number 17 using ehci_hcd
[ 1170.029018] hub 2-1:1.0: port 7 not reset yet, waiting 10ms
[ 1170.074338] hub 2-1:1.0: state 7 ports 8 chg 0000 evt ff80
[ 1170.102714] usb 2-1.7: ep0 maxpacket = 8

I enabled Improved Transaction Translator scheduling in the kernel and its working fine now.
It was under Device Drivers > USB Support > EHCI HCD (USB 2.0) support

[Konsti]

I wonder if there are any news regarding this issue. I say "news" because to my computer the setup has become really nearly unuseable now and I find no solution in the couple of threads here regarding the issue.

I found many threads in this forum (not outside in the internet or in other forums!) regarding this issue, I started to experience this with an gentoo setup and a razer copperhead mouse: Sometimes I simply have to plug out/plug in the mouse to be able to move the cursor instead of being able to do clicks in the upper left corner.

Meantime I have an archlinux (I will run gentoo there soon again ) on this computer running and a mainboard providing USB-3.0. And I have a new mouse, a razer imperator. When it is plugged into an USB-3.0 port, I can only click, not move the cursor. Replugging solves the problem. Any time, any boot. The trouble is anywhere in the timing of USB recognition or udev and the xorg server picking up, what kernel and udev delivers.

I wonder because of that, because the kernel output when replugging is identical:

Code: Select all

[  119.698756] input: Razer Razer Imperator as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.0/input/input4
[  119.698823] hid-generic 0003:1532:002F.0001: >input,hidraw0: USB HID v1.11 Mouse [Razer Razer Imperator] on usb-0000:04:00.0-2/input0
[  119.699688] input: Razer Razer Imperator as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-2/5-2:1.1/input/input5
[  119.699729] hid-generic 0003:1532:002F.0002: >input,hidraw1: USB HID v1.11 Keyboard [Razer Razer Imperator] on usb-0000:04:00.0-2/input1

[  149.646221] input: Razer Razer Imperator as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-1/5-1:1.0/input/input17
[  149.646516] hid-generic 0003:1532:002F.0003: >input,hidraw0: USB HID v1.11 Mouse [Razer Razer Imperator] on usb-0000:04:00.0-1/input0
[  149.648341] input: Razer Razer Imperator as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb5/5-1/5-1:1.1/input/input18
[  149.648499] hid-generic 0003:1532:002F.0004: >input,hidraw1: USB HID v1.11 Keyboard [Razer Razer Imperator] on usb-0000:04:00.0-1/input1

When I plug the mouse into an USB-2.0 port, it continously gets resetted -> reconnected -> resetted -> reconnected -> resetted ...

Code: Select all

Oct 15 21:21:35 localhost kernel: [48315.139668] usb 2-1.6: >new full-speed USB device number 5 using ehci_hcd
Oct 15 21:21:35 localhost kernel: [48315.227135] input: Razer Razer Imperator as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input21
Oct 15 21:21:35 localhost kernel: [48315.227422] hid-generic 0003:1532:002F.0007: >input,hidraw0: USB HID v1.11 Mouse [Razer Razer Imperator] on usb-0000:00:1d.0-1.6/input0
Oct 15 21:21:35 localhost kernel: [48315.229277] input: Razer Razer Imperator as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.1/input/input22
Oct 15 21:21:35 localhost mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6"
Oct 15 21:21:35 localhost mtp-probe: bus: 2, device: 5 was not an MTP device
Oct 15 21:21:35 localhost kernel: [48315.229546] hid-generic 0003:1532:002F.0008: >input,hidraw1: USB HID v1.11 Keyboard [Razer Razer Imperator] on usb-0000:00:1d.0-1.6/input1
Oct 15 21:21:37 localhost kernel: [48317.502476] usb 2-1.6: >USB disconnect, device number 5
Oct 15 21:21:37 localhost acpid: input device has been disconnected, fd 11

I found one hint in the several razer mouse threads which said to enable

Code: Select all

CONFIG_USB_EHCI_TT_NEWSCHED=y

to avoid this, on my kernel this IS enabled already.

Is there any help to get these mice running without replugging or has the discussion/solution taken some other place in the community?

Kind regards, Konsti

[PaulBredbury]

Maybe setting power/control will help.

[Konsti]

Meanwhile I am convinced the imperator mice itself have such problems. Thanks for your info pointing me to the usb powermanagement debugging and configuration issues, I will take care of that.

After submitting my post here I searched further upon and the mouse and its precedessor are very famous in google with the "coldboot bug" among the whole internet and Operating Systems. IIRC even in the BIOS I needed to replug the mouse (yes, my new motherboard's BIOS runs well with a mouse!). Some people say FW update does not help, others say it does. I updated the Firmware on mine also now (1.02 -> 1.04) and will tell here, what happened.

Kind Regards, Konsti