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: 44
Popularity: 1.48
First Submitted: 2015-09-01 13:57 (UTC)
Last Updated: 2019-09-15 13:19 (UTC)

Dependencies (2)

Required by (0)

Sources (2)

Pinned Comments

matejgroma commented on 2025-06-12 09:23 (UTC)

I have it enabled early on in the system, before sd-encrypt.

This currently implements only a mkinitcpio runtime hook, so it won't work with a systemd-based init. From [1]:

Runtime hooks are only used by busybox init. The systemd hook triggers a systemd-based init, which does not run any runtime hooks but uses systemd units instead.

I may eventually get around to implementing proper support for this, as it would be useful for me as well.

[1] https://wiki.archlinux.org/title/Mkinitcpio#Runtime_hooks

Latest Comments

matejgroma commented on 2025-06-12 09:23 (UTC)

I have it enabled early on in the system, before sd-encrypt.

This currently implements only a mkinitcpio runtime hook, so it won't work with a systemd-based init. From [1]:

Runtime hooks are only used by busybox init. The systemd hook triggers a systemd-based init, which does not run any runtime hooks but uses systemd units instead.

I may eventually get around to implementing proper support for this, as it would be useful for me as well.

[1] https://wiki.archlinux.org/title/Mkinitcpio#Runtime_hooks

Tellik commented on 2025-06-12 08:41 (UTC)

I've been having an issue getting this to work when using a LUKS2 encrypted drive, for it to enable early enough so that it's enabled before it asks for the LUKS2 password.

I have it enabled early on in the system, before sd-encrypt.

Was wondering if anyone had any suggestions for this situation.

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