Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Jan 1999 12:41:38 +0900
From:      Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
To:        Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Cc:        freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject:   Re: New syscons + XFree 3.3.3.1 = problem? 
Message-ID:  <199901180341.MAA23586@zodiac.mech.utsunomiya-u.ac.jp>
In-Reply-To: Your message of "Sun, 17 Jan 1999 18:49:51 %2B0100." <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> 
References:  <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> 

next in thread | previous in thread | raw e-mail | index | archive | help
>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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901180341.MAA23586>