From owner-freebsd-hardware Wed Jan 6 17:17:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06746 for freebsd-hardware-outgoing; Wed, 6 Jan 1999 17:17:24 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail5.realtime.net (mail5.realtime.net [205.238.128.241]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA06738; Wed, 6 Jan 1999 17:17:20 -0800 (PST) (envelope-from jktheowl@bga.com) Received: from barnowl ([205.238.146.129]) by mail5.realtime.net ; Wed, 06 Jan 1999 19:17:19 -600 Date: Wed, 6 Jan 1999 19:26:22 -0600 (CST) From: John Kenagy X-Sender: jktheowl@barnowl To: Eric Hodel cc: Pilo Phlat , questions@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Keyboard (PS/2?) problems (follow-up) In-Reply-To: <3693D34E.F06A5C1F@seattleu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 6 Jan 1999, Eric Hodel wrote: > Pilo Phlat wrote: > > > > Ok, I've tried different types of keyboards, including the ones mentioned > > below, a standard 104-key "win95 design" keyboard, Microsoft Natural > > Elite(TM)(R)(SM)(C) Microsoft, and some others. With all of them, I've had > > the same problems with the console locking up. I found out that after a > > lot (not sure how many exactly) of switching vty's, this happens, and > > locks up in mid-switch (using alt-Fkey). Is this a bug with the syscons > > driver? > > > > Please let me know if any of you have had this problem before. Thanks. > > Occasionally I will have to hit the numlock button a couple time to type > anything (the first time it beeps, the second time it toggles) but I haven't > noticed this in conjunction with switching consoles. I've had similar problems. It's the mouse - ps/2 variety - for me. Moving the mouse in the root window while holding down the control key (to pop up a menu) will freeze it up tight. The other situation is during an edit session with Xemacs. During those sessions and if the xconsole window is visible, I see errors indicating psmintr breaking lock or losing sync. I do not remember the exact error. I've rebuilt the kernel there is a variable that needs to be set in 2.2.1R, anyway: options PSM_CHECKSYNC You might want to check the documentation for your version to see if this might help. As far as I know this is a maybe. I've given up and run a serial mouse with no problems. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message