[opensuse] Setting NumLock to On During Boot
On TW (and this is probably the same for Leap), on my desktop PC I want NumLock to be on every time I boot the computer. The default is for NumLock to be off but as my login password has numbers in it, I like using the number pad. I tried Fedora on the same machine a while back and it defaulted to NumLock being on every time the machine booted. It seems to me that NumLock being on during boot would be a sensible default, so why is the default for it to be off? And what is the best way to set it to be on every time my PC boots? Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. So I have to press NumLock again and the light stays lit, and then the Num Pad works. Is this the current default or something with whatever driver is driving my keyboard? Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wednesday, 6 April 2016 03:33:32 BST sdm wrote:
On TW (and this is probably the same for Leap), on my desktop PC I want NumLock to be on every time I boot the computer. The default is for NumLock to be off but as my login password has numbers in it, I like using the number pad. I tried Fedora on the same machine a while back and it defaulted to NumLock being on every time the machine booted.
Have you checked Yast/Hardware/System Keyboard Layout/Expert Settings? I've got the option the for numlock with on/off/BIOS setting. I'm on the latest Tumbleweed.
It seems to me that NumLock being on during boot would be a sensible default, so why is the default for it to be off? And what is the best way to set it to be on every time my PC boots? Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. So I have to press NumLock again and the light stays lit, and then the Num Pad works. Is this the current default or something with whatever driver is driving my keyboard? Thanks
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm wrote:
On TW (and this is probably the same for Leap), on my desktop PC I want NumLock to be on every time I boot the computer. The default is for NumLock to be off but as my login password has numbers in it, I like using the number pad. I tried Fedora on the same machine a while back and it defaulted to NumLock being on every time the machine booted.
It seems to me that NumLock being on during boot would be a sensible default, so why is the default for it to be off? And what is the best way to set it to be on every time my PC boots? Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. So I have to press NumLock again and the light stays lit, and then the Num Pad works. Is this the current default or something with whatever driver is driving my keyboard? Thanks
Maybe have a look at this: /etc/sysconfig/keyboard::KBD_NUMLOCK -- Per Jessen, Zürich (16.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/06/2016 08:20 AM, Per Jessen wrote:
Maybe have a look at this:
/etc/sysconfig/keyboard::KBD_NUMLOCK I changed that to "yes" as it was set to "BIOS", and that now makes it so NumLock is on by default for boot. Before, it was set to "bios" but I checked in my UEFI firmware settings and there was not setting for NumLock. So thanks for that, But the issue still remains, where if I switch to TTY1 and login, even though NumLock shows as lit on the keyboard, I have to press it again and it stays lit, and then the NumPad works. Is there a way around that?
Also, why not just have a sensible default for KBD_NUMLOCK to always be on? I would opine a lot of newer BIOS's are like mine, and there are people with the same issue, where they have to press NumLock every time they enter their password in sddm because the default is set to BIOS whereas the BIOS never sets it because the setting doesn't exist, so it just stays off. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm wrote:
But the issue still remains, where if I switch to TTY1 and login, even though NumLock shows as lit on the keyboard, I have to press it again and it stays lit, and then the NumPad works. Is there a way around that?
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active.
Also, why not just have a sensible default for KBD_NUMLOCK to always be on? I would opine a lot of newer BIOS's are like mine, and there are people with the same issue, where they have to press NumLock every time they enter their password in sddm because the default is set to BIOS whereas the BIOS never sets it because the setting doesn't exist, so it just stays off.
I don't mind, but I also don't think it's a big deal. -- Per Jessen, Zürich (17.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active. well that's possible.. it's a USB Microsoft Natural Keyboard 4000, I'll
On 04/06/2016 08:55 AM, Per Jessen wrote: try another keyboard and see what turns up, and yes, it is odd. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm wrote:
On 04/06/2016 08:55 AM, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active. well that's possible.. it's a USB Microsoft Natural Keyboard 4000, I'll try another keyboard and see what turns up, and yes, it is odd.
I've just reread what you said:
Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list.
I'll try it out on my system too, maybe something weird is happening at the time of login. -- Per Jessen, Zürich (16.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
sdm wrote:
On 04/06/2016 08:55 AM, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active. well that's possible.. it's a USB Microsoft Natural Keyboard 4000, I'll try another keyboard and see what turns up, and yes, it is odd.
I've just reread what you said:
Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list.
I'll try it out on my system too, maybe something weird is happening at the time of login.
Problem confirmed. If I switch to tty1 with Numlock on, in tty1 the LED remains on, but the keypad isn't in numeric mode. Sounds like poor initialization somewhere. I suggest opening a bugreport. -- Per Jessen, Zürich (10.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2016 12:33 AM, Per Jessen wrote:
Per Jessen wrote:
sdm wrote:
On 04/06/2016 08:55 AM, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active. well that's possible.. it's a USB Microsoft Natural Keyboard 4000, I'll try another keyboard and see what turns up, and yes, it is odd. I've just reread what you said:
Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. I'll try it out on my system too, maybe something weird is happening at the time of login. Problem confirmed. If I switch to tty1 with Numlock on, in tty1 the LED remains on, but the keypad isn't in numeric mode. Sounds like poor initialization somewhere. I suggest opening a bugreport.
So I did some further testing, installing Fedora 24 KDE Alpha and the behavior is exactly the same as openSUSE, so I was wrong in my earlier email. I forgot that the last time I used Fedora just a couple months ago, it was on a completely different motherboard (completely BIOS-based) and NumLock showed as lit on the keyboard and worked when switching to a text console, and this was with the same exact keyboard as I use on openSUSE. Just to be sure, I checked again in the UEFI BIOS settings of my motherboard and there is nothing there for for NumLock, surprising as it may be. If I am to open a bug report, what should I report it against? sdm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm wrote:
On 04/07/2016 12:33 AM, Per Jessen wrote:
Per Jessen wrote:
sdm wrote:
On 04/06/2016 08:55 AM, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active. well that's possible.. it's a USB Microsoft Natural Keyboard 4000, I'll try another keyboard and see what turns up, and yes, it is odd. I've just reread what you said:
Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. I'll try it out on my system too, maybe something weird is happening at the time of login. Problem confirmed. If I switch to tty1 with Numlock on, in tty1 the LED remains on, but the keypad isn't in numeric mode. Sounds like poor initialization somewhere. I suggest opening a bugreport.
So I did some further testing, installing Fedora 24 KDE Alpha and the behavior is exactly the same as openSUSE, so I was wrong in my earlier email. I forgot that the last time I used Fedora just a couple months ago, it was on a completely different motherboard (completely BIOS-based) and NumLock showed as lit on the keyboard and worked when switching to a text console, and this was with the same exact keyboard as I use on openSUSE. Just to be sure, I checked again in the UEFI BIOS settings of my motherboard and there is nothing there for for NumLock, surprising as it may be. If I am to open a bug report, what should I report it against?
Base system. It's probably systemd that is in charge to starting the consoles, but it's not systemd that is doing the initialisation. -- Per Jessen, Zürich (8.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2016 07:13 AM, Per Jessen wrote:
sdm wrote:
On 04/07/2016 12:33 AM, Per Jessen wrote:
Per Jessen wrote:
sdm wrote:
On 04/06/2016 08:55 AM, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active. well that's possible.. it's a USB Microsoft Natural Keyboard 4000, I'll try another keyboard and see what turns up, and yes, it is odd. I've just reread what you said:
Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. I'll try it out on my system too, maybe something weird is happening at the time of login. Problem confirmed. If I switch to tty1 with Numlock on, in tty1 the LED remains on, but the keypad isn't in numeric mode. Sounds like poor initialization somewhere. I suggest opening a bugreport.
So I did some further testing, installing Fedora 24 KDE Alpha and the behavior is exactly the same as openSUSE, so I was wrong in my earlier email. I forgot that the last time I used Fedora just a couple months ago, it was on a completely different motherboard (completely BIOS-based) and NumLock showed as lit on the keyboard and worked when switching to a text console, and this was with the same exact keyboard as I use on openSUSE. Just to be sure, I checked again in the UEFI BIOS settings of my motherboard and there is nothing there for for NumLock, surprising as it may be. If I am to open a bug report, what should I report it against? Base system. It's probably systemd that is in charge to starting the consoles, but it's not systemd that is doing the initialisation.
I think its getty, not sure if that is now part of systemd or not.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm composed on 2016-04-07 06:45 (UTC-0700):
If I am to open a bug report, what should I report it against?
If the motherboard is relatively recent, it's manufacturer. Since when do desktop motherboards not have a firmware option for startup NUM state? Did you check to see if an update is already available? Who made it? What model is it? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/07/2016 11:28 AM, Felix Miata wrote:
sdm composed on 2016-04-07 06:45 (UTC-0700):
If I am to open a bug report, what should I report it against?
If the motherboard is relatively recent, it's manufacturer. Since when do desktop motherboards not have a firmware option for startup NUM state? Did you check to see if an update is already available? Who made it? What model is it? MSI Z68A-GD65, you can search on Google and find people complaining with similar MSI boards that there is no NumLock option. I searched up and down, it's not there. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm composed on 2016-04-07 12:34 (UTC-0700):
Felix Miata wrote:
sdm composed on 2016-04-07 06:45 (UTC-0700):
If I am to open a bug report, what should I report it against?
If the motherboard is relatively recent, it's manufacturer. Since when do desktop motherboards not have a firmware option for startup NUM state? Did you check to see if an update is already available? Who made it? What model is it?
MSI Z68A-GD65, you can search on Google and find people complaining with
https://us.msi.com/Motherboard/Z68AGD65_G3.html ?
similar MSI boards that there is no NumLock option. I searched up and down, it's not there.
Hard to figure out whether that's newer or older than mine, purchased last Sept., to evaluate similarity: https://us.msi.com/Motherboard/B85-G41-PC-Mate.html I have no such NUM trouble, but am not interested in rebooting 42.1 or booting TW any time soon to looksee in setup whether I have a NUM state option or not. I will try to keep it in mind for when next reboot comes to pass. I guess yours is older, with only Ivy Bridge and Sandy Bridge compat listings. Mine is Haswell, so maybe MSI already got a hint users don't like not having a NUM option, and put it back in newer products. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-04-06 17:55, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active.
Not at all. You can toggle the LED alone by software. I played with that on another life. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlcFgiIACgkQja8UbcUWM1w7sQD+LcCekg+b64kWDrBij6TtoL50 dTusST16HdH4fzv1r+AA/2ZiwsQ5EV+4/+um+9YV1OxRYy8ppotoBZw0+r0Fl2PX =qx8q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2016-04-06 17:55, Per Jessen wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active.
Not at all. You can toggle the LED alone by software. I played with that on another life.
Probably, but it still sounds weird that it should happen. -- Per Jessen, Zürich (9.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2016-04-07 at 08:17 +0200, Per Jessen wrote:
Carlos E. R. wrote:
Any chance it might be a hardware issue? It really sounds weird for the NumLock LED to be lit without the numerical keypad being active.
Not at all. You can toggle the LED alone by software. I played with that on another life.
Probably, but it still sounds weird that it should happen.
Of course. But the thing is, the LED in the keyboard is set from the computer, and independently, somewhere else in software there is a status kept for upper/lower case. And in Linux, one for graphics, another for text, and maybe one per seat login. To complicate things, I don't think the LED status can be read. That explains why the "real" status and what the LED says can be different. If I remember correctly, the keyboard sends the same key codes regardless of the LED or keyboard flag status. Ie, it is the software which reads 'a' then thinks "no, it is 'A'". But this I'm not sure at the moment, it has been more than a decade since I played with these low level things. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcGULwACgkQtTMYHG2NR9V+rQCePz35aLVCiTtq9lg2ixCo1jMJ vBIAniKenlQ+50LcPT+zIQ/MHNHbfgBA =jwrm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
sdm composed on 2016-04-06 03:33 (UTC-0700):
On TW (and this is probably the same for Leap), on my desktop PC I want NumLock to be on every time I boot the computer. The default is for NumLock to be off but as my login password has numbers in it, I like using the number pad.
Same here.
I tried Fedora on the same machine a while back and it defaulted to NumLock being on every time the machine booted.
It seems to me that NumLock being on during boot would be a sensible default, so why is the default for it to be off?
Laptop keyboards probably, and it's the legacy PC keyboard state.
And what is the best way to set it to be on every time my PC boots?
I don't think I've yet run across a PC without a BIOS option to start with NUM state on. Laptops are another matter. Their keyboards rarely support worth a hoot a NUM state maintained on.
Another annoyance is that when I switch to, let's say TTY1 from a graphical session on TTY7, the NumLock Key shows lit on my keyboard. But when logging in on TTY1, NumLock really isn't on, just the light is list. So I have to press NumLock again and the light stays lit, and then the Num Pad works. Is this the current default or something with whatever driver is driving my keyboard?
Is numlockx not installed on yours? If so, NUM should be on in the greeter whether the keyboard NUM state is in sync or not. /etc/sysconfig/keyboard on all my installations early on get the following: ## Type: integer ## Default: # # Keyboard delay time in ms (250, 500, 750, 1000) KBD_DELAY="250" ## Type: string(2.0,2.1,2.3,2.5,2.7,3.0,3.3,3.7,4.0,4.3,4.6,5.0,5.5,6.0,6.7,7.5,8.0,8.6,9.2,10.0,10.9,12.0,13.3,15.0,16.0,17.1,18.5,20.0,21.8,24.0,26.7,30.0) ## Default: # # Keyboard repeat rate (2.0 - 30.0) KBD_RATE="20" ## Type: list(bios,yes,no) ## Default: bios # # NumLock on? ("yes" or "no" or empty or "bios" for BIOS setting) # This setting may interfere with GNOME /desktop/gnome/peripherals/keyboard/remember_numlock_state GConf key. KBD_NUMLOCK="yes" Maybe having both numlockx installed and working plus "yes" in keyboard will solve your LED sync problem on both 42.1 and TW. If not, man setleds and adjust your login's .bash_profile. I've needed setleds on lots of installations in the past, but it has been a while. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R.
-
Felix Miata
-
ianseeks
-
Per Jessen
-
sdm