Date: Fri, 23 Jul 1999 14:19:59 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Thomas Dean <tomdean@ix.netcom.com> Cc: freebsd-smp@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP + XDM = keyboard lockup Message-ID: <199907230520.OAA05070@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Thu, 22 Jul 1999 21:51:41 MST." <199907230451.VAA52884@ix.netcom.com> References: <Pine.BSF.4.10.9907230012350.13821-100000@pawn.primelocation.net> <199907230432.VAA21465@apollo.backplane.com> <199907230451.VAA52884@ix.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>I am runing 4.0 current SMP. How recent is it? >The CTL-ALT-Fx problem was discussed and no solution was produced. >This is still an open issue. If you shutdown an X session and use >CTL-ALT-Fx before X completes resetting the screen and presents the >login prompt, the keyboard will lock. This happens every time. Please describe the exact sequence and symptom. How did you start X? By xdm? How did you "shutdown" the X sesssion? When the keyboard is looked up, which vty are you in? Do NumLock, CapsLock and ScrollLock change LED state? If you try to switch to another vty by hitting ALT-Fx, do you here beep? Would you hit ALT-Fx several times to see if it makes any difference? >After a long sequence, the answer to the question of how to start X >was to set /etc/ttys as I said earlier and start xdm in >/usr/local/etc/rc.d/<whatever>.sh. > >I switched to this mechanism and have not had a problem since. > >Has the "correct" way to start X changed back to using rc.local or >/etc/ttys? Some people like /etc/ttys. Other people prefer rc.local or /usr/local/etc/rc*. Me? I don't care which is "correct", so long as it works. Well, maybe I should think harder to decide which is more "correct"... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907230520.OAA05070>