Failed to start Load Kernel Modules

As it says in the title, my kernel isn’t loading in properly. Admittedly, the last time I shut it down was pretty sloppy; I removed it from it’s docking station and then force shut it down. Now it only says this one line and I cannot use the shell, or type anything at all. Am I screwed?

Image:
h ttps://cdn.discordapp.com/attachments/681552703801131038/762740625094737950/1005201418.jpg

Howdy!

I think it is time to chroot to fix that issue!

I would be more than happy to guide you through this!

You will need a Live USB to boot from it, then please provide me the output of lsblk

Thank you, have a wonderful day!:smile:

Sorry, but could you give me the process to live boot from a USB?

Oh, It is the same process as when you first installed manjaro!

[manjaro@manjaro ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 20.7M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 457.1M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1.6G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 606.2M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 465.8G 0 disk
└─sda1 8:1 0 465.8G 0 part
sdb 8:16 1 14.8G 0 disk
├─sdb1 8:17 1 2.7G 0 part /run/miso/bootmnt
└─sdb2 8:18 1 4M 0 part
sr0 11:0 1 1024M 0 rom

here it is

Thank you!

In the terminal, punch in sudo -i , then press enter and give your password.
Once inside root, punch in the whole following command: mkdir /1 && mount /dev/sda1 /1 && mount --bind /proc /1/proc && mount --bind /dev /1/dev && mount --bind /sys /1/sys && cp /etc/resolv.conf /1/etc && chroot /1

When it asks you if you want to overwrite /etc/resolv.conf , type in yes.

Once inside, try executing sudo pacman -Syyu && grup-mkconfig !

Let me know if it worked!

https://wiki.manjaro.org/index.php/GRUB/Restore_the_GRUB_Bootloader#Use_manjaro-chroot

$ manjaro-chroot -a

Just so you know, the boot from USB is it’s own new manjaro user, it isn’t mine. It prompts me to install manjaro like I did the first time on this laptop. Is there a way to access my hard drive, or should I just write that command as is?

Oh, Just write the command as is, it will access your drive for you!

Assuming the person has a Manjaro Live ISO…

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:

1 Like

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?