failed start kernel modules on reboot after kernel update

YXdev · 2020-12-10 05:36:54

this is on a new arch install, system is Dell System Inspiron N4110 so it's BIOS

after I ran pacman -Syu to update the kernel from 5.9.12 to 5.9.13 , I rebooted to find that the error message "Fail to start load Kernel Modules."

So I used a bootable iso of arch to mount all of my drives and arch-chroot into my install, I first checked my fstab to see if my boot drive was being mounted on reboot, it was. So i reinstalled the kernel and still got the same results

I regenerated the initramfs and rebooted, still nothing

using grub-mkconfig -o /boot/grub/grub.cfg to remake the grub config didn't work either

so I downgraded the kernel back to 5.9.12, after I did that the system booted up correctly

so I checked journalctl and it says "failed to look up module alias 'crytpo_user': Function not Implemented " and the same message for 'sg'

Pacman logs don't seem to show anything wrong either.

whenever I reboot after updating to 5.9.13 it takes longer than usual, black screen for at least 20 seconds before it shuts down

I don't think I messed around with any root files beforehand

for the time being I have pacman ignore the linux package on updates

Last edited by YXdev (2020-12-10 06:00:02)

seth · 2020-12-10 08:01:34

What's the output of "uname -a" after updating the kernel?
The alternative to forgetting to mount /boot is to actually (and accidentally) boot from the root device but placing the new kernel into the /boot partition.

YXdev · 2020-12-10 08:19:09

seth wrote:

What's the output of "uname -a" after updating the kernel?
The alternative to forgetting to mount /boot is to actually (and accidentally) boot from the root device but placing the new kernel into the /boot partition.

I can't get the output of uname -a because Im chrooted in and it gives me the kernel for the arch iso, and when I'm not using a usb and instead use ctrl+alt+f2 after the error shows up the command returns the 5.9.12 kernel, but pacman -Q linux returns 5.9.13

Im not booting from the root folder

seth · 2020-12-10 08:41:32

the command returns the 5.9.12 kernel, but pacman -Q linux returns 5.9.13

Well…

Im not booting from the root folder

… we'll see:

From the chroot, mount your installation root to /mnt and check

file /mnt/boot/vmlinuz-linux

Then mount your boot partition to /mnt-boot and check

file /mnt-boot/vmlinuz-linux

YXdev · 2020-12-11 10:56:44

so is this why my root directory looks like this

bin Desktop etc lib lost+found opt root sbin sys usr
boot dev home lib64 mnt proc run srv tmp var

seth · 2020-12-11 12:10:34

What's that's supposed to be good for?
You want to know whether you've a kernel in the /boot path of the root partition and in the / path of the boot partition and in case, which version either of them is.
The filesystem structure of the root partition is irrelevant.

Arch Linux

#1 2020-12-10 05:36:54

failed start kernel modules on reboot after kernel update

#2 2020-12-10 08:01:34

Re: failed start kernel modules on reboot after kernel update

#3 2020-12-10 08:19:09

Re: failed start kernel modules on reboot after kernel update

#4 2020-12-10 08:41:32

Re: failed start kernel modules on reboot after kernel update

#5 2020-12-11 10:56:44

Re: failed start kernel modules on reboot after kernel update

#6 2020-12-11 12:10:34

Re: failed start kernel modules on reboot after kernel update

Board footer