From: Emmeran Seehuber <rototor@rototor.de>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: PS/2 Mouse does no longer work with kernel 2.6 on a laptop
Date: Wed, 18 Feb 2004 00:37:53 +0000 [thread overview]
Message-ID: <200402180037.53614.rototor@rototor.de> (raw)
In-Reply-To: <200402171829.57596.dtor_core@ameritech.net>
On Tuesday 17 February 2004 23:29, Dmitry Torokhov wrote:
> On Tuesday 17 February 2004 06:13 pm, Emmeran Seehuber wrote:
>
> OK, I am lost.. how many pointing devices you physically have?
> 2 or 3? According to the kernel data you have 2 PS/2 devices
>
> and one USB trackball:
> > N: Name="PS2++ Logitech Mouse"
> > P: Phys=isa0060/serio2/input0
> > N: Name="PS/2 Generic Mouse"
> > P: Phys=isa0060/serio4/input0
> > N: Name="Microsoft Microsoft Trackball Explorer®"
> > P: Phys=usb-0000:00:03.2-1/input0
>
> Is this correct? Or you have only 2 devices (one PS/2 and one USB) and it
> is one of those wierd USB legacy emulation troubles. Does it behave better
> if you load USB modules first and only then psmouse?
Sorry, I didn't want to confuse you.
I`ve attached a USB mouse because the PS/2 trackball didn`t work when I was
creating the /proc-output (since I booted without the i????.nomux option).
But I don`t like the USB mouse, I prefer to use the trackball.
The problem is the same: The USB mouse can be attachend/detached any time. It
does hotplug very well. All data I've send you was with the USB mouse
detached. Only when I did the cat /proc/... I didn't want to use the trackpad
and attached the USB mouse ...
Just ignore the USB mouse. It doesn't seem to be related to the problem. And
yes, in this case I had 3 physical devices (trackpad, PS/2 trackball, USB
trackball) attached.
cu,
Emmy
prev parent reply other threads:[~2004-02-17 23:37 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
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 [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=200402180037.53614.rototor@rototor.de \
--to=rototor@rototor.de \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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