From owner-freebsd-current  Fri Sep 17  5:46: 4 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8CC0214A0E; Fri, 17 Sep 1999 05:45:56 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id OAA77092;
	Fri, 17 Sep 1999 14:45:08 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199909171245.OAA77092@freebsd.dk>
Subject: Re: Weird syscons keyboard behaviour
In-Reply-To: <199909171241.VAA23111@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Sep 17, 1999 09:41:49 pm"
To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA)
Date: Fri, 17 Sep 1999 14:45:08 +0200 (CEST)
Cc: mpp@FreeBSD.ORG (Mike Pritchard), freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Kazutaka YOKOTA wrote:
> 
> It appears that if you hit the keyboard before (at the boot loader
> prompt or during the kernel is probing devices) or while the keyboard
> driver is being initialized, you may see the problem.

Hmm I've seen the problem where on "loose" the input at the loader prompt
but it has always come back when syscons probes the keyboard.

But I have also seen the other problem exactly two times, and the
keyboard hasn't been touched at all those two times...
I had written it of as a fluke in my screen/keyboard/mouse switchbox...

-Sxren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message