From owner-freebsd-questions Wed Apr 15 13:25:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02312 for freebsd-questions-outgoing; Wed, 15 Apr 1998 13:25:49 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from euthyphro.uchicago.edu (euthyphro.uchicago.edu [128.135.21.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01954 for ; Wed, 15 Apr 1998 20:24:33 GMT (envelope-from sfarrell@phaedrus.uchicago.edu) Received: from phaedrus.uchicago.edu (phaedrus [128.135.21.10]) by euthyphro.uchicago.edu (8.8.6/8.8.4) with ESMTP id PAA22045; Wed, 15 Apr 1998 15:24:10 -0500 (CDT) Received: (from sfarrell@localhost) by phaedrus.uchicago.edu (8.8.8/8.8.5) id PAA03920; Wed, 15 Apr 1998 15:24:09 -0500 (CDT) To: Eric Lee Burns Cc: freebsd-questions@freefall.FreeBSD.org Subject: Re: XF86 keyboard lockup issue References: From: sfarrell+lists@farrell.org Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Date: 15 Apr 1998 15:24:08 -0500 In-Reply-To: Eric Lee Burns's message of "Wed, 15 Apr 1998 01:04:22 -0400 (EDT)" Message-ID: <873efeltp3.fsf@phaedrus.uchicago.edu> Lines: 39 X-Mailer: Gnus v5.6.3/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eric Lee Burns writes: > 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. Well, in your /etc/ttys file you shuld have at least one of those ttyv's set to "off", like: ttyv6 "/usr/libexec/getty Pc" cons25 off secure the x server will want to run on the first "off" vtty it finds. > 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.) Well, one work-around is dont' hold down random keys while the server is restarting... seriously, i'm confused at the problem. I think it's typical for X (especially Xsun on sparcs!) to fuck up the console royally and generally run amuck when switching modes. the solution is: don't do it. If it happens, either telnet in and run xdm, or else reboot. -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message