From owner-freebsd-hackers Fri Oct 18 08:54:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03031 for hackers-outgoing; Fri, 18 Oct 1996 08:54:33 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03026 for ; Fri, 18 Oct 1996 08:54:29 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA24597; Fri, 18 Oct 1996 09:54:21 -0600 (MDT) Date: Fri, 18 Oct 1996 09:54:21 -0600 (MDT) Message-Id: <199610181554.JAA24597@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: Doug Rabson , Nate Williams , "Brian N. Handy" , freebsd-hackers@freebsd.org Subject: Re: 2.2-961006-SNAP keyboard lockup In-Reply-To: <9839.845653806@time.cdrom.com> References: <9839.845653806@time.cdrom.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > 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! :-). Me too. It took a couple weeks of using it, but I (and my wrists) prefer it to normal keyboards. > 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. I can tell you almost equivicolly (sp?) that it's our problem. I have never run XInside (except for demos) on any of my boxes and it locks up all the time both in and out of X. Nate