Failed to start Load Kernel Modules

sudo pacman -Syyu && grup-mkconfig gives me many “error: failed retrieving file ‘core.db’ from…”

Can you execute ping manjaro.org to see if networking is working, please?

ok yes, haha, I was not connected to the internet. But once I did get connected I ran the commands again and I got “there is nothing to do” for the first part (I updated it yesterday, so not surprising), but It also said it couldn’t find grup-mkfile…did you mean to say grub-mkfile?

same thing…“update-grup: command not found”

Oh, my bad, made a typo, sincerely sorry
That should work… update-grub && mkinitcpio -P

I get a mixed output:

[manjaro /]# update-grub && mkinitcpio -P
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: ‘default’
-> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64.img
==> Starting build: 5.4.67-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
==> ERROR: module not found: usbhid' -> Running build hook: [keymap] -> Running build hook: [filesystems] ==> WARNING: No modules were added to the image. This is probably not what you want. ==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64.img ==> WARNING: errors were encountered during the build. The image may not be complete. ==> Building image from preset: /etc/mkinitcpio.d/linux54.preset: 'fallback' -> -k /boot/vmlinuz-5.4-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.4-x86_64-fallback.img -S autodetect ==> Starting build: 5.4.67-1-MANJARO -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [keyboard] ==> ERROR: module not found: usbhid’
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> WARNING: No modules were added to the image. This is probably not what you want.
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.4-x86_64-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.

hm, Lets bypass this by installing a new kernel, say Linux 57

Proceed with pacman -S linux57 && mkinitcpio -P && pacman -R linux54 && mkinitcpio -P && pacman -S linux54 && mkinitcpio -P && pacman -R linux57 && mkinitcpio -P

That command will install the linux kernel 57, create a ram image of linux 57, remove linux 54, resets the images, then reinstall linux 54, create a proper ram image, remove linux 57, and only keep linux 54.

Some steps might seems unnecessary, but it is better to attack from every angles than sinking slowly! :smile:

2 Likes

Haha I like the thinking, but it returns with an “error: target not found: linux56” interestingly enough

Right, forgot 56 is linux56-rt (realtime) …

I edited my previous post…

it looks like it worked correctly, only the ‘usbhid’ module wasn’t found, but it looks like that isn’t a critical module by any means, especially on an 8 year old laptop interface…so should I restart normally now?

One last step to be certain, update-grub , then reboot! :partying_face:

it gave me this, is it a problem?

[manjaro /]# update-grub
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.7-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.7-x86_64.img
Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Oh, that is fine! :sweat_smile:

That’s GRUB trying to probe your live USB …

You may reboot successfully, now!

It worked! Thank you very much!

1 Like

Sweet!! :partying_face:

Glad it worked !! Thank you for your patience!!

2 Likes

Sure, this is a Manjaro support forum after all. ISOs aren’t that hard to get (Manjaro - Downloads) and perhaps there is even a bootable usb left over from initial installation.

1 Like

You’re a genius! I had a similar issue and it worked perfectly. You saved my life bro

1 Like

Hello @The_Quantum_Alpha. I am experiencing the failure to load kernel modules error on boot as well. I also found this post but as I am not an expert with linux, I am struggling to interpret the suggested solution.

I tried your recommend solution, but on pacman -R linux54 it errors with:

checking dependencies…
:: removing linux54 breaks dependency ‘linux54’ required by linux54-nvida-340xx
:: removing linux54 breaks dependency ‘linux54’ required by linux54-virtualbox-host-modules

It was suggested to me to use mhwd-kernel -r linux54 instead. With that in mind, would the following be the correct command to resolve the load kernel modules error?

sudo pacman -S linux510 && mkinitcpio -P && mhwd-kernel -r linux54 && mkinitcpio -P && pacman -S linux54 && mkinitcpio -P && pacman -R linux510 && mkinitcpio -P

Thanks!

You can indeed give it a shot!

If not, let me know!

@The_Quantum_Alpha, I gave it a shot.

Error: You can’t remove your current kernel.