From nobody@FreeBSD.ORG  Mon Sep  4 16:56:33 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id A08AA37B43E; Mon,  4 Sep 2000 16:56:33 -0700 (PDT)
Message-Id: <20000904235633.A08AA37B43E@hub.freebsd.org>
Date: Mon,  4 Sep 2000 16:56:33 -0700 (PDT)
From: shurd@sk.sympatico.ca
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Keyboard driver problems with PS/2 Model 95 (MCA)
X-Send-Pr-Version: www-1.0

>Number:         21042
>Category:       i386
>Synopsis:       [kbd] Keyboard driver problems with PS/2 Model 95 (MCA)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    mdodd
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 04 17:00:01 PDT 2000
>Closed-Date:    Sun Oct 23 18:25:45 GMT 2005
>Last-Modified:  Sun Oct 23 18:25:45 GMT 2005
>Originator:     Stephen Hurd
>Release:        4.1-Release
>Organization:
Becquet's Custom Programming
>Environment:
N/A
>Description:
When the keyboard driver is loaded on a PS/2 Model 95 (Tried two of them) the keyboard is no longer sane...   The keyboard works fine otherwise.  Tried with about seven good keyboards.  Tried with newest snapshot also - same problem.  While I'm here I might as well wish for MCA support for the DEC 212 NIC.
>How-To-Repeat:
Try installing on a PS/2 Model 95 (I don't have any other PS/2's available for testing)
>Fix:
someone around here said "mumble mumble mumblity A20 Line mumble mumble Micro Channel" if that helps any :-)

>Release-Note:
>Audit-Trail:

From: Andy Farkas <andyf@speednet.com.au>
To: shurd@sk.sympatico.ca
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: i386/21042: Keyboard driver problems with PS/2 Model 95 (MCA)
Date: Tue, 5 Sep 2000 18:19:29 +1100 (EST)

 > Try installing on a PS/2 Model 95 (I don't have any other PS/2's
 > available for testing)
 
 I have one of these systems and saw exactly what you describe.  The
 solution I came up with was:
 
 device          atkbd0  at atkbdc? irq 1 flags 0x3
 
 and recompile kernel.  See LINT for flag decriptions.
 
 --
  
  :{ andyf@speednet.com.au
   
         Andy Farkas
     System Administrator
    Speednet Communications
  http://www.speednet.com.au/
   
 
 
 
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Tue Sep 5 02:01:57 PDT 2000 
State-Changed-Why:  
Does Andy's suggestion work for you?  Please be sure to 
send your follow-up to <freebsd-gnats-submit@freebsd.org>, 
preserving the Subject line of this e-mail message. 


Responsible-Changed-From-To: freebsd-bugs->yokota 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Tue Sep 5 02:01:57 PDT 2000 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21042 
Responsible-Changed-From-To: yokota->mdodd 
Responsible-Changed-By: sheldonh 
Responsible-Changed-When: Thu Sep 7 00:25:38 PDT 2000 
Responsible-Changed-Why:  
As per Matthew's feedback, he should be assigned all MCA specific 
stuff. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21042 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Sun Oct 23 18:25:09 GMT 2005 
State-Changed-Why:  
Feedback timeout (>1 year). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21042 
>Unformatted:
