From owner-freebsd-stable Sun Oct 8 21:27: 0 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 82DB637B502 for ; Sun, 8 Oct 2000 21:26:56 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e994QmK37863; Sun, 8 Oct 2000 21:26:48 -0700 (PDT) Date: Sun, 8 Oct 2000 21:26:48 -0700 (PDT) From: Doug White To: Vivek Khera Cc: stable@FreeBSD.ORG Subject: Re: curious interaction between kdm and snmpd on startup In-Reply-To: <14814.15644.780542.774320@onceler.kciLink.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Oct 2000, Vivek Khera wrote: > I run kdm from my /etc/rc.local script to get nice graphical login to > KDE. > > Recently I added ucd-snmp to this system. Today I did a reboot after > testing the vmware "vmnet" module which happened to lock up my kernel. > > Upon reboot, the keyboard within X under the kdm session was > non-responsive to most keystrokes. The CTRL-ALT-Fn sequence beeped at > me execpt for F2, which didn't do anything. CAPS LOCK worked, as did > NUMLOCK. The regular keys did nothing. All I could do was > CTRL-ALT-DEL to get out of it. This is what happens when the getty on console and xdm start up simultaneously. The keyboard goes into limbo-mode. The solution is to get xdm to wait 5-10 seconds for the getty to launch before starting itself. This can be done with some nifty shell tricks. Use this (which starts wdm, not xdm, but same idea) as a script in /usr/local/etc/rc.d/: [ -x /usr/X11R6/bin/wdm ] && echo -n ' wdm' && (sleep 5; /usr/X11R6/bin/wdm) & Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message