Messages in this thread Patch in this message | | | From | volodya@mindspri ... | Date | Sat, 29 Jul 2000 10:34:27 -0400 (EDT) | Subject | [patch] Re: ps/2 mouse (synaptics touchpad) |
| |
I found out what was wrong. Turns out someone introduced "PS/2 reconnect code" right about that time. This touches both 2.2.x and 2.4.x kernels. I put in a line to report when reconnect happens - and know what ? - my notebook reported several such events..
So the fix is to remove this code entirely - and then _both_ gpm and Xserver work. (and no Xserver couldn't decipher bogus data either. Apparently after each "reconnect" the kernel attempted to reset the mouse - oh my..).
Now it completely evades me why this was not marked as an "experimental and dangerous" option, since in most manuals I read PS/2 bus is clearly marked as not supporting hot-plugging.
The patch is quite simple:
--- pc_keyb.c.orig Sat Jul 29 09:53:42 2000 +++ pc_keyb.c Sat Jul 29 10:02:50 2000 @@ -402,13 +402,14 @@ } mouse_reply_expected = 0; } - else if(scancode == AUX_RECONNECT){ +#if 0 + else if((scancode == AUX_RECONNECT)){ queue->head = queue->tail = 0; /* Flush input queue */ aux_write_ack(AUX_ENABLE_DEV); /* ping the mouse :) */ return; } - +#endif add_mouse_randomness(scancode); if (aux_count) { int head = queue->head;
I leave it to the person who needs to hotplug his PS/2 devices so desperately to introduce an option in kernel configuration to enable his code.
Vladimir Dergachev PS And by the way gpm is maintained again.. I think I am using the June version.
On Fri, 28 Jul 2000, Andrew McNabb wrote:
> I had the exact same error with 2.2.16 (I think that something happened > after 2.2.15). The problem happily disappeared when I removed gpm, > which is currently unmaintained anyway. Aside from being unable to > change my Synaptics options (which gpm screwed up, too), my system > is much happier now. > > > On Fri, 28 Jul 2000 volodya@mindspring.com wrote: > > > > > Does someone have hints on the following problem: > > > > for some reason, my synaptics touchpad generates a lot of bad (or > > unrecognized) packets in 2.4.0-test4 - and works great with 2.2.14. > > Basically every few seconds of mouse movement gpm reports a ton of > > unrecognized data then another few seconds it works fine. I have compared > > the code with 2.2.14 and can't really see any that produces this. (I tried > > commenting out the toshiba and compaq fixes.. no change).. > > > > I am using gpm version 1.19.3 > > > > thank you > > > > Vladimir Dergachev > > > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majordomo@vger.rutgers.edu > > Please read the FAQ at http://www.tux.org/lkml/ > > > > ---------------------------------------------- > Andrew McNabb > Argus Systems Group > amcnabb@argus-systems.com > ---------------------------------------------- > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |