From owner-freebsd-questions Tue Apr 14 22:05:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20100 for freebsd-questions-outgoing; Tue, 14 Apr 1998 22:05:58 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20035 for ; Wed, 15 Apr 1998 05:05:54 GMT (envelope-from burns+@andrew.cmu.edu) Received: (from postman@localhost) by po8.andrew.cmu.edu (8.8.5/8.8.2) id BAA06639 for freebsd-questions@freefall.FreeBSD.org; Wed, 15 Apr 1998 01:05:52 -0400 (EDT) Received: via switchmail; Wed, 15 Apr 1998 01:05:51 -0400 (EDT) Received: from pcs37.andrew.cmu.edu via qmail ID ; Wed, 15 Apr 1998 01:04:23 -0400 (EDT) Received: from pcs37.andrew.cmu.edu via qmail ID ; Wed, 15 Apr 1998 01:04:22 -0400 (EDT) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.PC.3.2.CUILIB.3.45.SNAP.NOT.LINKED.pcs37.andrew.cmu.edu.sun4m.54 via MS.5.6.pcs37.andrew.cmu.edu.sun4_51; Wed, 15 Apr 1998 01:04:22 -0400 (EDT) Message-ID: Date: Wed, 15 Apr 1998 01:04:22 -0400 (EDT) From: Eric Lee Burns To: freebsd-questions@freefall.FreeBSD.org Subject: XF86 keyboard lockup issue Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am experiencing a really infuriating bug with virtually every X server I have tried for FreeBSD, including XF86 3.2-3.3.2 and AccelX 3.1 and 4.1. If the server ever dies, it takes the entire console with it. Basically, all keyboard control becomes locked out except for ctrl-alt-del, which works. Trying to switch virtual consoles with ctrl-alt-f* or just alt-f* produces a beep, and anything else does nothing. Here is what I know about the problem: The system never crashes with the X server. It always stays up, and X can actually be started again. If X is started, it generally produces some error about not being able to open the appropriate console, and starts anyway. In XF86's case, this error is "VT_ACTIVATE: cannot open console" or something along those lines. I took a look at the permissions on /dev/ttyv*. I added vty4-8 myself. All the devices are owned by root, but only ttyv0-2 belong to group "tty" and have a group writeable flag (crw--w----). I think this may have something to do with the problem. Does anyone know if there is a workaround for this? I know the keyboard lockout problem can be reproduced fairly easily. If you are running XF86, load XDM, log in, and exit. While the server is restarting, hold down some random keys. When the server comes up, it will be impossible to switch virtual consoles. (I haven't tested this since XF86 3.3, it may have been fixed since then.) If anyone knows how to resolve this, or to even correct the settings on the virtual consoles permanently, I would be extremely grateful. One more thing... can anyone recommend an appropriate way to start XDM? All I have now is a hack script in /usr/X11R6/etc/rc.d. I have been told that there is some way to do it through /etc/ttys, but I don't know how. Eric Burns (latinum@YAVIN.RES.CMU.EDU) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message