Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:3605 comp.os.386bsd.bugs:1440
Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!brunix!cs.brown.edu!Mark_Weaver
From: Mark_Weaver@brown.edu
Subject: Re: NetBSD 0.9 + XFree 1.3 -> occasional keyboard hangup
In-Reply-To: vdlinden@fwi.uva.nl's message of 18 Sep 1993 13:42:26 GMT
Message-ID: <MARK_WEAVER.93Sep18201917@excelsior.cis.brown.edu>
Sender: news@cs.brown.edu
Organization: Brown University Department of Computer Science
References: <27f382$7dc@mail.fwi.uva.nl>
Date: Sun, 19 Sep 1993 00:19:17 GMT
Lines: 21
In article <27f382$7dc@mail.fwi.uva.nl> vdlinden@fwi.uva.nl (Frank van der Linden) writes:
> I'm still trying out NetBSD 0.9, and have installed XFree 1.3. It
> works OK, except for one thing: every once in a while (while in X),
> the keyboard locks up. I can still use the mouse, exit X, and then
> it works again, although I once could not send signals (^C, ^\, ^Z)
> via the keyboard anymore after exiting X this way.
The problem happens every time /etc/daily is run. This causes a
SIGHUP to be sent to syslogd, which makes it reset. When syslogd
resets, it closes and then reopens /dev/console, which takes pccons
out of X mode. This problem has been fixed for XFree86 2.0 (when it
comes out), but in the meantime you can fix it by switching to codrv.
Another (hack) way of fixing it is to have /dev/console open by another
process so that the driver won't get the close() call. In an xterm you
can run "cat >/dev/console", and this should alleviate the problem until
XFree86 2.0 comes out.
--
--------------------------------------------------------------------
Email: Mark_Weaver@brown.edu | Box 2160, Brown University
| Providence, RI 02912-2160