You are not logged in.
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)
Offline
Is it related to this? https://www.archlinux.org/news/linux-31 … w-modular/
(Sorry if I misunderstood your question. I'm really tired. )
Offline
Does it sound like the kernel build error for the keyboard is related to the announcement about modular keyboard support?
I suppose it's possible that you determined (as explained in the announcement) that you needed to add "atkbd" to the MODULES, but accidentally wrote "keyboard" instead.
Offline
Is it related to this? https://www.archlinux.org/news/linux-31 … w-modular/
(Sorry if I misunderstood your question. I'm really tired. )
Yes.
Offline
I suppose it's possible that you determined (as explained in the announcement) that you needed to add "atkbd" to the MODULES, but accidentally wrote "keyboard" instead.
My computer does not have a PS/2 port, so the announcement does not apply. Not sure when/why I added the "keyboard" to MODULES.
The build error is now fixed - I removed "keyboard" from MODULES in /etc/mkinitcpio.conf .
Although I still have an unresponsive mouse and keyboard after XFCE launches.
Offline
My computer does not have a PS/2 port, so the announcement does not apply.
I'm not positive, but I think the built-in touchpads and pointer devices in laptops are usually implemented internally as PS/2.
Offline
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.
Offline
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)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
Yes, that's something I wasn't aware of! Thank you all.
Offline
Your understanding is correct, but that also shows that many systems without a visible ps/2 port still have the controller for it !
It kind of makes sense. Whatever the keyboard is connected to, it's the only thing that's ever going to be connected there. Plus, there are (or were until recently) certain limitations and considerations wrt USB kbds. Years ago, I had a distressing experience after setting up a new mobo to power on with a 'password'.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline