From owner-freebsd-bugs  Sat Mar 22 23:20:05 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA27560
          for bugs-outgoing; Sat, 22 Mar 1997 23:20:05 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA27554;
          Sat, 22 Mar 1997 23:20:02 -0800 (PST)
Resent-Date: Sat, 22 Mar 1997 23:20:02 -0800 (PST)
Resent-Message-Id: <199703230720.XAA27554@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org,
        Received:(from nobody@localhost) by.freefall.freebsd.org.id.XAA27408;Sat; (8.8.5/8.8.5);,
        22 Mar 1997 23:12:10.-0800 (PST)
Message-Id: <199703230712.XAA27408@freefall.freebsd.org>
Date: Sat, 22 Mar 1997 23:12:10 -0800 (PST)
From: hendrik@hg.com
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: kern/3067: Keyboard does not fonction after booting 2.2-RELEASE
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         3067
>Category:       kern
>Synopsis:       Keyboard does not fonction after booting 2.2-RELEASE
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 22 23:20:01 PST 1997
>Last-Modified:
>Originator:     Hendrik Groeneveld
>Organization:
>Release:        2.2-RELEASE
>Environment:
FreeBSD klatu.hg.com 2.2-RELEASE FreeBSD 2.2-RELEASE #0: Sun Mar 16 07:47:59 GMT 1997     jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC  i386
>Description:
When booting from the install floppy the keyboard does not function properly. The keyboard does work properly in UserConfig but is not functional when sysinstall executes. In sysinstall keys seem to produce random results. When booting with the -v option the system reports a keyboard reset failure. I tried setting the console flags to 0x10 but it didn't help. I have not found a work-around for this problem.

The problem occurs on a Vega 486 motherboard that worked very well with 2.1.5-RELEASE.
>How-To-Repeat:
Boot the kernel from the installation floppy (boot.flp).
>Fix:

>Audit-Trail:
>Unformatted: