public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David B. Stevens" <dsteven3@maine.rr.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Dave Jones <davej@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Nathan <wfilardo@fuse.net>
Subject: Re: Mouse not working with linux-2.5.3-dj4
Date: Mon, 11 Feb 2002 13:47:19 -0500	[thread overview]
Message-ID: <3C6811B7.D5E5A067@maine.rr.com> (raw)
In-Reply-To: <3C647DBC.B0BE0EB@maine.rr.com> <3C65B40F.77DBE5EB@maine.rr.com> <20020210105338.A20425@suse.cz>

Thanks,

I'll reconfigure X to use /dev/input/mouse and give it a spin, since
CONFIG_INPUT_MOUSEDEV is set to y.

Cheers,
  Dave

Vojtech Pavlik wrote:
> 
> On Sat, Feb 09, 2002 at 06:43:11PM -0500, David B. Stevens wrote:
> 
> > Dave,
> >
> > I have followed Vojtech Pavlik's advice and turned on I8042_DEBUG_IO the
> > result of which is attached.
> 
> The mouse looks like it operates just fine from the log. So it seems
> like you still have X or GPM configured to use /dev/psaux, instead of
> /dev/input/mice, and/or didn't enable CONFIG_INPUT_MOUSEDEV.
> 
> > Cheers,
> >   Dave
> >
> >
> >
> > "David B. Stevens" wrote:
> > >
> > > Dave,
> > >
> > > I have a Logitech radio control mouse that refuses to operate.  It is a
> > > PS/2 AUX device.  It appears that the mouse was properly detected
> > > according to the attached system log.  Do you see anything missing or
> > > incorrect in the attached config file?
> > >
> > > Thank you for any assistance that you can provide.
> > >
> > > Cheers,
> > >   Dave
> > >

      reply	other threads:[~2002-02-11 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-09  1:39 Mouse not working with linux-2.5.3-dj4 David B. Stevens
2002-02-09 23:43 ` David B. Stevens
2002-02-10  9:53   ` Vojtech Pavlik
2002-02-11 18:47     ` David B. Stevens [this message]

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=3C6811B7.D5E5A067@maine.rr.com \
    --to=dsteven3@maine.rr.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    --cc=wfilardo@fuse.net \
    /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