Re: gpm and X incompatible? (potato)
Mike said:
> Brenda J. Butler wrote:
> > On Mon, Jun 26, 2000 at 02:58:21PM +0200, Kerstin Hoef-Emden wrote:
> > >
> > > Hi John,
> > >
> > > On Sun, 25 Jun 2000, John Anthony Kazos Jr. wrote:
> > >
> > > > Killing gpm (through "gpm -k" and "/etc/init.d/gpm stop") makes the
> > > > mouse work in X and fixes the display problems in the framebuffer.
> > > > Does anyone have any ideas about what could be causing this?
> > >
> > > How does your setup in XF86Config in section Pointer look alike?
> >
> >
> > Hmm, it was my understanding that, yes, gpm and X aren't
> > compatible and you _shouldn't_ try to run them together.
> >
> > That was in slink. I've since upgraded to potato, and noticed that
> > both gpm and X are started in the same runlevel. However, I also
> > have trouble with the X server, and those problems go away
> > when I kill off gpm (and remove it from the rc2.d directory).
> >
> > I've never seen any documentation or announcement saying that gpm
> > and X are now compatible...
>
> Whereas I've always run gpm and X together, and never had a problem with
> them. I've done it with slink, potato, and now woody. In the process I've
> gone through a few different mother board / CPU combos. It would seem that
> whatever the problems with gpm and X cooperating are, they are most
> certainly not consistent.
>
In my expirience, this problem is mouse dependant, on one box I have a
mouse that requires a different protocol under gpm than under X-window but
the mouse will not auto-switch when X-window starts, so I don't run gpm on
that box. On another the mouse works with the same protocol (msc) under
both gpm and X-window, but will not work in X-window if gpm is running, I
use runlevels (starting gpm in runlevel two, stoping gpm in runlevel three
and starting wdm). Mostly I've decided to stop buying cheap mouses.
--
ptw
miscelaneous endeavors
(paul@cvanet.com)
--
ptw
miscelaneous endeavors
(paul@cvanet.com)
Reply to: