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.
I am using Slackware 14.2 64-bit with the KDE environment.
I installed yesterday's patches, including kernel 4.4.19, using the slackpkg method.
Now when I boot up Slackware using LILO all I get is a screen that says "Loading Slackware....................."
Yesterday's patch notes for the kernel state:
Quote:
Be sure to upgrade your initrd after upgrading the kernel packages. If you use lilo to boot your machine, be sure lilo.conf points to the correct kernel and initrd and run lilo as root to update the bootloader.
How do I upgrade initrd and lilo.conf if I am not even able to access Slackware past the LILO prompt?
Upgrade of initrd and lilo.conf must be done after upgrading the kernel and before you reboot the system.
Now, as said in previous post, you need to boot using the installation media or a rescue disk and chroot to your system to be able to perform the initrd and lilo.conf updates.
I don't understand how I need to modify lilo.conf or run initrd in order to get LILO to boot Slackware 64. The above-mentioned commands were working when I initially installed Slackware 64, so why don't they now? True, the install DVD came with kernel 4.4.14 and the day before yesterday pkgtool installed kernel 4.4.19 but I don't see any reference to the kernel version in LILO, so I don't understand why Slackware 64 stopped booting up.
I'm very inexperienced at this and might need some detailed instructions...
The links provided to you will give you all the detailed information you need. But here is a paint by numbers version that should get you up and running again. You mentioned you were able to boot the system using the install disc? Assuming you have no special install do this..
1) Boot form the install disc and log in as root
2) cd to the /boot directory
3) delete the vmlinuz symlink and create a new one pointing to the huge kernel like this "ln -s vmlinuz-huge-4.4.19 vmlinuz"
4) If you use the generic kernel with an initrd then you are going to have to make a new one because the old initrd is using modules from the old 4.4.14 kernel, that is mostly likely your problem, but we will get to that later. So go ahead and delete the old initrd (rm -r initrd.gz initrd-tree/)
5) now run "lilo -v", this should reinstall lilo with your new 4.4.19 huge kernel, you will not need to initrd since its the huge kernel.
6) reboot, if everything went well you should now be able to boot slackware with the 4.4.19 kernel. If successful. You can now go to /usr/share/mkinitrd and you use the script in there to create a new initrd to use with the generic 4.4.19 kernel.
The links provided to you will give you all the detailed information you need. But here is a paint by numbers version that should get you up and running again. You mentioned you were able to boot the system using the install disc? Assuming you have no special install do this..
1) Boot form the install disc and log in as root
2) cd to the /boot directory
3) delete the vmlinuz symlink and create a new one pointing to the huge kernel like this "ln -s vmlinuz-huge-4.4.19 vmlinuz"
4) If you use the generic kernel with an initrd then you are going to have to make a new one because the old initrd is using modules from the old 4.4.14 kernel, that is mostly likely your problem, but we will get to that later. So go ahead and delete the old initrd (rm -r initrd.gz initrd-tree/)
5) now run "lilo -v", this should reinstall lilo with your new 4.4.19 huge kernel, you will not need to initrd since its the huge kernel.
6) reboot, if everything went well you should now be able to boot slackware with the 4.4.19 kernel. If successful. You can now go to /usr/share/mkinitrd and you use the script in there to create a new initrd to use with the generic 4.4.19 kernel.
Thanks! I will try your suggestion tomorrow and see what happens. As for point 4), my /boot directory does not have file initrd.gz or directory initrd-tree/, so I guess the whole point 4) does not concern my situation.
@Daedra,
doinst.sh from the kernel package creates /boot/vmlinuz symlink to the kernel image from this package. So vmlinuz is linked to kernel from last installed kernel package.
Usually last installed kernel package is -huge- (by alphabet ;-) ) and vmlinuz is targeted to the huge kernel. So for default lilo.conf and huge kernel
and after 'slackpkg download kernel' and installpkg one additional step may be (note "-k new_version")
Code:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.19 | bash
# lilo
reboot and removepkg old kernel-{huge,generic,modules,headers} packages.
For 32-bit don't forget for -smp suffix in package's names and kernel's versions for default SMP kernels.
I was going to mention that to tb75252. I realized after I posted that the symlinks are created by doinst. So you're right, I would think that simply running lilo again should correct his problem. I have always made the symlinks myself just for piece of mind even though I know I don't really need too.
I was going to mention that to tb75252. I realized after I posted that the symlinks are created by doinst. So you're right, I would think that simply running lilo again should correct his problem. I have always made the symlinks myself just for piece of mind even though I know I don't really need too.
Yes, running "lilo" fixed the problem! Thanks everybody for the help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.