[SOLVED] Am I having kernel issues due to the modular keyboard

Question

Kernel 3.12.7-2 runs fine on my Lenovo X220 laptop.
However, any newer kernel results in my XFCE booting into a live desktop, but without control over keyboard or mouse.
Logging in via the second virtual terminal tells me:
$ systemctl --failed
netcfg.service loaded failed failed Netcfg multi-profile daemon
When running $ sudo pacman -Syu last, I received the following error message (with context):
[2014-04-23 10:32] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-04-23 10:32] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Starting build: 3.14.1-1-ARCH
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> ERROR: module not found: `keyboard'
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Starting build: 3.14.1-1-ARCH
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-04-23 10:32] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> ERROR: module not found: `keyboard'
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2014-04-23 10:32] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
[2014-04-23 10:32] [ALPM-SCRIPTLET] >>> WARNING: AT keyboard support is no longer built into the kernel.
[2014-04-23 10:32] [ALPM-SCRIPTLET] >>> In order to use your keyboard during early init, you MUST
[2014-04-23 10:32] [ALPM-SCRIPTLET] >>> include the 'keyboard' hook in your mkinitcpio.conf.
Note the "ERROR: module not found: `keyboard'".
My /etc/mkinitcpio.conf file contains:
MODULES="i915 keyboard"
BINARIES=""
FILES=""
HOOKS="base udev autodetect modconf block filesystems keyboard fsk"
Does it sound like the kernel build error for the keyboard is related to the announcement about modular keyboard support?
If so, I have not been able to further connect the dots on my own to track down the cause, which is why I'm looking for others' insights now.
Last edited by eoinoc333 (2014-04-24 08:34:55)

Answer 1

eoinoc333 wrote:
To be sure, I ran the command from the announcement:
$ dmesg -t | grep '^i8042'
i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
From my understanding, that means I don't have to take action regarding that announcement. Thanks for the comment.
Your understanding is correct, but that also shows that many systems without a visible ps/2 port still have the controller for it !
Last edited by Lone_Wolf (2014-04-25 11:44:22)