Messages in this thread | | | Date | Mon, 27 Feb 2012 13:09:50 -0800 | From | "H. Peter Anvin" <> | Subject | Re: [RESUBMIT] [PATCH] Use BIOS Keyboard variable to set Numlock |
| |
On 02/27/2012 11:23 AM, Joshua C. wrote: > I rebased this on the latest kernel-3.3-rc5 so that it can be properly applied. > ------------------ > > From 36e15b8d9d491817a3bada5ef9375aabe9439d9b Mon Sep 17 00:00:00 2012 > From: Joshua Cov <joshuacov@googlemail.com> > Date: Mon, 27 Feb 2012 20:49:18 +0100 > Subject: [PATCH] Use BIOS Keyboard variable to set Numlock > > The PC BIOS does provide a NUMLOCK flag containing the desired state > of this LED. Bit 0x417 has the current keyboard modifier state. This > patch sets the current state according to the data in the bios and > introduces a module parameter "numlock" which can be used to > explicitely disable the NumLock (1 = enable, 0 = disable). > > See first discussion back in 2007 at: > http://lkml.indiana.edu/hypermail/linux/kernel/0707.1/1834.html > > Signed-Off-By: Joshua Cov <joshuacov@googlemail.com> > Cc: H. Peter Anvin <hpa@zytor.com> > Cc: Bodo Eggert <7eggert@gmx.de> >
A better idea might be to query the status in the BIOS bootstrap code -- then non-BIOS boots can do the equivalent. It also has the side benefit of making people running Grub2 perhaps realize that they are f****ng themselves over by using the "linux" command and not "linux16", because of course policy in Grub2 is that if there is a sane way to do it, make sure it is NOT the default.
-hpa
| |