Date: Sun, 30 Jul 2000 23:04:05 -0400 (EDT) From: Kenneth Wayne Culver <culverk@wam.umd.edu> To: Chuck Robey <chuckr@picnic.chuckr.org> Cc: heistand@heistand.org, freebsd-current@FreeBSD.ORG Subject: Re: keyboard problems with X Message-ID: <Pine.GSO.4.21.0007302303150.28415-100000@rac1.wam.umd.edu> In-Reply-To: <Pine.BSF.4.21.0007302229010.601-100000@picnic.chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
My problems are with a previous build of late last week. And my problem isn't with X. My problem only happens when you start "tail" on some file, then try to exit. It locks the console solid... neither the mouse nor the keyboard work. ================================================================= | 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, Chuck Robey wrote: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0007302303150.28415-100000>