Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a wireless optical mouse with my new PC, but when I plug it in, nothing happens. I'd like to poke around, but I don't know where to start. What are the various configuration files used with mice? Are the drivers modules? Is there a general mouse howto as opposed to a USB/ button one that I keep comming across?
OK. It's an Ortek wireless infrared mouse. It came with my wireless Keyboard (which alwayed worked fine). The model number of the set is MCK-9000. Both connect vie PS/2. There are batteries in the mouse. I never see anything in /var/log/messages nor dmesg. In short when I plug in the new mouse it acts like I didn't plug it in.
now we need to know your:
linux distribution ( your profile shows red hat)
version (your profile show 9)
are you trying to use the mouse in the console?
are you trying to use the mouse in Xwindows?
IF yes to Xwindows, what version?
Oh, sorry, I should have included that. I'm running Fedora Core 2, with the 2.6.7 kernel (but I had to patch it to get the forcedeth driver for my nVidia ethernet thinge to work). Haven't tried using the mouse in the consol, just X. I think I've got X.org though (isn't that what FC2 comes with?) I guessed that `X -version` might be useful, so here it is:
[~]$ X -version
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF]
Current Operating System: Linux localhost.localdomain 2.6.7 #1 Fri Jul 23 18:40:45 IST 2004 i686
Build Date: 07 May 2004
Build Host: tweety.build.redhat.com
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.7 (email@example.com) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Fri Jul 23 18:40:45 IST 2004
There is also one one the keyboard and a lot of commented out mouse stuff.
I must admit that I really should have RTFM. After reading the manual, I was able to set the correct channel on the mouse, and now, when I plug it in, the mouse goes mental. It hops around the screen (tending to wind up on the right hand side of the screen), and the buttons seem to be pressed erraticly. When I don't try to move the mouse, it doesn't move, but when I move it (or press a button) it goes crazy.
Here is some the output of `tail /var/log/messages` for when the mouse was going mad:
Jul 28 14:39:12 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
Jul 28 14:39:17 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Jul 28 14:39:26 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
Jul 28 14:39:28 localhost last message repeated 2 times
Jul 28 14:39:31 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Jul 28 14:39:41 localhost last message repeated 2 times
Jul 28 14:39:43 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
Jul 28 14:39:45 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
Jul 28 14:39:53 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
Jul 28 14:40:42 localhost kernel: psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
This happens if the mouse is on a few types of surfaces (it's an optical mouse). The reciever is just 'under' my monitor and beside my speakers (it's pretty cramped), could that be causing interference? But i've never had a problem with my keyboard, it's always gone grand. Are mice more sensitive to interference?
What is in your modprobe.conf file? If your mouse has a light, is it turned on?
When I moved from RH9 to Fedora 2 (by doing an "upgrade" install), I wound up with modprobe.conf as an empty file, and several other files having been built. In particular, one called something like modprobe.conf.anaback had the configuration lines necessary for modprobe to activate my usb mouse and kb, and also my NIC. I fixed the problem by simply renaming that file to modprobe.conf, and then running modprobe.