Date: Sun, 30 Jul 2006 21:34:40 -0700 From: freebsd@bitfreak.org To: Emil Mikulic <emil@cs.rmit.edu.au> Cc: freebsd-current@freebsd.org, Wolfram Fenske <Wolfram.Fenske@Student.Uni-Magdeburg.DE>, Markus Trippelsdorf <markus@trippelsdorf.de> Subject: Re: Keyboard LEDs always on Message-ID: <44CD8860.70600@bitfreak.org> In-Reply-To: <20060731014023.GB12725@cs.rmit.edu.au> References: <20060729105933.GA687@bsd.trippelsdorf.de> <86mzaqn81y.fsf@student.uni-magdeburg.de> <20060731014023.GB12725@cs.rmit.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Emil Mikulic wrote: > On Sun, Jul 30, 2006 at 10:37:13PM +0200, Wolfram Fenske wrote: >> Markus Trippelsdorf <markus@trippelsdorf.de> writes: >> >>> After upgrading from -stable to -current, the three LEDs on my >>> USB keyboard are switched on at boot time and cannot be controlled >>> by the caps-, num- or scroll-lock keys anymore. >>> Is this a known problem? I would be grateful for any hints. >> I can't really help you solve this, but I can confirm it. I had the >> same problem with my USB keyboard. It didn't happen with an older >> -current from around around april. > > I'm seeing it too, but only in X11. If I switch to a textmode console, > NumLock and CapsLock behave as I expect them to. ScrollLock does weird > wacky things to the LEDs though... > > This is on a Dell GX280 with a USB keyboard. I recall having this problem years ago with a keyboard. The trick, IIRC though well-fogged memory, involved editting a keymap and changing the codes used to toggle the LEDs. This may not be applicable to USB keyboards, however.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44CD8860.70600>