Mouse Issues

Kyuuketsuki · 11-20-2007, 01:06 PM

Hi,

I have an issue with my mouse in that it locks up ... I was in the SuSE KDE desktop for less than 5 minutes when it locked.

The mouse in question is a Saitek GM3200 Gamers mouse. It is USB, corded, very sensitive, highly responsive and I bought it to replace my MS wireless mouse which was giving a fairly lacklustre response under Windows XP. Interestingly, though I have had no problems with it under XP, it failed several times under Vista.

Any ideas?

Kyu

Kyuuketsuki · 11-21-2007, 05:37 AM

OK, so I saw some of the requirements for posting hardware issues and have been talking to a friend about what to look at ... apologies if this makes no sense.

On Knoppix (version 5.0 kernel 2.6.17) I typed: /sbin/lspci:

Quote:

0000:00:00.0 Host bridge: nVidia Corporation: Unknown device 0071 (rev a1)
0000:00:00.1 RAM memory: nVidia Corporation: Unknown device 007f (rev a1)
0000:00:00.2 RAM memory: nVidia Corporation: Unknown device 0075 (rev a1)
0000:00:00.3 RAM memory: nVidia Corporation: Unknown device 006f (rev a1)
0000:00:00.4 RAM memory: nVidia Corporation: Unknown device 00b4 (rev a1)
0000:00:01.0 RAM memory: nVidia Corporation: Unknown device 0076 (rev a1)
0000:00:01.1 RAM memory: nVidia Corporation: Unknown device 0078 (rev a1)
0000:00:01.2 RAM memory: nVidia Corporation: Unknown device 0079 (rev a1)
0000:00:01.3 RAM memory: nVidia Corporation: Unknown device 007a (rev a1)
0000:00:01.4 RAM memory: nVidia Corporation: Unknown device 007b (rev a1)
0000:00:01.5 RAM memory: nVidia Corporation: Unknown device 007c (rev a1)
0000:00:01.6 RAM memory: nVidia Corporation: Unknown device 007d (rev a1)
0000:00:02.0 PCI bridge: nVidia Corporation: Unknown device 007e (rev a2)
0000:00:09.0 RAM memory: nVidia Corporation: Unknown device 003f (rev a1)
0000:00:0a.0 ISA bridge: nVidia Corporation: Unknown device 0030 (rev a3)
0000:00:0a.1 SMBus: nVidia Corporation MCP04 SMBus (rev a2)
0000:00:0b.0 USB Controller: nVidia Corporation MCP04 USB Controller (rev a1)
0000:00:0b.1 USB Controller: nVidia Corporation MCP04 USB Controller (rev a1)
0000:00:0b.2 USB Controller: nVidia Corporation MCP04 USB Controller (rev a2)
0000:00:0f.0 IDE interface: nVidia Corporation MCP04 IDE (rev f2)
0000:00:10.0 IDE interface: nVidia Corporation MCP04 Serial ATA Controller (rev f2)
0000:00:11.0 RAID bus controller: nVidia Corporation MCP04 Serial ATA Controller (rev f2)
0000:00:12.0 PCI bridge: nVidia Corporation MCP04 PCI Bridge (rev a2)
0000:00:13.0 Multimedia audio controller: nVidia Corporation MCP04 AC'97 Audio Controller (rev a1)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 554f
0000:01:00.1 Display controller: ATI Technologies Inc: Unknown device 556f
0000:02:06.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
0000:02:06.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
0000:02:06.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
0000:02:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

On openSUSE (version 10.3 kernel 2.6.22.5-31-default) I typed: /sbin/lspci:

Quote:

00:00.0 Host bridge: nVidia Corporation Unknown device 0071 (rev a1)
00:00.1 RAM memory: nVidia Corporation Unknown device 007f (rev a1)
00:00.2 RAM memory: nVidia Corporation Unknown device 0075 (rev a1)
00:00.3 RAM memory: nVidia Corporation Unknown device 006f (rev a1)
00:00.4 RAM memory: nVidia Corporation Unknown device 00b4 (rev a1)
00:01.0 RAM memory: nVidia Corporation Unknown device 0076 (rev a1)
00:01.1 RAM memory: nVidia Corporation Unknown device 0078 (rev a1)
00:01.2 RAM memory: nVidia Corporation Unknown device 0079 (rev a1)
00:01.3 RAM memory: nVidia Corporation Unknown device 007a (rev a1)
00:01.4 RAM memory: nVidia Corporation Unknown device 007b (rev a1)
00:01.5 RAM memory: nVidia Corporation Unknown device 007c (rev a1)
00:01.6 RAM memory: nVidia Corporation Unknown device 007d (rev a1)
00:02.0 PCI bridge: nVidia Corporation Unknown device 007e (rev a2)
00:09.0 RAM memory: nVidia Corporation Unknown device 003f (rev a1)
00:0a.0 ISA bridge: nVidia Corporation Unknown device 0030 (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP04 SMBus (rev a2)
00:0b.0 USB Controller: nVidia Corporation MCP04 USB Controller (rev a1)
00:0b.1 USB Controller: nVidia Corporation MCP04 USB Controller (rev a1)
00:0b.2 USB Controller: nVidia Corporation MCP04 USB Controller (rev a2)
00:0f.0 IDE interface: nVidia Corporation MCP04 IDE (rev f2)
00:10.0 IDE interface: nVidia Corporation MCP04 Serial ATA Controller (rev f2)
00:11.0 RAID bus controller: nVidia Corporation MCP04 Serial ATA Controller (rev f2)
00:12.0 PCI bridge: nVidia Corporation MCP04 PCI Bridge (rev a2)
00:13.0 Multimedia audio controller: nVidia Corporation MCP04 AC'97 Audio Controller (rev a1)
01:00.0 VGA compatible controller: ATI Technologies Inc R430 [Radeon X800 (PCIE)]
01:00.1 Display controller: ATI Technologies Inc R430 [Radeon X800] (PCIE) (Secondary)
02:06.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
02:06.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05)
02:06.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05)
02:0c.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)

I also typed "tail -f /var/log/messages" (before the mouse locked up):

Quote:

Nov 21 11:10:45 ar-draco-lx gconfd (undead-4572): Resolved address "xml:readonly:/etc/gconf/gconf.xml.schemas" to a read-only configuration source at position 3
Nov 21 11:11:11 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:11:11 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:12:17 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:12:17 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:13:23 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:13:23 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:14:37 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:14:37 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:14:59 ar-draco-lx su: (to root) undead on /dev/pts/1

... and again "tail -f /var/log/messages" (after the mouse locked up, I had to attach a conventional mouse to get the info):

Quote:

Nov 21 11:13:23 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:14:37 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:14:37 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:14:59 ar-draco-lx su: (to root) undead on /dev/pts/1
Nov 21 11:15:45 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:15:45 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:16:45 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:16:45 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:18:07 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:18:07 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
tail -f /var/log/messages
Nov 21 11:13:23 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:14:37 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:14:37 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:14:59 ar-draco-lx su: (to root) undead on /dev/pts/1
Nov 21 11:15:45 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:15:45 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:16:45 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:16:45 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.
Nov 21 11:18:07 ar-draco-lx kernel: atkbd.c: Unknown key released (translated set 2, code 0x81 on isa0060/serio0).
Nov 21 11:18:07 ar-draco-lx kernel: atkbd.c: Use 'setkeycodes e001 <keycode>' to make it known.

I stress I do not know what this information means, nor what other info I need to get but maybe it will help?

Kyu

Kyuuketsuki · 11-25-2007, 10:13 AM

More on this:

The last time I tried to use openSUSE my mouse didn't lock up as such ... after about 30 minutes of use it just went to exceptionally slow (and kind of "vibraty" on the screen if that makes sense) and in order to click anywhere I would have to drag the mouse, say, 10 times across to get it to actually move where I wanted.

This also seems (and I am not absolutely sure) to be a purely SuSE/openSUSE issue as I have had other LiveCD based Linux's running without issue.

I decided to test that last idea and rebuilt using openSUSE 10.1 and although I haven't *used it in anger* it never locked up once during the build process. From a technical perspective I find that intriguing as, not only does it strongly imply there is a change that affects USB mouse function is 10.3, but it also opens the door to a possible upgrade from 10.1 to 10.3 that, for whatever reason, may not end up in mouse lockups.

FURTHER EDIT:
Well ... 45 minutes in and no lockup so far. It may be time to start asking configuration questions.

Kyu