public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Ben Clifford <benc@hawaga.org.uk>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.5-dj1 - problem with /dev/input/mice
Date: Sun, 24 Feb 2002 22:27:08 +0100	[thread overview]
Message-ID: <20020224222708.A1814@ucw.cz> (raw)
In-Reply-To: <20020222022329.A3533@suse.cz> <Pine.LNX.4.33.0202241249540.11220-100000@barbarella.hawaga.org.uk>
In-Reply-To: <Pine.LNX.4.33.0202241249540.11220-100000@barbarella.hawaga.org.uk>; from benc@hawaga.org.uk on Sun, Feb 24, 2002 at 01:00:00PM -0800

On Sun, Feb 24, 2002 at 01:00:00PM -0800, Ben Clifford wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> > >  -dj includes a different input layer to Linus' tree, which requires
> 
> I've just moved from Linus 2.5.3 to 2.5.5-dj1.
> 
> I've tried the following both with modules and linked into bzImage.
> 
> I've tried pointing the software at /dev/input/mice and also at /dev/psaux
> which I created as a symlink to /dev/input/mice (to maintain compatibility
> with my working 2.5.3 setup)
> 
> I have a PS/2 mouse.
> 
> I've loaded mousedev.o and psmouse.o
> 
> gpm works. (**1)
> 
> cat /dev/input/mice
> gives random binary spew that looks pretty much like mouse input.
> 
> When I run my Xserver, the mouse pointer doesn't move. If I then kill off
> the Xserver, gpm doesn't work any more and cat/dev/input/mice doesn't
> generate anything any more.
> 
> If I unload psmouse.o and then load it again, I am back to (**1) until I
> load the Xserver again.

That's interesting. It almost looks like if the Xserver messed with the
mouse hardware somehow, which I hope it can't. Does 'dmesg' say anything
relevant?

I can help you find the cause - if you enable I8042_DEBUG_IO in
drivers/input/serio/i8042.h, you'll see all the data coming in and out
to the keyboard/aux controller.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-02-24 21:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-21 23:37 Linux 2.5.5-dj1 - Bug Reports Benjamin Pharr
2002-02-22  1:21 ` Dave Jones
2002-02-22  1:23   ` Vojtech Pavlik
2002-02-23 21:28     ` Pavel Machek
2002-02-24 21:00     ` Linux 2.5.5-dj1 - problem with /dev/input/mice Ben Clifford
2002-02-24 21:27       ` Vojtech Pavlik [this message]
2002-02-24 21:42         ` Ben Clifford
2002-02-24 21:45           ` Vojtech Pavlik
2002-02-28  9:58         ` Pavel Machek
2002-02-22  6:37   ` Linux 2.5.5-dj1 - Bug Reports Nathan Walp
2002-02-28 16:59     ` Nathan Walp
2002-02-28 19:57       ` Benjamin Pharr
2002-02-28 20:47       ` Dave Jones
2002-03-01 18:12     ` Manfred Spraul
2002-02-24 21:02   ` Linux 2.5.5-dj1 - IPv6 not loading correctly Ben Clifford
2002-02-25  6:16     ` Ben Clifford
2002-02-25 21:32       ` Dave Jones
2002-02-25 22:18         ` David S. Miller
2002-02-27 20:23           ` Arnaldo Carvalho de Melo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020224222708.A1814@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=benc@hawaga.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox