From owner-freebsd-current Sun Jul 30 17:59:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 8CB4E37B858 for ; Sun, 30 Jul 2000 17:59:37 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA11154; Sun, 30 Jul 2000 20:59:17 -0400 (EDT) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id UAA09506; Sun, 30 Jul 2000 20:59:07 -0400 (EDT) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id UAA09502; Sun, 30 Jul 2000 20:59:07 -0400 (EDT) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Sun, 30 Jul 2000 20:59:07 -0400 (EDT) From: Kenneth Wayne Culver To: heistand@heistand.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X In-Reply-To: <20000730234826.A53251B24B@wendell.heistand.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hrmm, that's even worse than my problem. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Sun, 30 Jul 2000 heistand@heistand.org wrote: > The problem I am seeing is that the keyboard isnt even seen. > Its useable up until about midway through the boot process, > then it goes dead/locks up. The boot continues fine and the machine > is up. The mouse is usable in X but not the keyboard. Cant even switch > virtual consoles. > > steve > > > I have, like when I'm running tail on something, and then I try to ctrl-c > > out of it, the whole console locks solid, and I have to reboot. (although > > if I was connected to an ethernet, I think I could probably ssh in and > > reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the > > lockmgr problems that were reported earlier. > > > > > > ================================================================= > > | Kenneth Culver | FreeBSD: The best NT upgrade | > > | Unix Systems Administrator | ICQ #: 24767726 | > > | and student at The | AIM: muythaibxr | > > | The University of Maryland, | Website: (Under Construction) | > > | College Park. | http://www.wam.umd.edu/~culverk/| > > ================================================================= > > > > On Sun, 30 Jul 2000 heistand@heistand.org wrote: > > > > > Hi, > > > > > > I updated my source tree yesterday (and kernel) and am having some problems > > > with my keyboard under X. Has anyone else noticed anything > > > strange. > > > > > > steve > > > > > > -- > > > Steve Heistand > > > heistand@heistand.org > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > -- > Steve Heistand > heistand@heistand.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message