From owner-freebsd-hackers  Fri Oct 18 08:50:30 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA02594
          for hackers-outgoing; Fri, 18 Oct 1996 08:50:30 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02586
          for <freebsd-hackers@freebsd.org>; Fri, 18 Oct 1996 08:50:27 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id IAA09841; Fri, 18 Oct 1996 08:50:06 -0700 (PDT)
To: Doug Rabson <dfr@render.com>
cc: Nate Williams <nate@mt.sri.com>,
        "Brian N. Handy" <handy@sag.space.lockheed.com>,
        freebsd-hackers@freebsd.org
Subject: Re: 2.2-961006-SNAP keyboard lockup 
In-reply-to: Your message of "Fri, 18 Oct 1996 09:41:14 BST."
             <Pine.BSF.3.95.961018093945.14906C-100000@minnow.render.com> 
Date: Fri, 18 Oct 1996 08:50:06 -0700
Message-ID: <9839.845653806@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I had this problem and I 'fixed' it by changing from syscons to pcvt.  I
> am *not* using one of those miserable M$ keyboards (we have stacks of them
> here and I hate them).

Hmmm...  (and I like my M$ keyboard, so pbbbblt! :-).  Let me try this
myself, and if it fixes the problem then I can get back to X Inside
and tell them that the problem is on our end, not theirs.

						Jordan