The oddest thing I found was after a reconfiguration of XFree4 my mouse
started working again. I then started about modifying my XF86Config back
to the way it was and then my mouse stopped again. So I started taking
out the differences one setting at a time. It turned out to be the
DefaultDepth setting. Setting it to 24 kept my mouse from showing up, but
16 and lower work fine. This is with a 3DFX Voodoo 3, my Matrox G400 at
home is uneffected. Sounds like a bug in the xserver not the kernel or
anything else gpm related.
Of course there probally is more than 1 problem at work here, and gpm
could be one of them.
On Tue, 25 Apr 2000, Adam J. Richter wrote:
> A number of people trying to use gpm with XFree86-4.0 have
> found their mouses not responding. According to a contributed
> patch included with the latest gpm, the problem is that XFree86-4.0
> now relies on SIGIO to detect mouse motion, and the Linux kernel does
> not support SIGIO for FIFO's in the file system, such as /dev/gpmdata.
> The contributed patch works around this problem by using a
> pseudo-terminal for /dev/gpmdata instead of a FIFO in the file system,
> but I think the correct fix is either to implement SIGIO for
> FIFO's in Linux or use unix domain socket in the file system.
> What I would like to know is: is there some reason (such as some
> posix standard or something) why SIGIO does not work on file system
> fifo's, or is it something that nobody has gotten around to impelementing?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:09 EST