From: Michael Ben-Gershon <mybg@netvision.net.il>
To: linux-kernel@vger.kernel.org
Subject: Keyboard and PS/2 mouse lockups
Date: Sun, 26 Aug 2001 15:58:03 +0300 [thread overview]
Message-ID: <3B88F25B.8AF25EF9@netvision.net.il> (raw)
I know this is not new, but I feel that my input is worth
noting.
I recently upgraded my hardware from a Tyan board with a PII 333
to an ASUS P4T with a P4 1.5G.
Running either kernel 2.2.19 or 2.4.6, 2.4.7, 2.4.8, 2.4.9, I get
a serious conflict between the PS/2 mouse and the keyboard. If the
mouse is plugged into the machine and generates any mouse event (by
moving it or clicking) the keyboard is completely locked up. I am
using a KVM (=kbd-video-mouse) splitter box, and the strange thing
is that the box will respond to a 'double scroll lock' keypress to
switch from one machine to the next, but if the kbd is locked up by
the above trouble it will not respond at all, and the manual switching
button must be used. This is very strange, as the 'double scroll lock'
action works even if the currently selected machine is switched off!
I get the lockup whether or not gpm is running, and even if the
kernel is built with no PS/2 mouse support. If the mouse is removed
before the trouble is triggered, all is OK.
All of the above is using the console. I can run X from a remote
machine - this is what I have usually done anyway, for a number
of local reasons. I can also telnet into the machine. But the
console keyboard is totally, utterly dead.
For what it is worth, the problem does not occur if the machine
is booted up into DOS rather than linux, so it cannot be purely
a hardware problem, but must be s combined hardware/linux kernel
problem.
Any ideas?
Michael Ben-Gershon
mybg@netvision.net.il
next reply other threads:[~2001-08-26 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 12:58 Michael Ben-Gershon [this message]
2001-08-27 20:48 ` Keyboard and PS/2 mouse lockups Michael Ben-Gershon
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=3B88F25B.8AF25EF9@netvision.net.il \
--to=mybg@netvision.net.il \
--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