On 2012-12-02, Mark Knecht <markkne...@gmail.com> wrote:
> On Sun, Dec 2, 2012 at 12:05 PM, Grant Edwards
><grant.b.edwa...@gmail.com> wrote:
>> On 2012-12-02, cov...@ccs.covici.com <cov...@ccs.covici.com> wrote:
><SNIP>
>>> I think numlock is on by default in newer kernels
>>
>> That pretty much sucks. Is that configurable sowewhere?
>>
>
> This is not my experience. I'm using 3.5.* everywhere and haven't had
> this problem on any machine to date. numlock is off by default on all
> machines as best I can tell.
Armed with the clue that the change happened at 3.4 rather than 3.5, I
found the thread in the kernel dev list where it was discussed.
Before 3.4, numlock defaulted to off. Starting in 3.4, numlock
defaults to whatever the BIOS configuration is. I change the numlock
setting in my BIOS (didn't know it had one), and everything's cool.
> /etc/init.d/numlock on/off will change the state of the lights on my
> keyboard. Have you tried that?
On my system it's start/stop rather than on/off. You can also just use
the setleds utility directly, but either is hard to do,
keyboard doesn't allow you to enter the letters u,i,o,p,j,k,l,m :)
> I didn't know that OpenRC had added numlock control but it's there
> and documented in a Gentoo Wiki.
OK, I understand how to enable numlock for various run states, but
just for curiousity's sake, how do you get the script called with the
"stop" paramter instead of the "start" parameter during startup?
Do other people's "numlock" keys still work with 3.4 and 3.5 kernels?
When running 3.5, my "numlock" key functions as a shift lock.
--
Grant Edwards grant.b.edwards Yow! I have many CHARTS
at and DIAGRAMS..
gmail.com
