kernel install versus kernel update
by deretsigernu from LinuxQuestions.org on (#4RRDP)
I am using -current x86_64. When I check slackpkg, it says this:
Quote:
... but at start up, the dmesg includes a statement that 4.19.58 is running. I confirm with this:
Quote:
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
Code:upgradepkg kernel-*-4.19.75-x86_64-1for each relevant package? Then I need to run
Code:grub-mkconfig -o /boot/grub/grub.cfgagain 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 Code:less /boot/grub/grub.cfg, 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.
Quote:
| bash-5.0# slackpkg search kernel NOTICE: pkglist is older than 24h; you are encouraged to re-run 'slackpkg update' Looking for kernel in package list. Please wait... DONE The list below shows all packages with name matching "kernel". [ Status ] [ Repository ] [ Package ] installed slackware64 kernel-firmware-20190926_c0590d8-noarch-1 installed slackware64 kernel-generic-4.19.75-x86_64-1 installed slackware64 kernel-headers-4.19.75-x86-1 installed slackware64 kernel-huge-4.19.75-x86_64-1 installed slackware64 kernel-modules-4.19.75-x86_64-1 installed slackware64 kernel-source-4.19.75-noarch-1 |
Quote:
| bash-5.0# uname -a Linux computer 4.19.58 #1 SMP Wed Jul 10 14:01:16 CDT 2019 x86_64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz GenuineIntel GNU/Linux |
Anyway, I guess I need to use
Code:upgradepkg kernel-*-4.19.75-x86_64-1for each relevant package? Then I need to run
Code:grub-mkconfig -o /boot/grub/grub.cfgagain 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 Code:less /boot/grub/grub.cfg, 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.