SlackwareThis Forum is for the discussion of Slackware 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've been working with this Slackware installation for quite a while. A few days back, the mouse started to behave weirdly, sending false signals from time to time. Having thought it must be faulty, I replaced it with a brand new one. To my surprise the problem persisted, only getting worse and worse to the point of rendering the computer unusable. every few seconds (of actively moving the mouse, being idle doesn't count) it sends 5-10 false signals at the same time or in a very short period, like the pointer jumping all over the screen, left/right/middle clicks like mad, etc.
This time I was pretty sure that the PS/2 port is the source of the trouble, but a quick boot to Windows (where there was no apparent issue) proved this wrong. Note that this behavior doesn't require X appear, it can begin right after the rc.gpm script is executed.
I have no idea what might be causing this. I haven't touched a single config file recently, and a web search didn't come up with anything useful.
More weirdness: this doesn't have anything to do with gpm. Any combination of Xserver and gpm cause it to happen.
Last bit of info I forgot to include: the madness stops (albeit for only a few seconds) only after I lift up the mouse for a while, and put it back down.
Make sure PS/2 mouse is set as a module in the kernel. If it is not, the mouse will not be detected correctly or it will not be detected upon boot up. The 2.6.x kernel and udev can not detect PS/2 mouse is a problem. The PS/2 mouse module have to be loaded manually is the only fix. I suggest playing around with options that the PS/2 mouse module provides. The PS/2 mouse module is named psmouse. The utility to find out what options that a module has and its information is /sbin/modinfo.
If it still gives you problems, probably it is time to invest in a newer and better power supply. If you do not want to that just yet, including noapic and/or noapci or apci=off at the boot loader.
I am the opposite, my mouse is a little glitchy in Windows. I had to disable fast initialization to make my mouse behave better in Windows. Only in Linux, I have the most control with my mouse. I use a KVM switch.
I don't have FreeBSD installation right now, but the problem persists with Ubuntu LiveCD. So I don't think it's related to kernel or distro.
As stated at the end of my first post,it doesn't have anything to do with gpm. I have already tried every combination of gpm and X.
Note that I've been using this kernel (with very minor modifications) for like 3 years. psmouse hasn't been compiled as a module, but it's very unlikely for this to be the source of the problem.
As for the power supply, I have just recently changed to a new one (a few weeks before the mouse went berserk). But could you please elaborate a bit more? What possible relation could acpi have with this?
Well, I just replaced the (new) mouse with another one and the problem was magically solved. Thing is, the mouse I had replaced the old one with was the exact same model, but this one is a slightly different model. Still I can't figure out how my mobo could have become hostile towards one specific model (which I was using normally for a long time).