[Solved] Failed to start Load Kernel Modules

PeaNugE · 2023-03-20 01:33:42

Sorry if I posted this in the incorrect section.

Hello Everyone,

I have run into an issue with my arch box. I am hoping I can save/fix it and maybe learn a thing or two in the process.

Two nights ago I decided to run the pacman -Syu update command and restart the computer. I don’t turn my computer off very often so I randomly do this.

When I turned it back on I got this. [Failed] Failed to start Load Kernel Modules. This screen appears and disappears quickly so I took a picture with my phone. Once this screen is gone all I get is a blank screen with a white blinking line I cannot do anything with. I googled for a fix but nothing seems to match what's going on.
Some info about my install. I have my disk is encrypted and I am using a nvme drive split into 3 partitions running efi system on the first two partitions and lvm on the third. I followed the learn linux tv arch install video to get everything setup and its worked fine until this issue.

On my Grub boot options I have arch on the edge and arch long term support installed. They both have fallback iniramfs in addition. I mention this because I tried all 4 of these options and they all lead to a blank screen.

I just made a usb with the latest ISO for prep to fix the issue. I was hopping it had a fix/diag option. So thats ready to go.

Any help would really be appreciated.

https://i.ibb.co/BcwW9Zj/IMG-20230319-202924.jpg
https://i.ibb.co/GRLDFhX/IMG-20230319-202806.jpg

Mod note: Replaced oversized screenshots with links -- V1del

Last edited by PeaNugE (2023-03-21 21:14:24)

seth · 2023-03-20 09:26:16

Remove the oversized screenshots.
You most likely forgot to mount the /boot partition before the update and end up booting an older kernel.

blank screen with a white blinking line

Try to boot only the multi-user.target, 2nd link below.

PeaNugE · 2023-03-20 16:23:10

seth wrote:

Remove the oversized screenshots.
You most likely forgot to mount the /boot partition before the update and end up booting an older kernel.
blank screen with a white blinking line
Try to boot only the multi-user.target, 2nd link below.

First, Sorry about the images and I appreciate the response.

I checked out the page but am I supposed to boot from the USB and then run systemctl set-default multi-user.target.
That would only change the symlink for the usb stick instance I have running correct?

seth · 2023-03-20 16:34:39

supposed to boot from the USB

The wiki wrote:

Alternatively, append one of the following kernel parameters to your boot loader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3)

PeaNugE · 2023-03-20 20:37:38

seth wrote:

supposed to boot from the USB
The wiki wrote:
Alternatively, append one of the following kernel parameters to your boot loader:
systemd.unit=multi-user.target (which roughly corresponds to the old runlevel 3)

It took me a few hours to figure this out but I finally figured out the commands to unlock my 3rd partition so I could mount all the lvm partitions.
Once I got everything mounted, I was able to arch-chroot and run the systemsctl multi-user.target command and once I reboot the system it did not error and I was able to log in. Terminal only which I assume is what the lvl 3 is you referred to before.

I don't seem to have internet access to run the update commands. I enabled the Network Manager but nothing yet.

Now that I can boot into the system how do I go about figuring out what went wrong to start fixing things.

Last edited by PeaNugE (2023-03-20 20:38:05)

seth · 2023-03-20 20:52:59

Compare "uname -a" and "pacman -Qs linux"

I was able to arch-chroot and run the systemsctl multi-user.target command

Great, but just for the record and as mentioned: this would not have been necessary.

PeaNugE · 2023-03-20 21:31:03

seth wrote:

Compare "uname -a" and "pacman -Qs linux"
I was able to arch-chroot and run the systemsctl multi-user.target command
Great, but just for the record and as mentioned: this would not have been necessary.

uname - a
Linux 6.1.19-1-lts

pacman -Qs Linus - gives alot of info
local/linux 6.2.7.arch1-1
linux -lts 6.1.20-1

linux headers 6.2.7.arch1-1
linux lts headers 6.1.20-1

seth · 2023-03-20 21:44:01

seth wrote:

You most likely forgot to mount the /boot partition before the update and end up booting an older kernel.

Mount the boot partition and re-install linux-lts

PeaNugE · 2023-03-21 00:10:37

seth wrote:

seth wrote:
You most likely forgot to mount the /boot partition before the update and end up booting an older kernel.
Mount the boot partition and re-install linux-lts

nvme0n1p2 /mnt/boot is already mounted from the overkill i did before.
so I ran sudo pacman -S linux-lts and everything seem to go smooth.
Do I need to do anything the get out of lvl 3 before I reboot?

After I posted this above I ran systemctl set-default graphical.target

uname -a now says 6.2.1-arch1-1

I went ahead and rebooted the system and it still said Failed to Start Kernel Modules.

I clearly did smothing incorrect.

did I not mount the boot partition correctly?

Last edited by PeaNugE (2023-03-21 00:48:27)

seth · 2023-03-21 07:58:36

Does the graphical.target boot (w/ the correct kernel) and you only get the service failure?
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

-------------------
Edit: disregard the below for the moment
From the mulit-user.target boot, what's the output of

cat /proc/cmdline

(You can hit the reverse scenario where you've a mouted boot partition but are actually booting from the root partition)

Also your screenshot shows TWO 500M partitions (nvme0n1p1 & nvme0n1p2) - sure you're mounting the correct™ one?

Last edited by seth (2023-03-21 08:00:10)

PeaNugE · 2023-03-21 11:27:01

seth wrote:

Does the graphical.target boot (w/ the correct kernel) and you only get the service failure?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
-------------------
Edit: disregard the below for the moment
From the mulit-user.target boot, what's the output of
cat /proc/cmdline
(You can hit the reverse scenario where you've a mouted boot partition but are actually booting from the root partition)
Also your screenshot shows TWO 500M partitions (nvme0n1p1 & nvme0n1p2) - sure you're mounting the correct™ one?

0n1p1 - EFI Partition
0n1p2 - Boot Partition
0n1p3 - lvm Encrypted Partition

When I get the usb to boot the system. I then unlock the 3rd partition and mount everything. run the systemctl multi user and reboot. then switch the bios to boot from the HD and then it boots into cmd just fine.
I log in and cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-lts root=/dev/mapper/volgroup0-lv_root rw cryptdevice=dev/nvme0n1p3:volgroup0:allow-discards log level=3 quite

Last edited by PeaNugE (2023-03-21 11:27:17)

seth · 2023-03-21 13:38:11

seth wrote:

Edit: disregard the below for the moment

So the relevant part was:

seth wrote:

Does the graphical.target boot (w/ the correct kernel) and you only get the service failure?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

PeaNugE · 2023-03-21 14:33:13

seth wrote:

seth wrote:
Edit: disregard the below for the moment
So the relevant part was:
seth wrote:
Does the graphical.target boot (w/ the correct kernel) and you only get the service failure?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

https://0x0.st/H-n-.txt

seth · 2023-03-21 14:48:37

You're using the service to load the nvidia module which fails along

Mar 21 06:51:46 miniarchbox kernel: traps: Missing ENDBR: _nv012309rm+0x0/0x10 [nvidia]

https://wiki.archlinux.org/title/NVIDIA#Installation - see the blue note about "ibt=off"

PeaNugE · 2023-03-21 20:37:35

seth wrote:

You're using the service to load the nvidia module which fails along
Mar 21 06:51:46 miniarchbox kernel: traps: Missing ENDBR: _nv012309rm+0x0/0x10 [nvidia]
https://wiki.archlinux.org/title/NVIDIA#Installation - see the blue note about "ibt=off"

Every Linux distro I have ever used has broken because of the video card drivers. This is the first time I have been able to get enough help to fix it. Thank you Seth.

I read through everything on the blue note and like much of the stuff on the arch wiki I can read and read and read and I usually end up with more questions that when I started.

I found this on redit.
sudo nano /etc/default/grub

Then find the line that looks like:

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet"

Add ibt=off just like before,

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet ibt=off"

CTRL+X to save

Then regenerate grub to use the edit you just made to make it permanent:

sudo grub-mkconfig -o /boot/grub/grub.cfg

This worked for me and I have a gui again.

Last edited by PeaNugE (2023-03-21 20:40:55)

seth · 2023-03-21 20:56:03

I found this on redit.

https://wiki.archlinux.org/title/Kernel_parameters#GRUB
https://wiki.archlinux.org/title/GRUB#Configuration

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2023-03-20 01:33:42

[Solved] Failed to start Load Kernel Modules

#2 2023-03-20 09:26:16

Re: [Solved] Failed to start Load Kernel Modules

#3 2023-03-20 16:23:10

Re: [Solved] Failed to start Load Kernel Modules

#4 2023-03-20 16:34:39

Re: [Solved] Failed to start Load Kernel Modules

#5 2023-03-20 20:37:38

Re: [Solved] Failed to start Load Kernel Modules

#6 2023-03-20 20:52:59

Re: [Solved] Failed to start Load Kernel Modules

#7 2023-03-20 21:31:03

Re: [Solved] Failed to start Load Kernel Modules

#8 2023-03-20 21:44:01

Re: [Solved] Failed to start Load Kernel Modules

#9 2023-03-21 00:10:37

Re: [Solved] Failed to start Load Kernel Modules

#10 2023-03-21 07:58:36

Re: [Solved] Failed to start Load Kernel Modules

#11 2023-03-21 11:27:01

Re: [Solved] Failed to start Load Kernel Modules

#12 2023-03-21 13:38:11

Re: [Solved] Failed to start Load Kernel Modules

#13 2023-03-21 14:33:13

Re: [Solved] Failed to start Load Kernel Modules

#14 2023-03-21 14:48:37

Re: [Solved] Failed to start Load Kernel Modules

#15 2023-03-21 20:37:35

Re: [Solved] Failed to start Load Kernel Modules

#16 2023-03-21 20:56:03

Re: [Solved] Failed to start Load Kernel Modules

Board footer