Yeah, there definitely is a strong bias against the Num Lock key in the 'nix world.
Here is how I set the Num Lock for console mode (run from within rc.local):
Code:
# Turn numlock on:
# the following should match the number of consoles opened in /etc/inittab
# how many ttys are assigned in /etc/inittab?
INITTY=/dev/tty[1-`grep -v "^# " /etc/inittab | grep -c "^c[0-9]:"`]
for tty in $INITTY; do
# -v = verbose
# /usr/bin/setleds -v -D +num < $tty
/usr/bin/setleds -D +num < $tty
done
For graphical mode, use one of the Num Lock programs as mentioned above.
Additionally, KDE supports Num Lock. Look in the Control Center, under Peripherals/Keyboard. KDE also supports Accessibility options to enable a low volume pip noise when the Num Lock key is toggled. Look in the Control Center, Regional & Accessibility, Accessibility, Locking Keys. Within KDE Num Lock and Caps Lock are considered locking keys. I don't know why Scroll Lock and Insert are not. They should be.
If you want Num Lock support with the kernel, you have to modify keyboard.c and recompile the kernel. Always irritated me that I set Num Lock in the BIOS and Linus toggled Num Lock off. Should be a boot parameter, not hard-coded.
Quote:
also the . on my number pad doesnt work under linux?
|
Temporarily disable Num Lock and check that the key acts as a Delete key. If not then the key might be dirty and not making contact.