I am using -current x86_64. When I check slackpkg, it says this:

... but at start up, the dmesg includes a statement that 4.19.58 is running. I confirm with this:

So, while 4.19.75 is installed, it seems I'm actually running 4.19.58? I'm trying to figure out how I get to running ~.75 and I searched the forum. I found this. I also came across something in SlackDocs or the slackpkg manual that said I should blacklist any kernel packages, so I did.

Anyway, I guess I need to use

for each relevant package? Then I need to run

again to make sure I get the new kernel as an option to boot? Or will that just make the new kernel the only option to boot? I'm still not clear on how to customize GRUB2 exactly. I currently have Slackware 14.2+, Advanced Slackware boot options, and Windows bootloader as menu options when the computer boots and I don't know how I add another menu item to have multiple kernels to boot from, in case the new kernel doesn't like something on my computer.

When I , there is a section in there for 4.4.14 and that's not an option in the GRUB2 menu at boot. I bring that up, because the presence of the old kernel in grub.cfg and not on the GRUB2 boot menu makes me think that the boot menu only allows one kernel visible at a time. I don't want the old kernel, just using that to make my point about what shows in the boot menu.

It just occurs to me: maybe I just need to run grub-mkconfig... now, without bothering with the upgradepkg? Then GRUB2 will recognize and boot from the new kernel? I'm still not sure how I can have multiple kernels in the boot menu, if there is a problem with the new kernel for some reason.

There's a good practice to not upgrade straight forward a working kernel and install along the new one. Until next upgrade.

Your grub thing might have a few origins :
What is the name of the section might not be the name of the kernel.
The way grub is told to boot can be : this or that number of the list or last booted one

Anyway, the grub-mkconfig command should list all available kernels.

IIRC, you'll have to take a look at /etc/default/grub to see how /boot/grub/grub.cfg will be built.

1 members found this post helpful.

I agree with @Tonus. This is boot loader issue. Show us
and
kernel modules must be the same as running kernel. You can have multiple different kernels. Myself I am using lilo. I can't help with proper grub setup.

1 members found this post helpful.

@Tonus
The suggestion to run grub-mkconfig might work? I don't know if it will commit me to making a choice between kernels? I don't know the script well. I'll look at the man/help.


@igadoter

Since you state it's a boot loader issue, it seems my second hunch in prior post might have been right: I have to jump to running

and not deal with the "updatepkg kernel.*" step to get the new kernel in place. I understand the caution that you and Tonus are giving and I agree. It's not a good idea to just run a new kernel without knowing how the system will react to it. I don't want to do that exactly. I want the GRUB2 boot menu to list both kernels, the one I'm currently using that I know works (~.58) and the new one (~.75). This way I can reboot, select the new kernel, make sure everything works with it and then use that. And if ~.75 doesn't work, I can force a shut-down and restart and go back to ~.58 and wait for a newer kernel and/or solve the problem in ~.75.

Unrelated: I see your location as Wroclaw. An old friend of mine lives there. I visited a few years back and really enjoyed Poland. I think that "thank you" is proscze? ... Maybe that's "please" ... dzen kuyue?

grub2 can show both kernels, if they are both present.

https://github.com/Richard-Cranium/SlackwareGrub2 may help with that, but it isn't required. All it does is match up a versioned initrd with a versioned generic kernel.

I've been using slackroll instead of slackpkg to track -current. slackroll has specific commands for upgrading the kernel (kernel-upgrade, which just installs the new kernel, and kernel-clean, which uninstalls the old kernel). You'd run kernel-upgrade, create a new initrd followed by whatever you need to do to update your bootloader, and then reboot. If the new kernel works, run kernel-clean.

2 members found this post helpful.

Without the output option, result is to stdout.
If you redirect to a dummy file, it still will show the kernel available.

Have a look to grub-reboot and grub-set-default.

I ran .

Now at boot, the GRUB2 menu looks the same, but the default option is for the new kernel, 4.19.75. If I select "Advanced Options", the 2nd menu item, I get a list of all the possible kernels there. I was hoping that I could have that list on the main menu. I need to learn more about customizing the GRUB2 boot menu.

1 members found this post helpful.

I don't know much about grub2. But I can see a few possibilities here. First I'm assuming you rebooted after updating your kernel? Perhaps it is trite to say but a reboot is required after a kernel update for it to take effect.

Secondly, I'm going to assume you're using GPT (UEFI) as opposed to legacy MBR booting.

I'm using elilo with GPT as I have for a few years now, and in my experience the kernel image ("vmlinuz") is copied as opposed to linked to /boot/efi/EFI/Slackware (or what have you). So it could be that an old version of the kernel is still lying around in /boot/efi and that is what is actually being booted. I would try running md5sum on the kerbel image sitting in /boot/efi against the vmlinuz file you're expecting to boot from /boot and see if they match.

You can edit /etc/default/grub to set your default from that list. This page has a basic explanation of the options: https://www.gnu.org/software/grub/ma...iguration.html Check out the 'GRUB_DEFAULT' section.