Arch Linux User Repository

For anyone who wants to keep the automatic numlock in the initrd after switching to systemd, I've made a small systemd unit which I've shared with the community as the mkinitcpio-sd-numlock package (the mkinitcpio hook is called sd-numlock).

It's a "pure" systemd unit (no shell script), so it work even if you remove the base hook (which is optional when using systemd).

For anyone who wants to keep the automatic numlock in the initrd after switching to systemd, I've made a small systemd unit which I've shared with the community as the mkinitcpio-sd-numlock package (the mkinitcpio hook is called sd-numlock).

It's a "pure" systemd unit (no shell script), so it work even if you remove the base hook (which is optional when using systemd).

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

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.

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.

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