Arch Linux

thaniel

Member

Registered: 2015-07-05

Posts: 5

[SOLVED] Not booting to updated kernel

I recently tried to update the kernel with pacman.  This is my first kernel update: I installed arch for the first time about a month ago.

Everything seems to go just fine until I reboot, upon which systemd-modules-load.service fails and I understandabley can't start Xorg.  Before the reboot I ran

sudo dkms autoinstall -k 4.1.2-2-ARCH

and

catalyst-build-module 4.1.2-2-ARCH

both of which seem to execute properly.  This is the relevant output from pacman.log:

[2015-07-28 19:00] [ALPM] upgraded linux (4.0.7-2 -> 4.1.2-2)
[2015-07-28 19:00] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2015-07-28 19:00] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Starting build: 4.1.2-2-ARCH
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Image generation successful
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Starting build: 4.1.2-2-ARCH
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: wd719x
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2015-07-28 19:00] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2015-07-28 19:00] [ALPM-SCRIPTLET] ==> Image generation successful
[2015-07-28 19:00] [ALPM] upgraded linux-headers (4.0.7-2 -> 4.1.2-2)

All the modules get loaded into /usr/lib/modules/4.1.2-2-ARCH, but upon boot it says that I am still running 4.0.7-2-ARCH,

uname -a

confirms this. However, 

pacman -Q linux

returns 4.1.2-2.

I downgraded for now and am using 4.0.7-2 for the time being but would like to upgrade.

I am using EFISTUB to boot.  It seems to me that EFISTUB is still trying to boot the old kernel version, but there are no longer any modules for it to load as they are all now in the 4.1.2-2 directory.  What else might I try to get my machine to boot the new kernel?

Last edited by thaniel (2015-07-29 05:06:55)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] Not booting to updated kernel

You probably updated your kernel without the ESP mounted.

thaniel

Member

Registered: 2015-07-05

Posts: 5

Re: [SOLVED] Not booting to updated kernel

Right you are sir!  Problem solved.  Ran

sudo mount -a

and did the update again and everything is working fine.

Thank you!