Clarification needed on "PS/2 keyboard support is now modular" news

lightstream · 2014-02-26 12:27:33

I read the news item mentioned in my post, and it seems my motherboard is one of the ones that doesn't allow automatic detection of the i8042 controller, because I get the message about "No PS/2 controller found. Probing ports directly."

So I've added atkbd to the MODULES= line in mkinitcpio.conf and run mkinitcpio -P

After reboot, I get the same message "No PS/2 controller found. Probing ports directly."

Is this correct, or does it mean my atkbd module isn't being loaded or something?

This is probabaly obvious to most people, but it's possible that I'm somehow booting off a different boot partition - I don't think that's the case so I just want to be sure the fix is working for me before I upgrade.

karol · 2014-02-26 12:37:00

Post your /etc/mkinitcpio.conf. Do you get any errors when running mkinitcpio?

graysky · 2014-02-26 12:54:13

Did you add "earlymodules=atkbd modules-load=atkbd" to your kernel line?

lightstream · 2014-02-26 12:57:18

My /etc/mkinitcpio.conf:

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="atkbd"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=""

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

No apparent errors from running mkinitcpio:

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.12.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.12.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

So does this mean that I should no longer get this message about 'No PS/2 controller found' from dmesg?

I have two drives in this PC (it's maybe 4 years old) - the one that /should/ be booting is an SSD that has a boot directory (rather than a separate boot partition), while the old drive has a separate boot partition. I really hope I'm booting off the new drive, but I could be mistaken. I'm going to do some checks now to try to rule that out.

lightstream · 2014-02-26 12:59:13

graysky wrote:

Did you add "earlymodules=atkbd modules-load=atkbd" to your kernel line?

Graysky - no I didn't, I thought that was only if you hadn't made the fixes to mkinitcpio.conf?

I haven't yet updated, so my keyboard is still working fine. I just want to make sure all's OK first

karol · 2014-02-26 13:01:26

You said you did reboot. What do you mean by "I haven't yet updated"?
Apart from the message in dmesg, do you have any problems with the keyboard?

lightstream · 2014-02-26 13:03:29

karol wrote:

You said you did reboot. What do you mean by "I haven't yet updated"?
Apart from the message in dmesg, do you have any problems with the keyboard?

I haven't run pacman yet to update my system - I first checked the news & saw the current item about keyboard, so I've made the changes to mkinitcpio.conf and I rebooted (but still no updates yet)

lightstream · 2014-02-26 13:04:01

and no, my keyboard is currently working fine, as I haven't updated yet

karol · 2014-02-26 13:11:13

Check your bootloader to see which partition are you booting from.
Update your system and keep your fingers crossed when you reboot. You should always have a liveCD / liveUSB and the instructions on how to chroot etc. on hand.

lightstream · 2014-02-26 13:34:59

OK I discovered my system is still booting off the boot partition on the old spinning disk.

I now seem to remember modifying Grub on that partition to boot into Linux on the SSD as a temporary measure, and I then forgot all about it.

I'm going to have to take a bit of time after work & try and sort it out properly.

Thanks a lot for your help karol & graysky

Arch Linux

#1 2014-02-26 12:27:33

Clarification needed on "PS/2 keyboard support is now modular" news

#2 2014-02-26 12:37:00

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#3 2014-02-26 12:54:13

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#4 2014-02-26 12:57:18

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#5 2014-02-26 12:59:13

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#6 2014-02-26 13:01:26

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#7 2014-02-26 13:03:29

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#8 2014-02-26 13:04:01

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#9 2014-02-26 13:11:13

Re: Clarification needed on "PS/2 keyboard support is now modular" news

#10 2014-02-26 13:34:59

Re: Clarification needed on "PS/2 keyboard support is now modular" news

Board footer