From: Vojtech Pavlik <vojtech@suse.cz>
To: Emmeran Seehuber <rototor@rototor.de>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>, linux-kernel@vger.kernel.org
Subject: Re: PS/2 Mouse does no longer work with kernel 2.6 on a laptop
Date: Mon, 16 Feb 2004 15:36:17 +0100 [thread overview]
Message-ID: <20040216143617.GA959@ucw.cz> (raw)
In-Reply-To: <200402161334.43583.rototor@rototor.de>
On Mon, Feb 16, 2004 at 01:34:43PM +0000, Emmeran Seehuber wrote:
> On Sunday 15 February 2004 15:28, Dmitry Torokhov wrote:
> [...]
> >
> > I see that the kernel correctly identifies both devices so I suspect there
> > could be a problem with your setup. Could you also post your XF86Config
> > and tell me the the options you are passing to GPM, please?
> What I forgot to mention: cat /dev/input/mouse1 gives me some garbage as soon
> as I move on the trackpad. But cat /dev/input/mouse0 gives me nothing, so I
> don't think that this is a userspace configuration problem. The kernel seems
> to get no input from the PS/2 mouse at all.
Dmitry, this looks like either MUX or PassThrough problem.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-02-16 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 23:44 PS/2 Mouse does no longer work with kernel 2.6 on a laptop Emmeran Seehuber
2004-02-13 7:03 ` Dominik Kubla
2004-02-13 7:15 ` H. Peter Anvin
2004-02-13 7:23 ` Dmitry Torokhov
2004-02-13 20:20 ` Dominik Kubla
2004-02-14 9:28 ` Emmeran Seehuber
2004-02-14 17:05 ` Dmitry Torokhov
2004-02-15 14:25 ` Emmeran Seehuber
2004-02-15 15:28 ` Dmitry Torokhov
2004-02-15 19:32 ` Emmeran Seehuber
2004-02-16 13:34 ` Emmeran Seehuber
2004-02-16 14:36 ` Vojtech Pavlik [this message]
2004-02-17 6:18 ` Dmitry Torokhov
2004-02-17 23:13 ` Emmeran Seehuber
2004-02-17 23:29 ` Dmitry Torokhov
2004-02-18 0:37 ` Emmeran Seehuber
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=20040216143617.GA959@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rototor@rototor.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.