Date: Sun, 17 Jan 1999 18:49:51 +0100 (CET) From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: New syscons + XFree 3.3.3.1 = problem? Message-ID: <199901171749.SAA08436@dorifer.heim3.tu-clausthal.de>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901171749.SAA08436>