From owner-freebsd-doc Thu Apr 23 16:00:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14342 for freebsd-doc-outgoing; Thu, 23 Apr 1998 16:00:03 -0700 (PDT) (envelope-from owner-freebsd-doc@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14325; Thu, 23 Apr 1998 16:00:01 -0700 (PDT) (envelope-from gnats) Date: Thu, 23 Apr 1998 16:00:01 -0700 (PDT) Message-Id: <199804232300.QAA14325@hub.freebsd.org> To: freebsd-doc Cc: From: Tim Vanderhoek Subject: Re: conf/3590 Reply-To: Tim Vanderhoek Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR conf/3590; it has been noted by GNATS. From: Tim Vanderhoek To: freebsd-gnats-submit@FreeBSD.ORG Cc: Subject: Re: conf/3590 Date: Thu, 23 Apr 1998 18:49:32 -0400 (EDT) And, of course, for reference purposes, Kazu always seems to know what he's talking about... :) This is probably a good summary and should be FAQ-ified. -- tIM...HOEk OPTIMIZATION: the process of using many one-letter variables names hoping that the resultant code will run faster. ---------- Forwarded message ---------- Date: Wed, 22 Apr 1998 14:16:40 +0900 From: Kazutaka YOKOTA To: "Alok K. Dhir" Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Disappearing keyboard >I've been having a strange problem with -current since late March. The >machine is a Dell Workstation 400, dual Pentium 300 (running SMP). > >Problem is that occasionally, the keyboard stops responding completely. >The mouse in X continues to work, and telnet sessions are fine. It just >stops taking keyboard input. > >I can make this happen repeatably simply by having "xdm" in rc.local. >Then, every time it comes up, the keyboard is dead. Taking xdm out of >rc.local, and starting it manually as root after the system is up keeps >the keyboard working OK. It still dies every now and then though. > >Any ideas? There may be conflict between getty and xdm. On which vty are you running xdm? AFAIK, there are four ways to start xdm and avoid conflicts with getty. 1. Specify xdm in /etc/ttys. If you want to run xdm in ttyv3, you write: ttyv3 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure 2. Run xdm from /etc/rc.local (or other rc* files). if [ -x /usr/X11R6/bin/xdm ]; then (sleep 10; /usr/X11R6/bin/xdm) & fi It is essential to add "sleep N" for proper operation. You may need to experient in order to find an appropriate value for N in your configuration. 3. Another way to run xdm from /etc/rc.local (or other rc* files). if [ -x /usr/X11R6/bin/xdm ]; then /usr/X11R6/bin/xdm fi You need to explicitly specify a vty in which to run the X server by modifying /usr/X11R6/lib/X11/xdm/Xserver. :0 local /usr/X11R6/bin/X vt4 The above example will run the X server in ttyv3. Note that the X server counts vtys as vt1, vt2, vt3..., whereas FreeBSD uses the notation ttyv0, ttyv1, ttyv2,... 4. Specify the X server in /etc/ttys. ttyv3 "/usr/X11R6/bin/X vt4 -query localhost" xterm on secure _Remove_ the X server from /usr/X11R6/lib/X11/xdm/Xserver. _Add_ localhost to /usr/X11R6/lib/X11/xdm/Xaccess. Start xdm from /etc/rc* as: if [ -x /usr/X11R6/bin/xdm ]; then /usr/X11R6/bin/xdm fi Hope this will give you some ideas. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message