From owner-freebsd-current Sun Jan 17 09:50:03 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08553 for freebsd-current-outgoing; Sun, 17 Jan 1999 09:50:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08472 for ; Sun, 17 Jan 1999 09:49:56 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id SAA08436 for freebsd-current@FreeBSD.ORG; Sun, 17 Jan 1999 18:49:51 +0100 (CET) (envelope-from olli) Date: Sun, 17 Jan 1999 18:49:51 +0100 (CET) From: Oliver Fromme Message-Id: <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: New syscons + XFree 3.3.3.1 = problem? Newsgroups: list.freebsd-current Organization: Administration Heim 3 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, 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). The kernel contains the following entries: controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts pseudo-device splash device sc0 at isa? tty options MAXCONS=10 options SC_HISTORY_SIZE=500 XFree used to allocate the next free virtual terminal when started (in this case the 11th), 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? 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. Does anyone else experience the same problems? Am I doing something wrong? What can I do to help tracking down the problem? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message