From: "Udo A. Steinberg" <sorisor@Hell.WH8.TU-Dresden.De>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PS/2 Mouse/Keyboard conflict and lockup
Date: Thu, 08 Feb 2001 16:20:39 +0100 [thread overview]
Message-ID: <3A82B947.BA4368DE@Hell.WH8.TU-Dresden.De> (raw)
In-Reply-To: <E14Qm1u-0002nf-00@the-village.bc.nu>
Alan Cox wrote:
>
> > I'm not sure whether this is related to the ominous ps/2 mouse bug
> > you have been chasing, but this problem is 100% reproducible and
> > very annoying.
>
> It isnt but it might be related to which 2.2.19pre you are running (if any)
No, at that time I was running 2.4.1-ac5.
> Does downgrading the bios fix it. If so then I suspect you need to talk to
> the BIOS vendor. You might find that turning off USB legacy keyboard/mouse
> emulation helps too
Downgrading the Bios does fix it, but that just shadows the ACPI bugs that
cause the problem. With 1003 + ACPI, mouse and keyboard both work,
but I've seen spurious scancode problems and keyboard weirdness that I
reported to lkml a week or two ago. 1005D + ACPI completely mess up PS/2
mouse and keyboard and lock them up after a while.
The solution is not to use ACPI until that is fixed. It appears that without
ACPI everything is working perfectly.
-Udo.
-
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:[~2001-02-08 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 2:35 Udo A. Steinberg
2001-02-08 3:42 ` Udo A. Steinberg
2001-02-08 7:59 ` Peter Horton
2001-02-08 11:37 ` Pierre Rousselet
2001-02-08 8:02 ` Alan Cox
2001-02-08 12:08 ` Ian Stirling
2001-02-08 15:20 ` Udo A. Steinberg [this message]
2001-02-12 22:08 Mark Swanson
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=3A82B947.BA4368DE@Hell.WH8.TU-Dresden.De \
--to=sorisor@hell.wh8.tu-dresden.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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®