Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
How do you have the 'X' configured for your system? When you first installed you would have been given the choice to setup your mouse. If you want to re-run the script you can use 'pkgtool'. Which mouse setting, 'bare' or 'ms'?
Well, indeed, I configured the mouse in instalation process (with Microsoft protocol, the same I use in Slackware 12.2). After, I used the #xorgsetup, but without sucess. The X start normally, but mouse stay freeze.
I found the same problem in other area of this forum:
So, lsmod show many loaded modules, of course, and sermouse (after edit rc.modules to include it). If you looking for a module conflict, psmouse (or other modules used by mice) is not loaded in. I dont use/like gpm. So, I dont need it to configure my mouse. If you want a detailed lsmod output, wait my lunch, because I am at work now.
The reason I asked about 'gpm' is that sometimes there can be a conflict. A good test to see if the mouse is working at the console level would be to enable '/etc/rc.d/rc.gpm' then '/etc/rc.d/rc.gpm start' to see if you have the mouse in the console before 'X'. If the mouse functions then you know that 'X' is not configured properly.
Do you see anything in your logs or 'dmesg'? You should be able to use parts of your 12.2 xorg.conf that pertain to the mouse.
I tested my mouse with gpm and it works. As you told, is not a module conflict or something like that, is a X configuration problem. But how solve it?
Well, after read the file log generated by the X (/var/log/), I saw something betrayer:
"AllowEmptyInput" is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled".
That is, I found my problem.
After read the X.conf man page, I discovered that "AllowEmptyInput" is a ServerFlag Option, "on" by default. What is the obvious solution? I set up "AllowEmptyInput" to "off" and, OMG, my mouse worked... strange...
I recieved a secret gift: Each time I pressed one key (keyboard or mouse), I saw triplicate echoes (or double clicks). That shit. Reading documentation again, I discovered another two ServerFlags that must be "off" or X would add, configure and enable devices (three keyboards and two mice?). I confirmed this, after read X log file again.