kernel usage/configuration? (Slackware-current kernels on Slackware-stable)
by dchmelik from LinuxQuestions.org on (#6QSK5)
My main (64-bit Slackware-current) workstation PC is in need of repair, so I'm temporarily using a family's one (so far all Debian-based (Devuan, *ubuntu, Neon, Mint to be easier for users) currently on Devuan (ugh) so I'm not as aware of some Slackware-current updates due to always using Slackware-stable on servers unless it becomes too old for whatever server software (like in the over five year gap between Slackware 14.2 and 15)... so I don't entirely understand what's going on with kernels...
I see huge has been removed for generic, so do I still need mkinitrd, and might I find need to compile more various/obscure drivers? However, that's not so important (just for after my main PC is repaired) as my question about (suggested) usage of Slackware-current Linux kernels on Slackware-stable (still don't know this is really recommended, but some forum posters said do this for a display/video/graphics driver for recent years central processing unit (CPU) which now works). After installing the last several kernels 6.1.n to 6.10.n to 6.10.10 (and 6.11.0 testing) it seems grub-update now makes the menu in the wrong order. Of course I still have kernel 5.15.19 (removed from /var/log/packages as in a suggestion) in case of emergency (accidenal removal of kernels from /var/log/packages or bugs/corruption). However, grub-update puts kernel 5 at top (and as default option) and only puts kernels 6 (current main and testing) in 'advanced options' so I no longer can automatically (re)boot without attendance to get driver I need: I have to be at the monitor and select advanced options and scroll down to one of the kernel 6s.
Is there some grub(-update/etc.) option or argument/flag/switch I can enter so the menu gets made in the correct/historical/traditional order of newest first (even testing) or maybe this only works on actual Slackware-current with its grub (I can't install that on Slackware-stable due to load of dependencies that would just require a total upgrade to Slackware-current basically).
I see huge has been removed for generic, so do I still need mkinitrd, and might I find need to compile more various/obscure drivers? However, that's not so important (just for after my main PC is repaired) as my question about (suggested) usage of Slackware-current Linux kernels on Slackware-stable (still don't know this is really recommended, but some forum posters said do this for a display/video/graphics driver for recent years central processing unit (CPU) which now works). After installing the last several kernels 6.1.n to 6.10.n to 6.10.10 (and 6.11.0 testing) it seems grub-update now makes the menu in the wrong order. Of course I still have kernel 5.15.19 (removed from /var/log/packages as in a suggestion) in case of emergency (accidenal removal of kernels from /var/log/packages or bugs/corruption). However, grub-update puts kernel 5 at top (and as default option) and only puts kernels 6 (current main and testing) in 'advanced options' so I no longer can automatically (re)boot without attendance to get driver I need: I have to be at the monitor and select advanced options and scroll down to one of the kernel 6s.
Is there some grub(-update/etc.) option or argument/flag/switch I can enter so the menu gets made in the correct/historical/traditional order of newest first (even testing) or maybe this only works on actual Slackware-current with its grub (I can't install that on Slackware-stable due to load of dependencies that would just require a total upgrade to Slackware-current basically).