Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
02-10-2013, 02:59 AM
|
#1
|
|
LQ Newbie
Registered: Jan 2013
Location: Vancouver, Canada
Distribution: Slackware 14.0
Posts: 25
Rep: 
|
"X" does not recognize my PS/2 Mouse under Slackware 14.0
Under Slackware 13.37, "X" recognized my PS/2 Mouse.
Under Slackware 14.0 , "X" does not recognize my PS/2 Mouse.
I answered "PS/2" for Mouse in "Setup" when I installed 14.0
What's up?
|
|
|
|
02-10-2013, 03:49 AM
|
#2
|
|
Member
Registered: Apr 2009
Location: Oz
Distribution: slackware64-14.0
Posts: 630
Rep: 
|
The question in setup is for gpm which gives you the mouse on a text console, it doesn't have anything to do with X unless it blocks X from the mouse.
Now, X has a nice log that it generates on start up you can find it in /var/log/Xorg.0.log if you paste that to http://pastebin.com/ we can have a look and offer some suggestions.
|
|
|
|
02-10-2013, 06:37 AM
|
#3
|
|
LQ Newbie
Registered: Aug 2012
Location: Ryomgård, Danmark
Distribution: Slackware
Posts: 24
Rep: 
|
Maybe the module psmouse is not loaded:
Se section about PS/2 mouse support in /etc/rc.d/rc.modules-3.2.29.
|
|
|
|
02-10-2013, 07:18 AM
|
#4
|
|
Member
Registered: Apr 2005
Distribution: Debian, Slackware
Posts: 948
|
Quote:
Originally Posted by wildwizard
The question in setup is for gpm which gives you the mouse on a text console, it doesn't have anything to do with X unless it blocks X from the mouse.
|
In my limited experience of gpm, it can do exactly that. I remember having to disable it 13.37 due to this and haven't enabled it for any install since.
|
|
|
|
02-10-2013, 09:01 AM
|
#5
|
|
Senior Member
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 2,830
|
Quote:
Originally Posted by caravel
In my limited experience of gpm, it can do exactly that. I remember having to disable it 13.37 due to this and haven't enabled it for any install since.
|
The description of the gpm package says :
Quote:
|
NOTE: This program may cause problems when you start X on systems that do not use a serial mouse. If you get an 'unable to open mouse device' error from X, disable /etc/rc.d/rc.gpm.
|
But reading this it seems that a PS/2 mouse be a serial one, so I'm not sure that could be the cause in your case.
Now for the OP: you could have another problem, in that case as suggested by wildwizard please exhibit your X log.
|
|
|
|
02-10-2013, 05:16 PM
|
#6
|
|
Slackware Maintainer
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 635
|
Quote:
Originally Posted by Didier Spaier
But reading this it seems that a PS/2 mouse be a serial one, so I'm not sure that could be the cause in your case.
|
While technically a PS/2 mouse is a serial mouse, when talking about a "serial mouse" we mean one that connects to a /dev/ttyS* device.
As noted in another thread, the problem in this particular case is likely to be a complete absence of kernel modules on the machine (at least for the running kernel).
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 02:36 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|