From owner-freebsd-questions Thu Jan 15 20:46:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23682 for questions-outgoing; Thu, 15 Jan 1998 20:46:58 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gte.net (1Cust166.tnt1.lafayette.in.da.uu.net [208.254.19.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23578 for ; Thu, 15 Jan 1998 20:45:41 -0800 (PST) (envelope-from bhlewis@gte.net) Received: from localhost (localhost [127.0.0.1]) by gte.net (8.8.8/8.8.8) with ESMTP id XAA14469 for ; Thu, 15 Jan 1998 23:44:56 -0500 (EST) (envelope-from bhlewis@gte.net) Message-Id: <199801160444.XAA14469@gte.net> X-Mailer: exmh version 2.0.1 12/23/97 cc: freebsd-questions@FreeBSD.ORG Subject: Re: Keyboard LEDs In-reply-to: Your message of "Thu, 15 Jan 1998 18:44:09 EST." <199801152344.SAA13025@gte.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Jan 1998 23:44:55 -0500 From: Benjamin Lewis Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk Hi again- > I've gotten vgetty working pretty well on my system, and I've been trying to > get one of the keyboard LEDs to blink when there is a message. > > The problem is that the LEDs only seem to change state when there is some > other reason to do so, e.g. the Caps Lock key is pressed. I've managed to fix the problem. It turns out the the XKEYBOARD extension was the culprit. Inserting the XkbDisable keyword in /etc/XF86Config file disables the extension and returns the LEDs to normal behavior. -Ben -- Benjamin Lewis bhlewis@gte.net -or- bhlewis@purdue.edu