Num lock LED doesn't light up while Num lock state is "on" via PS/2 A4 Tech keyboard

[Ihor Romanyshyn]

With my PS/2 A4 Tech keyboard, Num lock LED doesn't light up while Num lock state is "on". If you press Num lock key, it will be put to "off". And when you press it again, it will be "on" and LED will on. In some cases LED will be off again while Num keys will continue to work same as Num LED is enabled. All above is true for logon screen, for desktop and for terminals by ctrl+alt+F[1-6]. Found it on multiple computers with numpad. This bug presents on v3.17-rc2-utopic and v3.17-rc3-utopic too.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-35-generic 3.13.0-35.62
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ihor 2025 F.... pulseaudio
Date: Tue Sep 2 13:57:03 2014
HibernationDevice: RESUME=UUID=22d29605-7b7f-4743-9e46-c30f09460dfa
InstallationDate: Installed on 2014-08-07 (26 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=0a0a156d-8fc5-473d-bb54-ef83d71e2feb ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-35-generic N/A
 linux-backports-modules-3.13.0-35-generic N/A
 linux-firmware 1.127.5
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd11/30/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Ihor Romanyshyn, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Motherboards/M5A78LM_LX/HelpDesk_Download/ an update to your BIOS is available (1603). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

[Ihor Romanyshyn (iromanyshyn)]

Christopher, thank you! I'm updated BIOS and it works fine!

[Ihor Romanyshyn (iromanyshyn)]

Oops, still remain the same problem. Num lock LED switched off suddenly but numpad is working as Num lock is on.

[Ihor Romanyshyn (iromanyshyn)]

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

1603
11/05/2013

[penalvch (penalvch)]

Ihor Romanyshyn, did this problem not occur in a release prior to Trusty?

[Ihor Romanyshyn (iromanyshyn)]

Christopher M. Penalver (penalvch), i found it sooner on 13.10, maybe. But that problem was most in virtual terminals.

[penalvch (penalvch)]

Ihor Romanyshyn, for regression testing purposes, could you please test Precise 12.04.0 via http://old-releases.ubuntu.com/releases/12.04.0/ and advise to the results?

As well, what type of keyboard would you be using specifically (ex. bluetooth mfg/model)?

If bluetooth, would you have another keyboard (ex. USB corded) that you could do a test to see if this happens with it as well?

[Ihor Romanyshyn (iromanyshyn)]

Will test 12.04 live-USB later. In all cases, keyboards are PS/2 A4 Tech or Genius without any additional keys/features.

[Ihor Romanyshyn (iromanyshyn)]

Now testing Linux ubuntu 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux.
System has booted with Numlock state off and LED is off too. But, when i switch to virtual terminal by ctrl+alt+F2, i got the same problem: Num lock state is on, but LED doesn't light.

[penalvch (penalvch)]

Ihor Romanyshyn, if you have kernel 3.8.x you would appear to have downloaded the incorrect release (12.04.3). What was requested was 12.04.0 (kernel 3.2.x).

[Ihor Romanyshyn (iromanyshyn)]

Sorry, tested again on Linux ubuntu 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux. System was booted with Num lock off, real is "off" too. In virtual terminals Num lock was off and LED was off. But, when i enabled Num lock at desktop and switched to terminal, i got enabled LED, and disabled Num lock.

[penalvch (penalvch)]

Ihor Romanyshyn, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked.

Thank you for your understanding.