SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It looks like you're invoking mkinitrd 2 times with different instructions; I'm not sure that will work.
The kernel is referenced in the mkinitrd, and I pass the kernel I want as an argument with -l (so mkinitrd_command_generator.sh -l /boot/vmlinuz-generic).
Also editing the grub.cfg file is not ideal because it is overwritten by grub-mkconfig.
One thing: when I chroot sometimes I'm given a prompt that includes the whole path of the working directory and sometimes it does not include the path. Isn't that weird?
I chroot'ed and ls /lib/modules gave:
Code:
4.4.14 4.4.14-smp 5.4.49-smp
(I installed 5.4.49, not 5.4.50) Should I put -k 5.4.49 or -k 5.4.49-smp?
Not sure, at the moment, do you use the smp on plain kernel? Use one if it doesn’t work use the other one. Which ever one you use, use it with the generic kernel
Last edited by colorpurple21859; 10-31-2020 at 10:53 AM.
Regarding my -current installation, which I am using right now, I have found it uses the huge kernel! So it was the huge we finally used for -current, not the generic.
Richard, thanks for a handy little program. I used it to move from LILO to GRUB with no issues. BUT I do have two questions:
1) After following the read.me instructions, should I remove 09_slackware_linux from /etc/grub.d? And then re-run grub-mkconfig once rebooted?
2) I also notice that my Grub menu didn't have the two kernels available in /boot, vmlinuz-generic-4.4.240 and vmlinuz-custom-5.4.75ba. Is it a naming issue? It seems that both are in the grub.cfg under /etc/grub/10_linux, but under a heading for "Advanced options for Slackware-14.2 GNU/Linux" as submenu entries. I'd rather have the latest kernel appear and actually by a default load after 5 seconds of no answer. Is that possible?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.