[SOLVED] GRUB not booting 5.19.9 initially

NakedRider · 09-15-2022, 05:08 PM

I just did a slackpkg upgrade-all. With it came the new kernel.

I also ran grub-mkconfig -o /boot/grub/grub.cnf

Now when I boot and pick the first selection from the GRUB menu it tells me I need to load the kernel first.

I can go the the second menu and can't pick the first two options. The third one will load the 5.19.9 kernel.

Any idea why this is happening?

Thanks.

Daedra · 09-15-2022, 05:10 PM

just an initial thought. but did you make a new initrd when you upgraded the kernel?

NakedRider · 09-15-2022, 05:15 PM

Quote:

Originally Posted by Daedra

just an initial thought. but did you make a new initrd when you upgraded the kernel?

No. Shouldn't need to. I've just run the command grub-mkconfig -o /boot/grub/grub.cnf in the past and it has always worked.

colorpurple21859 · 09-15-2022, 05:44 PM

Quote:

grub-mkconfig -o /boot/grub/grub.cnf

unless this is a miss-type should be

Code:

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

NakedRider · 09-15-2022, 06:05 PM

Quote:

Originally Posted by colorpurple21859

unless this is a miss-type should be

Code:

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

Bingo! I usually look at my notes. I THOUGHT I had this memorized. Looks like I'll go back to looking at my notes.

Thank you so much for your help.

Regnad Kcin · 09-16-2022, 07:05 PM

refind makes it sooo easy if you have efi boot. unzip and run the install script. if you forget mkinitrd garp, or mysteries of grub2, refind has your six. we <3 refind.

ZhaoLin1457 · 09-16-2022, 07:17 PM

Quote:

Originally Posted by NakedRider

Bingo! I usually look at my notes. I THOUGHT I had this memorized. Looks like I'll go back to looking at my notes.

Thank you so much for your help.

I do not remember where I have found this little script named "update-grub" but I find it really useful.

Code:

#!/bin/sh
set -e
exec grub-mkconfig -o /boot/grub/grub.cfg "$@"

It's less error prone to type "update-grub" , right?

NakedRider · 09-21-2022, 09:46 AM

Quote:

Originally Posted by ZhaoLin1457

It's less error prone to type "update-grub" , right?

Yes, indeed. I wrote a script yesterday, updated the kernel and tried it out. All's well.
Thanks for the suggestion.

colorpurple21859 · 09-21-2022, 12:31 PM

Quote:

I do not remember where I have found this little script named "update-grub" but I find it really useful.

It is used in debian based distros.

elcore · 09-22-2022, 08:24 AM

Quote:

Originally Posted by NakedRider

No. Shouldn't need to.

Am I the only one assuming that initrd image should contain modules from the currenly running kernel and not modules from several versions behind?

kjhambrick · 09-22-2022, 01:05 PM

Quote:

Originally Posted by Daedra

just an initial thought. but did you make a new initrd when you upgraded the kernel?

Quote:

Originally Posted by elcore

Am I the only one assuming that initrd image should contain modules from the currenly running kernel and not modules from several versions behind?

Hmmm ...

I would think so too ... kernel-modules should probably come from the same kernel source as the running kernel bzimage.

-- kjh( I guess one might get away with old modules with a new kernel but why screw around when it's so simple to do it the right way ? )