From: jfannin@gmail.com (Joseph Fannin)
To: Harald Dunkel <harald.dunkel@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12.5: psmouse mouse detection doesn't work
Date: Sun, 21 Aug 2005 01:26:10 -0400 [thread overview]
Message-ID: <20050821052610.GD13127@nineveh.rivenstone.net> (raw)
In-Reply-To: <4308062F.7080208@t-online.de>
On Sun, Aug 21, 2005 at 06:42:23AM +0200, Harald Dunkel wrote:
> Hi folks,
>
> At boot time my Logitech mouse is detected as
>
> I: Bus=0011 Vendor=0002 Product=0001 Version=0000
> N: Name="PS/2 Generic Mouse"
> P: Phys=isa0060/serio1/input0
> H: Handlers=event1 ts0 mouse0
> B: EV=7
> B: KEY=70000 0 0 0 0
> B: REL=3
>
> After manually reloading psmouse I get the expected
>
> I: Bus=0011 Vendor=0002 Product=0002 Version=0049
> N: Name="PS2++ Logitech Mouse"
> P: Phys=isa0060/serio1/input0
> H: Handlers=event1 ts0 mouse0
> B: EV=7
> B: KEY=f0000 0 0 0 0
> B: REL=3
>
> Using psmouse_noext=1 at boot time does not help.
>
> How comes that this doesn't work on the first run?
>
> I asked this more than a year ago, and somebody posted
> a fix, but obviously it wasn't accepted.
>
> What needs to be done to fix this?
If psmouse is a module, you'd need to pass proto=bare as a module
parameter rather than on the kernel command line. Check `modinfo
psmouse`.
Are you sure proto=imps hasn't found its way into
/etc/modprobe.conf or so? I could imagine a distribution shipping
this way.
--
Joseph Fannin
jfannin@gmail.com
/* So there I am, in the middle of my `netfilter-is-wonderful'
talk in Sydney, and someone asks `What happens if you try
to enlarge a 64k packet here?'. I think I said something
eloquent like `fuck'. - RR */
prev parent reply other threads:[~2005-08-21 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-21 4:42 Harald Dunkel
2005-08-21 5:16 ` Michael Krufky
2005-08-21 14:03 ` Harald Dunkel
2005-08-21 5:19 ` Dmitry Torokhov
2005-08-21 5:26 ` Joseph Fannin [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=20050821052610.GD13127@nineveh.rivenstone.net \
--to=jfannin@gmail.com \
--cc=harald.dunkel@t-online.de \
--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®