From owner-freebsd-questions Wed Jan 20 14:48:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28522 for freebsd-questions-outgoing; Wed, 20 Jan 1999 14:48:38 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from modgud.nordicdms.com (h21-168-107.nordicdms.com [207.21.168.107]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA28516 for ; Wed, 20 Jan 1999 14:48:37 -0800 (PST) (envelope-from walton@nordicdms.com) Received: (qmail 8693 invoked by alias); 20 Jan 1999 22:48:29 -0000 Message-ID: <19990120224829.8690.qmail@modgud.nordicdms.com> Received: (qmail 8679 invoked from network); 20 Jan 1999 22:48:29 -0000 Received: from mail-ftp.nordicdms.com (HELO mail-ftp) (207.21.168.100) by mail.nordicdms.com with SMTP; 20 Jan 1999 22:48:29 -0000 From: "Dave Walton" Organization: Nordic Entertainment Worldwide To: "K. Arun" , questions@FreeBSD.ORG Date: Wed, 20 Jan 1999 14:48:28 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Keyboard freezes under 2.2.8. Reply-to: walton@nordicdms.com In-reply-to: <199901202108.VAA01519@giasmda.vsnl.net.in> X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Jan 99, at 20:17, K. Arun wrote: > I've been running FreeBSD 2.2.8 for about three weeks now. I've > set it up to boot straight into a wdm login. At times the keyboard > simply freezes (under both fvwm2 and WM), and no input is accepted. > None of the Lock (caps,num, etc.) work either. Since I can't switch to > a virtual terminal I'm generally forced to hit the reset button. If you are on a network, you should still be able to telnet in and reboot that way. > The problem is not readily reproducible, it generally happens > within ten minutes of my logging in and starting the window manager. > It happens with XKB (what is it ?) enabled and disabled. Mouse clicks > still work fine. I'm able to use menus and buttons, but no text input > anywhere is allowed. I haven't really checked if this is a consequence > of my booting straight into X (wdm). I don't recall such a problem when > starting X from the console. What am I missing ? This sounds like it may be a problem that I just ran into. Find out exactly which tty your X login window is coming up on. Then make sure that you have that tty disabled in /etc/ttys. For example, if you can switch away from X using Ctrl-Alt-F1 and then switch back to X with Alt-F3, then X is running on /dev/ttyv2. Make sure that the ttyv2 line in /etc/ttys has "off" in the "status" column. If X is running on a tty that is enabled, the conflict will cause exactly the problem you describe. (I learned that the hard way this morning...) Dave ---------------------------------------------------------------------- Dave Walton Webmaster, Postmaster Nordic Entertainment Worldwide walton@nordicdms.com http://www.nordicdms.com ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message