I’ve partitioned my disk, e.g. I decreased the size of my home and installed another distro onto the free space. Everything went fine but after this, I cannot boot into my “normal” kernel (I get only the logo of the laptop company, no tty, no nothing) but I can boot into the fallback kernel (that’s what I’m on now currently). Both are the same latest LTS kernel.
My question: Is there a way to fix the normal one? Like reinstalling it or using some GRUB magic? Otherwise I always have choose the fallback one while booting and I wish to spare me this extra step.
Let’s say the latest LTS kernel is called linuxXYZ, this is the one I used before the partitioning. Does mhwd-kernel -i linuxXYZ REINSTALL the latest LTS if I execute this on the fallback kernel of linuxXYZ?
The difference between fallback image and normal image is the modules included in the image.
As I remember it the fallback image uses udev for the modules whereas the normal image may include predefined modules.
So if the fallback image works then a module included in the normal image is dysfunctional.
There is no one-size-fits-all answer but if you rebuild the images as suggested by @freggel.doeand rebuild your grub config your issue should go away.
But as you have added another Linux to the equation - not mentioned in the OT - it is next to impossible to deduct what may have caused this. E.g. what other changes have you not mentioned?
I am afraid this is going to be a circular issue - a socalled xy problem.
That didn’t help either. Or do I have to execute sudo mkinitcpio -P and sudo grub-mkconfig -o /boot/grub/grub.cfg during the same boot? Now I executed the first one in 1 boot and the second in the next one.
Hmm, this makes me think, you don’t use Manjaros grub at all, but the grub of the other linux installation you mentioned.
Make Manjaros grub the primary grub (reinstall/restore grub when booted into fallback) and only use that one to boot up your system.