You are not logged in.
Hi, I've had arch installed in my computer for years and today I did a system update and rebooted and now I get a kernel panic!
This is the error I get:
https://cdn.discordapp.com/attachments/ … nknown.png
Please help!
Last edited by miarma (2022-02-02 12:20:10)
Offline
Please don't embed huge images directly.
Your initramfs is corrupted. Make sure there's enough free space on your /boot partition, use a live disk to chroot in and regenerate your images with mkinitcpio -P.
If this is insufficient, mount the partitions as you expect them to be, chroot in and post the outputs of
lsblk -f
df -hOffline
First of all, sorry for embedding the image!
It was indeed a disk space problem, I've solved it temporarily by using -9 in COMPRESSING_OPTIONS. Anyways, my initrd-image is almost 60M and I do not know why is that big. I'm not using dkms and I have nvidia-drivers installes and bcom-wl (just in case it has soimething to do with it)
A friend of mine who is also with nvidia drivers showed my his image and it's only 9M, why is the difference so big? This is my mkinitcpio.conf:
MODULES=(nvidia)
BINARIES=()
FILES=()
HOOKS=(base systemd udev autodetect modconf block filesystems keyboard fsck)
COMPRESSION="zstd"
COMPRESSION_OPTIONS="-9"Offline
Ok, I've solved everything.
The huge size of my initramfs was filling up my boot partition. Using the best compression for the image solved the issue temporarily but the main culprit of the problem was having "nvidia" module in my mkinitcpio.conf for early module loading. Removing it made my image way smaller (9M) and didn't affect anything else.
Offline
Having the nvidia module in the initramfs can be necessary/useful if you have loading races during bootup. So if you notice issues with that (e.g. your graphical session doesn't start from one boot to another) you might have to rethink this a bit, either increasing the /boot partition's size or using a boot loader that can read images from your root filesystem like GRUB or so and putting your /boot on that instead.
Offline
Thanks! I'll keep that in mind. I am just too scared to resize the efi partition (or resize any partition). I hope I don't have to get to that ![]()
Offline
Yeah as mentioned if you opt for GRUB you can have your /boot on your root and have GRUB read the big kernel images from there. No resizing of partitions necessary just a bit of config shuffling.
Offline