Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
Last edited by Kyuuketsuki; 11-20-2007 at 01:38 PM.
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:
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?
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
Last edited by Kyuuketsuki; 11-25-2007 at 01:15 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.