Pavel Machek, le Sat 13 Jul 2013 01:33:01 +0200, a écrit : > > > > This permits to reassign keyboard LEDs to something else than keyboard > > > > "leds" > > > > state, by adding keyboard led and modifier triggers connected to a > > > > series > > > > of VT input LEDs, themselves connected to VT input triggers, which > > > > per-input device LEDs use by default. Userland can thus easily change > > > > the LED > > > > behavior of (a priori) all input devices, or of particular input > > > > devices. > > > > > > Nice! Leds now have proper /sys interface. > > > > > > But... I boot up, switch from X to console, press capslock, and no > > > reaction anywhere. > > > > Is it working without the patch? Console-setup for instance is known to > > have broken the capslock LED, which is precisely one of the reasons for > > this patch, which will provide console-setup with a way to bring back > > caps lock working properly. > > You are right, it was broken before.
Ok. You then may want fix your setup by configuring your caps lock led the way console-setup will be supposed to do in the future: echo ctrlllock > /sys/class/leds/vt::capsl/trigger Or some other of the locks that console-setup might be using to implement caps lock. > > Things work fine with my USB keyboard too, is this perhaps using an odd > > driver which would not expose LEDs in a standard way? > > No, everything works as well as it did. Feel free to add: > > Tested-by: Pavel Machek <pa...@ucw.cz> Thanks for testing, Samuel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
