GRUB freezes on "Loading initial ramdisks"

seth · 2026-11-06 08:49:22

lspci: Unable to load libk mod resources: error -2

That's only after a chroot? Running lspci from the install iso still works?

Can you

LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup | tee /tmp/integrity.txt

after the chroot? And post /tmp/integrity.txt ?
Booting the fallback image fails as well?

ValidName · Yesterday 04:02:52

Seth, thank You for not forgetting about me! So, lspci always returns the same thing (no matter chroot'ness). Then I executed Your command in chroot, the result in /tmp/integrity is:

amd-ucode: 17 total files, 1 altered file
filesystem: 127 total files, 1 altered file
systemd: 1995 total files, 1 altered file

I already think, that this is wrong... Shouldn't GREP search for lines that contain both "0 altered files" and "backup"? But the command is right...

seth · Yesterday 08:48:05

Then I executed Your command in chroot

That looks almost too innocent - but the lspci output is somewhat concerning if you also get that from the install iso.
From the install iso, no chroot:

uname -a
pacman -Qs kernel
lspci -knn

"man grep" / -v does what?:P

ValidName · Yesterday 09:18:20

Seth, OK, I was dumb here. So, the result for uname is on:
https://termbin.com/xfkv/
pacman is:
https://termbin.com/v0td/
And lspci:
https://termbin.com/18kg/

seth · Yesterday 15:41:07

That all looks rather sane, did lspci issue "Unable to load libkmod resources: error -2" again??

So status quo: system boots fine from the install iso, the installation starts the kernel but stalls somewhen after/with loading the initramfs.
There're no (error) messages, booting the multi-user.target / nomodeset and nosmp don't work either - that's all correct?

When I use archinstall, PC instead freezes on Arch's logo

Is that when running archinstall or when using archinstall to install the system?
Did you otherwise make any changes to the default mkinitcpio.conf and/or install/configure sth. like plymouth?
Have you tried to install/boot a UKI?

ValidName · Today 03:00:39

Seth, so, when I look through the output of lscpi, I don't see anything (but I look with less, so maybe it's something like in another stream)
Yes, there are no error messages when trying to boot GRUB, no matter the loglevel
When I some time ago was trying with about the same problems, I decided to instead of manual installation, redo everything with archinstall. It went smoothly, but when I tried to boot the OS, it froze on Arch logo
I don't think that I edited mkinitcpio.conf, all I was doing is sometimes running mkinitcpio with or without -P
After looking into what UKI is, I think I didn't do it. Maybe only mkinitcpio. So, is it the problem?

seth · Today 09:13:17

but I look with less, so maybe it's something like in another stream

lspci > /dev/null

The message would go to stderr

So, is it the problem?

No, but it sidesteps the problem of loading an initramfs - even if that works there's a chance that things will fail at a different stage (but hopefully w/ at least some error)

Have you tried installing a different distro? Does that boot?

ValidName · Today 14:22:59

Seth, so I have tried another district, but I strive to specifically Arch. So, here's how it is:
When I first started to try to install Arch, I thought that it would be a 2-3 days max. But, I got all these endless errors, and I still needed to somehow interact with the web. So, when near deadline hit, I got an idea. To install another distro. I picked Fedora. I booted it from ISO and I was greeted by real GUI! I tried installing it, but it kept failing, something like "couldn't make file system on /dev/sda2". But I decided that I didn't need that. I had graphics, browser, editor, and whole ~3 (GiB) of empty space!
And so, when I need to do something, I boot it quickly, install things I needed and was ready to go. Then when I needed Arch back, I would just shutdown and everything would get wiped (which is unfortunate). Maybe this is the root of all evil. I think I should have told You this earlier...

seth · Today 14:30:47

I would just shutdown and everything would get wiped (which is unfortunate)

You're running the fedora live system (that can also be used to install fedora but is more akin to knoppix, grml etc.)

"couldn't make file system on /dev/sda2"

lsblk -f

When installing arch, do you struggle to format the drive or create a filesystem?
Does fedora not offer you to completely format and repartition the drive?

Arch Linux

#26 2026-11-06 08:49:22

Re: GRUB freezes on "Loading initial ramdisks"

#27 Yesterday 04:02:52

Re: GRUB freezes on "Loading initial ramdisks"

#28 Yesterday 08:48:05

Re: GRUB freezes on "Loading initial ramdisks"

#29 Yesterday 09:18:20

Re: GRUB freezes on "Loading initial ramdisks"

#30 Yesterday 15:41:07

Re: GRUB freezes on "Loading initial ramdisks"

#31 Today 03:00:39

Re: GRUB freezes on "Loading initial ramdisks"

#32 Today 09:13:17

Re: GRUB freezes on "Loading initial ramdisks"

#33 Today 14:22:59

Re: GRUB freezes on "Loading initial ramdisks"

#34 Today 14:30:47

Re: GRUB freezes on "Loading initial ramdisks"

Board footer