Don’t tinker. NumLock is set in the bios. System Numlock is set in /etc/sysconfig/keyboard and can be changed using “yast2 sysconfig”.
## Type: list(bios,yes,no)
## Default: bios
# NumLock on? ("yes" or "no" or "bios" for BIOS setting)
# This setting may interfere with GNOME /org/gnome/settings-daemon/peripherals/keyboard/remember-numlock-state DConf key.
In my experience, I had to tinker too. There’s no NumLock setting in BIOS, and I don’t recall the issue being fixed by setting to “yes”. I may have done it wrong somehow though, as I was trying to get it working mostly for the graphical session. Later I discovered that in vt’s the numpad wouldn’t work (no numlock key).
KBD_NUMLOCK overrides bios, plasma settings override KBD_NUMLOCK. tty1…6 default to numlock=no and may be changed in /etc/sysconfig/keyboard. X11 checks for file numlock-on which is created or deleted by /usr/sbin/kbdsettings. Settings are:
Thanks, it’s indeed a better solution, as it fixes for both consoles and Xorg. I’ll propose changing the docs for /etc/sysconfig/keyboard to include that Xorg picks it up too, not just text consoles. Do you think it makes sense? I feel somewhere in the Xorg docs should mention this as well, but have no idea where.
Unfortunately it’s too short and inaccurate. Section 3 should be deleted as “Expert Settings” are no longer available. Add at the end of the section:
The following settings may be changed using yast2 > sysconfig > hardware > keyboard:
Delay before Repetition Starts
Start-up States for Num Lock, Caps Lock, and Scroll Lock
Devices on which the values for Num Lock, Caps Lock, and Scroll Lock should be set
Disable Caps Lock
I clicked “Edit source” but learned a fork was needed to propose changes to the documentation. When I looked further it says it would apply to SLE but the documentation says it applies to Leap 15.2. I am left confused.