You are not logged in.

#1 2019-02-04 14:32:57

pvenkman
Member
Registered: 2016-01-09
Posts: 6

[SOLVED] No keyboard input at [encrypt] hook possible after system upg

Hi,
I just updated my arch installation to version 240. mkinitcpio did not bring up any errors and built the images successfully. After rebooting I am able to get into the boot loader and use the keyboard, if the boot continues however and gets to the [encrypt] hook, I am no longer able to input the encryption passphrase. I tried connecting a PS/2 keyboard as well (and rebooting) - to no avail.

Please provide tips on how to solve this issue. Thank you.

Last edited by pvenkman (2019-02-04 20:30:16)

Offline

#2 2019-02-04 15:23:09

schard
Member
From: Hannover
Registered: 2016-05-06
Posts: 367
Website

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

Please provide the output of

$ grep ^HOOKS /etc/mkinitcpio.conf

And did you build the initramfs with a keyboard connected to the machine in question?

Last edited by schard (2019-02-04 15:24:23)

Offline

#3 2019-02-04 16:29:23

pvenkman
Member
Registered: 2016-01-09
Posts: 6

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

/etc/mkinitcpio.conf:
HOOKS=(base udev autodetect modconf block mdadm_udev encrypt lvm2 filesystems keyboard fsck)

Yes, a keyboard was connected at the time of build

Offline

#4 2019-02-04 17:01:18

schard
Member
From: Hannover
Registered: 2016-05-06
Posts: 367
Website

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

Try moving the keyboard hook before the autodetect hook and rebuild the initramfs.

Offline

#5 2019-02-04 17:36:16

frostschutz
Member
Registered: 2013-11-15
Posts: 760

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

otherwise, add keyboard related modules directly to mkinitcpio.conf MODULES (a few threads recently had atkbd missing on laptops)

Offline

#6 2019-02-04 20:29:50

pvenkman
Member
Registered: 2016-01-09
Posts: 6

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

Moving the keyboard hook solved the keyboard issue. However the initramfs I built failed at first because the "ext4" module was missing. After adding that to the MODULES section and rebuilding again, I was able to boot successfully.

Thanks for your support.

Quick follow-up. You asked about a keyboard being plugged in. https://wiki.archlinux.org/index.php/mkinitcpio nowhere mentions a need for that. Can you point me to a resource? ext4 seems to be a similar "detected" feature. I had built initramfs nearly every week for the last 2,5 years on that system, ext4 never went missing.

Last edited by pvenkman (2019-02-04 20:41:44)

Offline

#7 2019-02-04 23:49:57

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 2,535

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

pvenkman wrote:

Quick follow-up. You asked about a keyboard being plugged in. https://wiki.archlinux.org/index.php/mkinitcpio nowhere mentions a need for that. Can you point me to a resource?

arch wiki wrote:

Tip: For systems that are booted with different hardware configurations (e.g. laptops with external keyboard vs. internal keyboard or headless systems), it is helpful to place this hook before autodetect in order to always include all keyboard drivers. Otherwise the external keyboard only works in early userspace if it was connected when creating the image.

https://wiki.archlinux.org/index.php/mk … mmon_hooks

Offline

#8 2019-02-05 00:01:56

pvenkman
Member
Registered: 2016-01-09
Posts: 6

Re: [SOLVED] No keyboard input at [encrypt] hook possible after system upg

2ManyDogs wrote:
pvenkman wrote:

Quick follow-up. You asked about a keyboard being plugged in. https://wiki.archlinux.org/index.php/mkinitcpio nowhere mentions a need for that. Can you point me to a resource?

arch wiki wrote:

Tip: For systems that are booted with different hardware configurations (e.g. laptops with external keyboard vs. internal keyboard or headless systems), it is helpful to place this hook before autodetect in order to always include all keyboard drivers. Otherwise the external keyboard only works in early userspace if it was connected when creating the image.

https://wiki.archlinux.org/index.php/mk … mmon_hooks

Thanks for pointing that out. I did read the whole section and especially the keyboard hook multiple times but did not arrive at that conclusion. I will propose changing this to something like "Warning: this hook will be ignored if no keyboard is plugged in". I would expect some sort of keyboard support to always be included when the keyboard hook is specified.

Last edited by pvenkman (2019-02-05 00:20:07)

Offline

Board footer

Powered by FluxBB