On Wed, 2004-03-24 at 09:26, Ole-Egil Hvitmyren wrote:
> Michel Dänzer wrote:
> > On Wed, 2004-03-24 at 03:02, Viktor Rosenfeld wrote:
> >
> >>Minor gotcha: I switched the X mouse device from /dev/gpmdata (I had gpm
> >>repeat mouse events) to /dev/input/mice, because I remember reading that
> >>w
Michel Dänzer wrote:
On Wed, 2004-03-24 at 03:02, Viktor Rosenfeld wrote:
Minor gotcha: I switched the X mouse device from /dev/gpmdata (I had gpm
repeat mouse events) to /dev/input/mice, because I remember reading that
with the new 2.6 kernel more than one processes can listen to mouse
events
On Wed, 2004-03-24 at 03:29, Viktor Rosenfeld wrote:
>
> Michel Dänzer wrote:
>
> > > the mouse will not work until I move the pad a couple of seconds.
> > >
> > > Anybody experiencing the same problem?
> >
> > No. What protocol do you use? This might be expected behaviour with
> > "auto".
>
>
Hi,
Michel Dänzer wrote:
> > and because udev did not create the gpmdata device node. Now,
> > the mouse will not work until I move the pad a couple of seconds.
> >
> > Anybody experiencing the same problem?
>
> No. What protocol do you use? This might be expected behaviour with
> "auto".
Act
On Wed, 2004-03-24 at 03:02, Viktor Rosenfeld wrote:
>
> Minor gotcha: I switched the X mouse device from /dev/gpmdata (I had gpm
> repeat mouse events) to /dev/input/mice, because I remember reading that
> with the new 2.6 kernel more than one processes can listen to mouse
> events
/dev/input/m
Hi,
thanks to all that replied. It works now.
Minor gotcha: I switched the X mouse device from /dev/gpmdata (I had gpm
repeat mouse events) to /dev/input/mice, because I remember reading that
with the new 2.6 kernel more than one processes can listen to mouse
events and because udev did not crea
6 matches
Mail list logo
