LKML Archive on
help / color / mirror / Atom feed
From: Pavel Machek <>
To: Nicholas Berry <>,,
Subject: Re: Odd keyboard related crashes.
Date: Sun, 7 Oct 2001 09:23:52 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>
In-Reply-To: <>; from Nicholas Berry on Fri, Oct 05, 2001 at 10:42:16AM -0400


> >>> Ian Stirling <> 10/05/01 05:01AM >>>
> >I'm running 2.4.10, and the ps/2 keyboard came out of it's socket.
> >On plugging back in, all worked fine, until 10 seconds later there was a
> >crash. (the keyboard worked after being plugged in)
> >No oops, just a reboot.
> >Thinking this must just have been a wierd coincidence, after the system
> >came back up, I tried it again, and again it crashed a few seconds afterwards.
> >It doesn't seem to want to do this again though.
> When the keyboard is powered up (or plugged in), it goes through a self test, and reports the status back to the PC. Normally, a start up dialogue takes place between the PC and the keyboard at this point.
> That's fine when you boot your PC, but if you unplug then re-plug the keyboard, the PC will be sent data it's really not expecting, and the BIOS will be very confused.
> If you ever want to switch a keyboard between PCs, make sure you leave power supplied to it at all times.

BIOS is not alive enough at the time linux boots. This can't be BIOS
I'm "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at

  reply	other threads:[~2001-10-07 20:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05 14:42 Nicholas Berry
2001-10-07  7:23 ` Pavel Machek [this message]
2001-10-08 15:18   ` Eric W. Biederman
2001-10-08 16:21     ` Ian Stirling
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09 10:51 Nicholas Berry
2001-10-09 16:28 ` James Simmons
2001-10-09 16:02   ` Daniel Egger
     [not found] <>
2001-10-05 21:24 ` Ian Stirling
2001-10-05  9:17 Thomas Foerster
2001-10-05  9:01 Ian Stirling

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Odd keyboard related crashes.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).