View previous topic :: View next topic |
Author |
Message |
selig Guru


Joined: 31 Jul 2005 Posts: 425 Location: Prague, Czech Republic
|
Posted: Fri Oct 20, 2006 9:46 am Post subject: PS/2 mouse timeouts in X.org 7.1 [SOLVED] |
|
|
I upgraded my xorg-x11 from 7.0-r1 to 7.1 yesterday, and my PS/2 mouse is working unreliably. Every once in a while it stops and starts working again only after a second or so. Alternatively, it "loses synchronization" and goes crazy until I click a button on it.
I am getting errors from the kernel psmouse driver too:
Code: |
psmouse.c: bad data from KBC - timeout
psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away.
|
This would suggest something wrong is either with the mouse or controller, but when I tried just "cat /dev/input/mouse0" and "used" it for a few minutes, no errors in the kernel log appeared. I have also tried booting into windoze and the mouse is working correctly there.
I did nothing other with my system than updated my xorg-x11, so I would say it is the cause of my troubles.
Last edited by selig on Sat Oct 21, 2006 9:39 am; edited 1 time in total |
|
Back to top |
|
 |
halfgaar l33t


Joined: 22 Feb 2004 Posts: 781 Location: Netherlands
|
Posted: Fri Oct 20, 2006 1:26 pm Post subject: |
|
|
It may not be a direct answer to your question, but is your mouse USB, or does it have USB functionality (in case you connected it with a USB-to-PS2 converter)? In that case, you could try the "evdev" protocol (It may also work for PS2, I don't know). It requires some configuration (kernel configuration for one) and investigating. With evdev, I can use all of the 8 buttons on my Logitech MX500 mouse.
If evdev is not an option for you, or if it doesn't solve the problem, I have no idea what it could be. Can you give some more info about what kind of mouse it is, and show the mouse section in xorg.conf? _________________ Linux backups the right way.
Get surround sound working. |
|
Back to top |
|
 |
selig Guru


Joined: 31 Jul 2005 Posts: 425 Location: Prague, Czech Republic
|
Posted: Fri Oct 20, 2006 6:25 pm Post subject: |
|
|
Thank you for your advice, it is a standard PS/2-only mouse, a pretty old one. Genius NetMouse PRO. Nothing fancy in my config:
Code: |
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mouse0"
Option "ZAxisMapping" "4 5"
EndSection
|
When I try "cat"ing the evdev devices, I get input from it on evdev2. I am going to try setting it as an evdev input device, and post an update then. I hope it will work with evdev. |
|
Back to top |
|
 |
selig Guru


Joined: 31 Jul 2005 Posts: 425 Location: Prague, Czech Republic
|
Posted: Fri Oct 20, 2006 7:14 pm Post subject: |
|
|
I have successfully set up the mouse as an evdev device, but with the same results. It worked for a while and then it started malfunctioning and this appeared in dmesg:
Code: |
psmouse.c: bad data from KBC - timeout
psmouse.c: Mouse at isa0060/serio1/input0 lost synchronization, throwing 3 bytes
away.
psmouse.c: resync failed, issuing reconnect request
|
So it is the same message again. I am using my Wacom Graphire bluetooth tablet mouse as an emergency solution, because the malfunctioning PS/2 mouse is too dangerous (it already messed up my desktop a few times). Maybe I will have to buy a new mouse for USB... I do not want to downgrade my Xorg, because the tablet is working better in it than in 7.0. |
|
Back to top |
|
 |
halfgaar l33t


Joined: 22 Feb 2004 Posts: 781 Location: Netherlands
|
Posted: Fri Oct 20, 2006 9:44 pm Post subject: |
|
|
The tablet works OK, and the mouse doesn't? That kind of implies that there's something wrong with the mouse. But if there were, why didn't the problem occur with X.org 7.0, or in Windows?
I think this is a bug in X.org. It's kind of a difficult one to track down, but I think it's worthy of a bug report at www.x.org or xorg.freedesktop.org. _________________ Linux backups the right way.
Get surround sound working. |
|
Back to top |
|
 |
selig Guru


Joined: 31 Jul 2005 Posts: 425 Location: Prague, Czech Republic
|
Posted: Sat Oct 21, 2006 7:56 am Post subject: |
|
|
I have just found out that it indeed is a hardware problem, so I have to buy a new mouse. I do not know why it appeared just now, but it must have been a coincidence. But thank you for your help and pointing out the evdev mouse option, I think I am going to need it since I would like to buy the Logitech MX revolution mouse. I hope it will serve me for so long as my old NetMouse PRO.  |
|
Back to top |
|
 |
halfgaar l33t


Joined: 22 Feb 2004 Posts: 781 Location: Netherlands
|
Posted: Sat Oct 21, 2006 10:47 am Post subject: |
|
|
Another small tip: use the logitech-applet. If you don't, the optical sensor uses it's default CPI (counts per inch). My MX500 has 400 default (as does any mouse), and with the applet I can set it to 800. This makes the mouse cursor move much faster, and therefore, you can reduce the amount of software acceleration. If at first this doesn't sound appealing, consider that the CPI of mice haven't changed since the 640x480 era (I believe). When using 1280x960 or something similair, a faster responding mouse is convinient.
And, with the tool I can disable the "cruise control" buttons (cruise control means they act as scroll-up and scroll-down), and get them to work as autonomous buttons. _________________ Linux backups the right way.
Get surround sound working. |
|
Back to top |
|
 |
Doogman Apprentice


Joined: 24 Sep 2004 Posts: 244
|
Posted: Sat Oct 21, 2006 11:24 am Post subject: |
|
|
Actually you want to use "lomoco" as the logitech_applet is a dead project. I went through setting-up my MX518 here:
https://forums.gentoo.org/viewtopic-t-502422-highlight-.html
You better search a bit on the revolution. I'm not sure if that funky mouse wheel is fully supported in Linux. |
|
Back to top |
|
 |
selig Guru


Joined: 31 Jul 2005 Posts: 425 Location: Prague, Czech Republic
|
Posted: Sat Oct 21, 2006 5:30 pm Post subject: |
|
|
Thank you for the info. I have decided on buying a G7 rather than Revolution, since the former has 2000DPI sensor and the latter only 800, for similar price. |
|
Back to top |
|
 |
|