Madcatz Cyborg R.A.T. 7 Gaming Mouse drivers needed.

[nikitis]

Madcatz Cyborg R.A.T. 7 Gaming mouse. (Kernel recognizes it as a Saitek Cyborg R.A.T. 7 mouse.)

I already posted this in the Desktop hardware incompatibility list, but I'm doing it here to just so it gets noticed.

This mouse works when you first start into Gnome or KDE. I've done this on my Desktop running Gnome 10.04, and KDE 10.04 on my Laptop, and I get the same results.

When using it after a few seconds, things no longer become clickable left or right. I'm not entirely sure if it's the mouse, or if it's the Display Managers (Maybe Xorg?), but if I push the buttons to change the "DPI" Settings on the mouse, things work again for a few more seconds, then it starts to happen all over again.

The only thing that makes me think it's on the software side of things and not just the hardware is 1.) It works in Windows without drivers and doesn't crashes, and 2.) in KDE, I can still click on the big "K" start menu like item while it's wigging out. This mouse has an usually high Dot Per Inch laser and maybe the linux kernel can't handle it? 5400 DPI. Most mice only go up to like 800 or 1500.

Anyway, I tried asking in #ubuntu IRC, but they don't know what's going on. They had me try a: $ tail -f /var/log/syslog and tail -f /var/log/messages to see if there was anything going nuts while using it, and I got nothing except for the plug in and plug out messages.

This mouse needs to work if Linux is ever going to be taken seriously on the gaming front please, please PLEASE i beg someone to help me diagnose and fix this error! I will do/try anything, including reinstalls. Just help me out here!

[mohaine]

I can verify this issue.

It seems that with this mouse hooked up, the window manager gets confused. The application with focus will still accept mouse clicks, but you can not click on anything outside the focused window.

Pressing the mode button will fix things for a bit, but the issue will come back very quickly(< 30 seconds)

[pag747]

Same issue!!

[pag747]

Firefox and Gedit


(firefox-bin:11366): Gdk-CRITICAL **: gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed

(gedit:13609): Gdk-CRITICAL **: gdk_window_get_events: assertion `GDK_IS_WINDOW (window)' failed

[mohaine]

This seems to be an Xorg issue.

I've compiled Xorg from GIT and it seems to be fixed upstream.

Still broken in 10.10 alpha 3.

[jawvvd]

Please log in and vote (mark yourself as affected) here: https://bugs.launchpad.net/ubuntu/+s...el/+bug/615892

Hopefully it's possible to patch this for 10.04, after all it's a LTS release...

[Ancanus]

Does the workaround posted on the bug report work for you guys?

[TheMadEngineer]

I managed to get the Xmodmap fix to work in 10.10 with a R.A.T. 3 Mouse, though with a slight modification:

In ~/.Xmodmap,

pointer = 1 2 3 4 5 6 7 8 9 0 0 0

Apparently, the mode button is specified by 10, 11, and 12 for this mouse. To get it to work, though, I had to actually restart the X server from a virtual terminal after rebooting.

[bl4z]

that worked for me // thanks

I managed to get the Xmodmap fix to work in 10.10 with a R.A.T. 3 Mouse, though with a slight modification:

In ~/.Xmodmap,

pointer = 1 2 3 4 5 6 7 8 9 0 0 0

Apparently, the mode button is specified by 10, 11, and 12 for this mouse. To get it to work, though, I had to actually restart the X server from a virtual terminal after rebooting.

[mpampis636]

Hello Im using the RAT 5, and not 7, on Debian. I've run into the same problem many times. Everytime this happens, i log out and log back in, and the mouse works. However the solution of changing .Xmodmap or even the global Xmodmap didn't help. I run xev, and noted down all buttons, which run from 1,2,3,4,5,8,9,10,11,12,[13,14,15],16,17 The buttons 13,14,15 are found on the same button (the emblem that switches profiles). I tried using /dev/input/event instead of /paux/mouse, with options buttons 15 enabled in xorg.conf but still nothing changed. Im assuming the problem lies with the fact that the profile button is mapped as 3 different buttons, cuz If i log in (the second time) and never click it, the mouse keeps running fine. I don't know how to go on, to solve this issue, but I'm assuming someone with more experience might have a solution...