From owner-freebsd-current Sun Jul 30 19:42:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from wendell.heistand.org (wendell.heistand.org [209.181.116.46]) by hub.freebsd.org (Postfix) with ESMTP id 24B4937B985 for ; Sun, 30 Jul 2000 19:42:30 -0700 (PDT) (envelope-from heistand@heistand.org) Received: by wendell.heistand.org (Postfix, from userid 1821) id E3E7E1B24B; Sun, 30 Jul 2000 20:41:27 -0600 (MDT) Subject: Re: keyboard problems with X To: freebsd-current@freebsd.org Date: Sun, 30 Jul 2000 20:41:27 -0600 (MDT) From: heistand@heistand.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000731024127.E3E7E1B24B@wendell.heistand.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Originally didnt response back to mailing list...) The keyboard works fine when I dont start X, single user mode or just at the console. I can crash the machine whenever I switch virtual consoles which is most not fun. Not sure if its strictly an X problem on not. My previous -current was before the radical changes so I might have something out of wack but not sure. I think I got everything in my kernel config file uptodate. steve 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. Is it useable or not, outside of X? Can you single-user boot and get the keyboard working? I am not clear if it's an X problem or a system problem. You said you updated your source tree yesterday. If that was from a recent build, then I don't know, but I'm very curious, just how old was your previous build? The config changed really radically maybe 2 months ago, so maybe your config file is hosed? > > 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 > > > > > > > > > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message ----- End of forwarded message from Chuck Robey ----- -- Steve Heistand heistand@heistand.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message