[Bug 1180962] New: Kernel did not see the status numlock from bios.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 Bug ID: 1180962 Summary: Kernel did not see the status numlock from bios. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: virex@mail.ru QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Kernel did not see the status numlock from bios. After several updates I found what the numlock status is off by default. Checking the setting in BIOS. It is on by default With settings KBD_NUMLOCK="bios" in /etc/sysconfig/keyboard it is always off. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@suse.com, | |virex@mail.ru Flags| |needinfo?(virex@mail.ru) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Do you get the correct status if you run /usr/lib/kbd/numlockbios manually? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c2 --- Comment #2 from Igor Kuznetsov <virex@mail.ru> --- #/usr/libexec/kbd/numlockbios on numlockbios read this status correctly. So the KBD_NUMLOCK="bios" settings in file /etc/sysconfig/keyboard do not work correct. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- OK, then run /usr/sbin/kbdsettings once (at best on VT1). Does it change the LED status correctly? This should have been called from systemd kbdsettings.service, and you can see the status from systemctl. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c4 --- Comment #4 from Igor Kuznetsov <virex@mail.ru> --- after starting kbdsettings led is did not switch to on # /usr/sbin/kbdsettings status of kbdsettings is: lnxvrxtosh:/home/virex # systemctl status kbdsettings ��� kbdsettings.service - Apply settings from /etc/sysconfig/keyboard Loaded: loaded (/usr/lib/systemd/system/kbdsettings.service; enabled; vend> Active: active (exited) since Sun 2021-01-17 12:05:48 +04; 1h 3min ago Process: 777 ExecStart=/usr/sbin/kbdsettings (code=exited, status=0/SUCCESS) Main PID: 777 (code=exited, status=0/SUCCESS) ������ 17 12:05:47 lnxvrxtosh systemd[1]: Starting Apply settings from /etc/syscon> ������ 17 12:05:48 lnxvrxtosh systemd[1]: Finished Apply settings from /etc/syscon> lnxvrxtosh:/home/virex # systemctl restart kbdsettings lnxvrxtosh:/home/virex # systemctl status kbdsettings ��� kbdsettings.service - Apply settings from /etc/sysconfig/keyboard Loaded: loaded (/usr/lib/systemd/system/kbdsettings.service; enabled; vend> Active: active (exited) since Sun 2021-01-17 13:09:06 +04; 2s ago Process: 27148 ExecStart=/usr/sbin/kbdsettings (code=exited, status=0/SUCCE> Main PID: 27148 (code=exited, status=0/SUCCESS) ������ 17 13:09:06 lnxvrxtosh systemd[1]: Stopped Apply settings from /etc/sysconf> ������ 17 13:09:06 lnxvrxtosh systemd[1]: Stopping Apply settings from /etc/syscon> ������ 17 13:09:06 lnxvrxtosh systemd[1]: Starting Apply settings from /etc/syscon> ������ 17 13:09:06 lnxvrxtosh systemd[1]: Finished Apply settings from /etc/syscon> -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- Now let's check whether the setleds that was invoked in the script actually works. e.g. try /usr/bin/setleds -D +num < /dev/tty1 on VT1. Does it enable the numlock LED? (Also -D -num to disable LED.) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c6 --- Comment #6 from Igor Kuznetsov <virex@mail.ru> --- /usr/bin/setleds -D +num < /dev/tty7 switch on led in graphic mode also it is work on tty1-5 in console mode /usr/bin/setleds -D +num < /dev/tty1..5 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c7 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-bugs@opensuse.org |sbrabec@suse.com Flags|needinfo?(virex@mail.ru) | --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- OK, thanks. Then this sounds more like a problem in the invocation of setleds. My wild guess is that no TTY is available at the time this command is invoked by systemd (or other terminal than TTY1-6 is active), while setleds works only for the active terminal. Reassigned to kbd package maintainer. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1180962 https://bugzilla.suse.com/show_bug.cgi?id=1180962#c9 Igor Kuznetsov <virex@mail.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Igor Kuznetsov <virex@mail.ru> --- perhaps it is work now -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com