Arch Linux

WalterSmuts

Member

Registered: 2018-03-31

Posts: 10

[SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

On boot I get the message

Failed to start Load Kernel Modules

This had the effect of breaking startx and any attempt at connecting to a network via wifi or ethernet cable. I assume drivers weren't loaded and/or some services weren't started.

Eventually I figured out that I must have upgraded linux since my last boot and the new version linux-4.17.3-1 may have caused the system to break. So I booted into a live-usb, chrooted, and downgraded to linux-4.17.2-1.

This seems to have fixed the problem but I don't see it as a permanent solution since I'd like to keep my system up to date. After reading the Arch-Newbie corner forum sticky post I checked out the news and found the latest post.

Seems like I had to "intervene" to upgrade successfully. Well I did what the post said, then upgraded and still had the same issue.

Currently I'm assuming the latest post had nothing to do with my issue but I may be wrong. What's my next step to try to have a successful upgrade?

Last edited by WalterSmuts (2018-07-15 19:38:12)

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

Welcome to the arch linux forums WalterSmuts.  Systemd#Investigating_systemd_errors.  Is /boot on a separate filesystem if so was it mounted when the kernel was updated?

WalterSmuts

Member

Registered: 2018-03-31

Posts: 10

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

I have everything in a single partition. Only other partitions I've created was the swap partition and the EFI partition.

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

Update the package again then reboot and what is the output of

pacman -Q linux
uname -a

WalterSmuts

Member

Registered: 2018-03-31

Posts: 10

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

Before updating (Still Works):

uname -a
Linux cuddles 4.17.2-1-ARCH #1 SMP PREEMPT Sat Jun 16 11:08:59 UTC 2018 x86_64 GNU/Linux

pacman -Q linux
linux 4.17.2-1

After updating(Doesn't work anymore):

uname -a
Linux cuddles 4.17.2-1-ARCH #1 SMP PREEMPT Sat Jun 16 11:08:59 UTC 2018 x86_64 GNU/Linux

pacman -Q linux
linux 4.17.3-1

So version numbers are different.

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

What bootloader is the system using?  Also if mount the EFI partition to /mnt does it contain vmlinuz-linux and initramfs-linux.img?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,104

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

And how did you set up your UEFI? If you used systemd-boot you must generate the kernel's initramfs onto the UEFI partition, which is most painlessly done by simply mounting the EFI partition to /boot . If that isn't the case you run in the issue you are running into, namely that your initramfs is refering to an old kernel on your EFI partition that doesn't match the one currently installed.

Also because it will guaranteed run you into another problem eventually. If you've followed the news item despite not getting the error referenced in the news item, you shouldn't be doing that action either. After successfully mounting /boot run the next upgrade operation explicitly with

pacman -Syu js52

to ensure that is correct as well.

WalterSmuts

Member

Registered: 2018-03-31

Posts: 10

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

What bootloader is the system using?

GRUB.

Also if mount the EFI partition to /mnt does it contain vmlinuz-linux and initramfs-linux.img?

Yep

And how did you set up your UEFI?

I followed this guide to install. I believe I've got an UEFI system. Got a zenbook UX305U. But this is probably where the error is originating from. What do you suggest I do?

If you've followed the news item despite not getting the error referenced in the news item, you shouldn't be doing that action either.

I only moved the file. Then upgraded. Then rebooted. Realised it still didn't work. Then downgraded. Then moved the file back. This should have been safe right?

Last edited by WalterSmuts (2018-07-03 15:32:41)

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

The simplest is add an fstab entry mounting the ESP to /boot.  Mount /boot then reinstall the linux package.  Unmount /boot then remove anything in /boot eg vmlinuz-linux and initramfs-linux.img
so that an empty directory is left as the mout point.  Reboot and check all then works as expected.

RickDeckard

Member

From: Acworth, Georgia, USA

Registered: 2016-02-19

Posts: 59

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

The simplest is add an fstab entry mounting the ESP to /boot.  Mount /boot then reinstall the linux package.  Unmount /boot then remove anything in /boot eg vmlinuz-linux and initramfs-linux.img
so that an empty directory is left as the mout point.  Reboot and check all then works as expected.

Are you sure the ESP goes there?  I believe the correct location for it would be /boot/efi.  The boot partition should just be a regular ext2/4.

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

Are you sure the ESP goes there?  I believe the correct location for it would be /boot/efi.  The boot partition should just be a regular ext2/4.

I have everything in a single partition. Only other partitions I've created was the swap partition and the EFI partition.

With no separate boot partition and the kernel currently being installed on the ESP mounting the ESP to /boot would involve less changes than using /boot/efi either location can be used with the appropriate configuration.

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,694

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

The simplest is add an fstab entry mounting the ESP to /boot.  Mount /boot then reinstall the linux package.  Unmount /boot then remove anything in /boot eg vmlinuz-linux and initramfs-linux.img
so that an empty directory is left as the mout point.  Reboot and check all then works as expected.

Are you sure the ESP goes there?  I believe the correct location for it would be /boot/efi.  The boot partition should just be a regular ext2/4.

In some configurations, maybe, but not in general. Honestly, having a separate /boot partition that's ext2 or ext4 is almost always totally useless.

WalterSmuts

Member

Registered: 2018-03-31

Posts: 10

Re: [SOLVED] Breaks after upgrading from linux-4.17.2-1 to linux-4.17.3-1

Sorry for the long wait. Life got in the way.

Anyways. I created an fstab mounting the efi partition to boot and re-installed grub (Not sure if it was necessary). All works now! Thanks so much!

How to I mark this thread as solved?