From owner-freebsd-current Sun Feb 18 19:51:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA24991 for current-outgoing; Sun, 18 Feb 1996 19:51:30 -0800 (PST) Received: from gwydion.hns.st-louis.mo.us (root@dialup-67.icon-stl.net [199.217.153.67]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA24985 for ; Sun, 18 Feb 1996 19:51:27 -0800 (PST) Received: (from kenth@localhost) by gwydion.hns.st-louis.mo.us (8.7.3/8.7.2) id VAA00546; Sun, 18 Feb 1996 21:51:10 -0600 (CST) From: Kent Hamilton Message-Id: <199602190351.VAA00546@gwydion.hns.st-louis.mo.us> Subject: Re: Keyboard lockout on 2.x.x To: coredump@nervosa.com (invalid opcode) Date: Sun, 18 Feb 1996 21:51:10 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: from "invalid opcode" at Feb 18, 96 06:16:57 pm Reply-To: KentH@HNS.St-Louis.Mo.US X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk > > When exactly does it lock up? Ohh, sorry, I've seen this mentioned here before so I guess I thought it was a well known problem. I'm using syscon and when flipping to a different vt you'll get locked out. It appears to happen when there is also SCSI activity. I've seen it both on machines with PS/2 keyboards, and standard AT keyboards. SCSI cards have been Adaptec or Buslogic. Only way I've found is to rlogin and re-boot but I thought someone mentioned having a work-around once. > On Sun, 18 Feb 1996, Kent Hamilton wrote: > > > Does anyone have a workaround (or better yet a solution) to the keyboard > > lockup problem on FreeBSD? > > > > I've had this problem running 2.0.5, 2.1.0, and -current. So it doesn't > > appear to be fixed anywhere. Does anyone have a workaround? -- Kent Hamilton Work: KHamilton@Hunter.COM URL: http://www.icon-stl.net/~khamilto Play: KentH@HNS.St-Louis.Mo.US