SlackwareThis Forum is for the discussion of Slackware 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.
Spent most of the night trying to figure out what was going wrong with my mouse. All of a sudden, it stopped working, sort of. I could move the cursor around on the screen, but there were some icons that I couldn't click on, while others I could. Eventually, all of them became unclickable. I tried a ctrl+alt+delete to end session, and I couldn't even click on that, nor could I hit the enter key on the keyboard to select the end session button.
My mouse worked fine up until today, when this strange behavior started. I tried reinstalling Slack, and I'm still experiencing the same effect. Installing Slack a third time disabled the mouse on the cli.
Can anyone tell me what's going on? Slackware is the only distribution that I've used, and I really would like to continue the trend, but if I can't get this to work, I'm going to have to look elsewhere. What would be a good alternative to Slackware (something not too foreign) if I can't get this to work?
I assume that you have actually verified there is not a hardware failure here? Like load up a live CD, and use that for a day or so, to see if the problem persists there.
Hmm..I'll have to try that one. I should have a live version of SuSE or Knoppix lying around somewhere.
I also should clarify that I'm using a Compaq laptop with a usb mouse. I don't have any more specs, as I'm currently going out the door onto work, but I could run any commands needed/necessary at the cli.
When I tried the 2.4 default kernel, I didn't notice this happening at all. However, I need the ipw2200 card for my wireless to work, which is the only reason I went with huge26 to begin with. Is it possible there's a kernel difference between these two that may throw the mouse into orbit?
When I tried the 2.4 default kernel, I didn't notice this happening at all. However, I need the ipw2200 card for my wireless to work, which is the only reason I went with huge26 to begin with. Is it possible there's a kernel difference between these two that may throw the mouse into orbit?
That maybe the case, The 2.6 kernels use a different mouse device than the 2.4's. The 2.4's use devfs to create all the devices in the /dev directory, while 2.6's now uses udev and hotplug to create the devices in the /dev directory.
I also have an entry in my /etc/X11/xorg.conf file to support the usb mouse, also support the scroll button:
Code:
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
# By default we will add support for a usb mouse, since a usb mouse can be
# added to a system after bootup, add support now will guarantee it will work
# when the device is attached.
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
I wonder if putting the entry in the /etc/X11/xorg.conf file may make it a bit more stable.
Nope, this hasn't worked either. The mouse still fails to select some buttons part of the time. I even tried killing the gpm daemon, but still no luck.
I'm about to head to sleep, so I'll post my xorg tomorrow. However, my mouse section looks just like yours, but it's a Mouse0 instead of a Mouse1, which shouldn't matter.
The touchpad works the same as the mouse. When the mouse fails, I try the touchpad (both are enabled at the same time), and I still can't click on the spots that were unclickable with the usb mouse.
Another update; I tried a Slax CD, and while the mouse wasn't as troublesome as it was in my Slack install, it did periodically have the same symptoms, but never to the point that everything stopped working. Oftentimes, I'd open an application, and I couldn't close it without using alt+F4. However, in Slax I could still get to the "start" menu, but eventually everything stops working with Slackware.
It's definitely a hardware issue; I'm having the same problems with WinXP. That's Slack, Slax, and WinXP. Definitely has to be my mouse. It seems that once the usb mouse starts acting up, the garbage it passes to the mouse device messes up the laptop touchpad for a bit. Eventually, using the touchpad will restabilize itself.
So good news is Slack has another chance. Bad news is I need to buy another mouse. The mouse is pretty old, and has taken a beating, so it's probably just its time.
Thanks everyone for your help, but it looks like I solved this one.
Yep, just gave it another try. It appears my theory is correct. My USB mouse was interfering with my touchpad. I disconnected it, and reinstalled Slack 11. Everything works just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.