From owner-freebsd-current Sun Jan 17 19:39:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01234 for freebsd-current-outgoing; Sun, 17 Jan 1999 19:39:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01215 for ; Sun, 17 Jan 1999 19:39:27 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:iFNtvgqX3v0dNoFdyK2/Qvpdbwp1l2Wt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA26417; Mon, 18 Jan 1999 12:39:07 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA23586; Mon, 18 Jan 1999 12:41:39 +0900 (JST) Message-Id: <199901180341.MAA23586@zodiac.mech.utsunomiya-u.ac.jp> To: Oliver Fromme cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: New syscons + XFree 3.3.3.1 = problem? In-reply-to: Your message of "Sun, 17 Jan 1999 18:49:51 +0100." <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> References: <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> Date: Mon, 18 Jan 1999 12:41:38 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm using -current as of 1998-01-14 with the new syscons (with >separated keyboard driver) and XFree86 3.3.3.1 (XF86_SVGA on a >Matrox G200). The keyboard and mouse are plain PS/2 models, >they work fine under syscons (i.e. not using XFree). [...] >XFree used to allocate the next free virtual terminal when >started (in this case the 11th), Yes, and it still should be. >but that doesn't happen any- >more. Instead, it uses the current one (i.e. if I'm on ttyv3 >and start X, it uses ttyv3). Is this intentional, or is it a >bug? Hmm, no, this shouldn't be happening. How do you start X, by hand, or via a local shell script (i.e. rc.local or something), or via /etc/ttys? >While the above isn't really a serious problem, the following >is: When X has run for some time, the keyboard suddenly starts >being unresponsive and unusable. This can happen after a few >minutes or after a few hours. There are no error messages, no >syslog entries. It looks like the keypresses don't get to >XFree anymore, but to the vty beneath. Restarting X helps, >until it happens again. Quite annoying. It sounds like the X server and getty is fighting for keyboard input... How many vtys do you have (check MAXCONS in the kernel config)? How many of which will run getty (check /etc/ttys)? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message