From: "James E. Jennison" <james.jennison@digital-creationsonline.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: ImExPS/2 status
Date: Wed, 19 Oct 2005 06:45:49 -0700 [thread overview]
Message-ID: <200510190645.49426.james.jennison@digital-creationsonline.com> (raw)
In-Reply-To: <200510190030.54715.dtor_core@ameritech.net>
On Tuesday 18 October 2005 22:30, you wrote:
<Cut to save space and not be so long>
...
...
...
> > I have included the results from what dmesg displayed when I connected
> > the mouse to the computer, as well as some of the output from
> > /var/log/messages:
> >
> > input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
> >
> > Oct 18 06:47:25 scooby gpm[18741]: Started gpm successfully. Entered
> > daemon mode.
> > Oct 18 06:48:46 scooby kernel: psmouse.c: bad data from KBC - timeout
> > Oct 18 06:48:47 scooby hal.hotplug[22794]: DEVPATH is not set
> > Oct 18 06:48:47 scooby hal.hotplug[22836]: DEVPATH is not set
> > Oct 18 06:48:47 scooby kernel: input: PS/2 Generic Mouse on
> > isa0060/serio1
>
> So you start without a mouse plugged in and still it detects a mouse?
No, in both instances, the mouse was already plugged in.
> > Oct 18 06:52:54 scooby hal.hotplug[2047]: DEVPATH is not set
> > Oct 18 06:52:55 scooby hal.hotplug[2133]: DEVPATH is not set
> > Oct 18 06:52:55 scooby kernel: input: ImExPS/2 Generic Explorer Mouse on
> > isa0060/serio1
>
> And here you plug the mouse, right?
>
> > Oct 18 06:54:28 scooby hal.hotplug[5846]: DEVPATH is not set
> > Oct 18 06:54:28 scooby hal.hotplug[5884]: DEVPATH is not set
> > Oct 18 06:54:29 scooby kernel: input: PS/2 Generic Mouse on
> > isa0060/serio1
next prev parent reply other threads:[~2005-10-19 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 0:11 James E. Jennison
2005-10-19 5:30 ` Dmitry Torokhov
2005-10-19 13:45 ` James E. Jennison [this message]
[not found] <4Z9Qz-7an-5@gated-at.bofh.it>
2005-10-19 3:52 ` Robert Hancock
2005-10-19 4:48 ` James E. Jennison
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=200510190645.49426.james.jennison@digital-creationsonline.com \
--to=james.jennison@digital-creationsonline.com \
--cc=dtor_core@ameritech.net \
--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
all inboxes | Powered by JetHome®