From owner-freebsd-current Mon Feb 19 12:01:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA18870 for current-outgoing; Mon, 19 Feb 1996 12:01:19 -0800 (PST) Received: from DeepCore.dk (cph30.pip.dknet.dk [194.192.0.62]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA18862 for ; Mon, 19 Feb 1996 12:01:13 -0800 (PST) Received: (from sos@localhost) by DeepCore.dk (8.7.3/8.7.3) id UAA00463; Mon, 19 Feb 1996 20:55:59 +0100 (MET) From: Søren Schmidt Message-Id: <199602191955.UAA00463@DeepCore.dk> Subject: Re: Keyboard lockout on 2.x.x To: j@uriah.heep.sax.de (J Wunsch) Date: Mon, 19 Feb 1996 20:55:58 +0100 (MET) Cc: freebsd-current@freebsd.org, KentH@HNS.St-Louis.Mo.US In-Reply-To: <199602191810.TAA12654@uriah.heep.sax.de> from "J Wunsch" at Feb 19, 96 07:10:03 pm Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk In reply to J Wunsch who wrote: > > As Kent Hamilton wrote: > > > I remembered someone saying it had to do with the LED's, I have > > re-set the machines to not turn them on at boot and I almost never > > use a caps/num lock anyway. What else will toggle the LED states? > > Scroll lock which I never use... anything else? > > It doesn't matter whether LEDs would really be toggled. The command > is always sent to the keyboard on a VT switch, even if the update will > yield the same LED state as previously. Hence the line conflict will > always happen. Erhm, once I put in the code to do the LED update asynchronously.. What I don't remember is if its still in there, try look for a #if ASYNCH or something like that and then define it and recompile. If this works you have one of those kbd controllers.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..