From owner-freebsd-questions Mon Feb 16 10:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11403 for freebsd-questions-outgoing; Mon, 16 Feb 1998 10:31:02 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11082 for ; Mon, 16 Feb 1998 10:29:57 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id KAA10498; Mon, 16 Feb 1998 10:29:51 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 16 Feb 1998 10:29:51 -0800 (PST) From: Doug White Reply-To: Doug White To: Gopakumar H Pillai cc: FreeBSD Questions Subject: Re: LED command not ACKed In-Reply-To: <34E371F7.FC943003@global.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Feb 1998, Gopakumar H Pillai wrote: > I get this message, whenever I am in vi or emacs for a while form > FreeBSD 2.2.2. I think it's because the OS tries to monitor the numeric > keypad LED, which it loses control of while in vi. The error message: > > batman kernel log messages: > > Keyboard LED command not ACKed (responses 0x9c 0xfa) > > What should I do to get rid of it? Try a different keyboard, and if that doesn't fixit, well, you need a new motherboard. Or go into the kernel source, find the printf for that line and comment it out. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message