From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Steven N. Hirsch" <shirsch@adelphia.net>, linux-kernel@vger.kernel.org
Subject: Re: Phantom PS/2 mouse persists..
Date: Sun, 3 Dec 2000 16:19:40 -0700 [thread overview]
Message-ID: <20001203161940.A24531@vger.timpanogas.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0012031021580.3253-100000@pii.fast.net> <E142drf-0002yf-00@the-village.bc.nu> <20001203144558.B24353@vger.timpanogas.org>
In-Reply-To: <20001203144558.B24353@vger.timpanogas.org>; from jmerkey@vger.timpanogas.org on Sun, Dec 03, 2000 at 02:45:58PM -0700
On Sun, Dec 03, 2000 at 02:45:58PM -0700, Jeff V. Merkey wrote:
> On Sun, Dec 03, 2000 at 06:27:52PM +0000, Alan Cox wrote:
> > > Unfortunately, 2.2.18pre24 is still convinced that I have a PS/2 mouse
> > > attached to my machine.
> >
> > 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 see it on pre18-23 but pre18-24 seems to be fixed. I need to test with the
> anaconda installer, since I an still using a pre18-23 boot kernel for
> the install.
>
> Jeff
I just tested 2.2.18-24 as a boot kernel with anaconda -- works great --
mouse problem on PS/2 system is nailed. New problem, BTW. With Frame
buffer enabled, a system here with an older S3 video card has some
sickness with the mouse (???). The mouse is a giant 2" x 2" block
of wavy lines.
Jeff
>
> >
> > -
> > 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/
> -
> 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/
-
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-03 22:54 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 [this message]
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
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=20001203161940.A24531@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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®