Date: Mon, 19 Feb 1996 20:55:58 +0100 (MET) From: Søren Schmidt <sos@DeepCore.dk> To: j@uriah.heep.sax.de (J Wunsch) Cc: freebsd-current@freebsd.org, KentH@HNS.St-Louis.Mo.US Subject: Re: Keyboard lockout on 2.x.x Message-ID: <199602191955.UAA00463@DeepCore.dk> In-Reply-To: <199602191810.TAA12654@uriah.heep.sax.de> from "J Wunsch" at Feb 19, 96 07:10:03 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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 ..
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602191955.UAA00463>