Package Details: mkinitcpio-numlock 1.0.3-1

Git Clone URL: https://aur.archlinux.org/mkinitcpio-numlock.git (read-only, click to copy)
Package Base: mkinitcpio-numlock
Description: Enable numlock in early userspace
Upstream URL: https://bbs.archlinux.org/viewtopic.php?pid=869618
Licenses: GPL
Submitter: matejgroma
Maintainer: matejgroma
Last Packager: matejgroma
Votes: 18
Popularity: 0.91
First Submitted: 2015-09-01 13:57 (UTC)
Last Updated: 2019-09-15 13:19 (UTC)

Latest Comments

mmelvin0 commented on 2021-12-05 04:09 (UTC) (edited on 2021-12-05 05:39 (UTC) by mmelvin0)

EDIT: Disregard. This was apparently entirely to due with VMware guest clock out of sync with host, and nothing to do with this package...

I found a strange bug. If I have this hook enabled like so in my mkinitcpio.conf:

HOOKS=(base udev autodetect modconf block filesystems keyboard numlock fsck)

systemd-journald does not start up correctly! This can be verifies by checking dmesg and comparing to the journal. systemd-journald logs a message at each boot to dmesg about the journal being corrupt, and checking the journal, all boot messages, including those about systemd-journald starting are lost.

Upon removing the numlock hook, rebuilding my initial ramdisk, and rebooting (twice, since the next boot yields the same thing) resolves the issue.

blaubos commented on 2021-03-14 01:59 (UTC) (edited on 2021-03-14 01:59 (UTC) by blaubos)

Please note that for this package to have any effect, you must add the numlock hook to some point of HOOKS in /etc/mkinitcpio.conf. I added it before block, right after modconf. Then, you will need to re-generate all your mkinitcpio images:

# mkinitcpio -P