From: "Linux Kernel Developer" <linux_developer@hotmail.com>
To: "Steven N. Hirsch" <shirsch@adelphia.net>,
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>
Subject: Re: Phantom PS/2 mouse persists..
Date: Sun, 3 Dec 2000 20:47:00 -0500 [thread overview]
Message-ID: <OE40Njy1jCzc3UspbP200006074@hotmail.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012031739360.3253-100000@pii.fast.net>
----- Original Message -----
From: "Steven N. Hirsch" <shirsch@adelphia.net>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>; <linux-kernel@vger.kernel.org>
Sent: Sunday, December 03, 2000 5:42 PM
Subject: Re: Phantom PS/2 mouse persists..
> On Sun, 3 Dec 2000, Jeff V. Merkey wrote:
>
> > > On Sun, Dec 03, 2000 at 06:27:52PM +0000, Alan Cox wrote:
> > > >
> > > > I've fixed the major case. I can see no definitive answer to the
other ghost
> > > > PS/2 stuff (except maybe USB interactions). I take it like the
others 2.4test
> > > > also misreports a PS/2 mouse being present.
> > > >
> > > > Anyway I think its no longer a showstopper for 2.2.18. Someone with
an affected
> > > > board can piece together the picture
>
> > I just tested 2.2.18-24 as a boot kernel with anaconda -- works great --
> > mouse problem on PS/2 system is nailed.
>
> <sigh> I always seem to own the wierd hardware. I agree the mouse
> mis-detection isn't a showstopper - just damn annoying.
>
> FWIW, USB isn't compiled into the kernel in question.
>
Definately could be your hardware. I once saw a 486 board (PcChips M571
I think) which would report a PS/2 mouse even though the port didn't even
exist on the motherboard. This problem showed up on all versions of Win9x.
>From what I could tell it appeared as if the BIOS had support for the PS/2
mouse port but the port pins themself had not been saudered onto the board
and for some reason the board alway thaught it had a PS/2 mouse and reported
as so to Windows.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-04 2:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-03 15:24 Steven N. Hirsch
2000-12-03 18:27 ` Alan Cox
2000-12-03 21:45 ` Jeff V. Merkey
2000-12-03 23:19 ` Jeff V. Merkey
2000-12-03 22:42 ` Steven N. Hirsch
2000-12-04 0:44 ` Jeff V. Merkey
2000-12-04 3:52 ` Steven N. Hirsch
2000-12-04 1:47 ` Linux Kernel Developer [this message]
2000-12-03 23:49 ` Daniel Roesen
2000-12-04 0:53 ` Jeff V. Merkey
2000-12-04 3:51 ` Steven N. Hirsch
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=OE40Njy1jCzc3UspbP200006074@hotmail.com \
--to=linux_developer@hotmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shirsch@adelphia.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
all inboxes | Powered by JetHome®