Serial mouse on Slackware 13
 

Hi there,

I am glad to be here.

My serial mouse was run perfect with Slackware 12.2 (Microsoft protocol and /dev/ttyS0 in /etc/X11/xorg.conf), but now, with Slackware 13.0, I dont know how to setup my serial mouse.

When I started the X Windows System, the arrow freeze.

The mouse-test can detect my mouse on /dev/ttyS0

But it dont work...

I uncommented "modprobe sermouse" in /etc/rc.d/rc.modules, but dont work too...

Who can help me?

Thank you and sorry my english...

cya,

ozeax

Hi,

Welcome to LQ!

Your English is fine.

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'?

To be continue...
 

Hi and thanks,

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:

http://www.linuxquestions.org/questi...36#post3604636

There are a solution, but I dont know how to do it... as I told, I edited the rc.modules to load sermouse module, but dont work. I loaded sermouse module by hand, but dont work too.

Sorry if I am asking in wrong form (:newbie:)

Thank you again,

ozeax

Hi,

What does your 'lsmod' show? Do you have 'gpm' enabled? If so how is it configured?

Hi,

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.

Thx and cya,

ozeax

Hi,

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.

Solved
 

Hi,

Yes, you right.

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.

Complete Solution (/etc/X11/xorg.conf):


Now, all works fine.

Thank you very much for help me.

I see you arround,

ozeax

Hi,

Glad to hear you have your system running.

As the 'OP' you can mark the Thread as [SOLVED] via the 'Thread Tools'. This will aid others when searching.