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.
Hi all, i got a problem when i upgrade my slackware kernel. i've compiled the kernel (3.11), and i dont update the lilo(when i update the lilo, the system miss the glibc). then i rebooted it. so i got this error when startup.
When you don't update Lilo your new kernel will not be booted, it will start the old one. So your problem can't be a problem with the new kernel, but rather with your system, which is also indicated by the error you get regarding the missing glibc.
Is this the recommended full install?
When you have not removed your old kernel than lilo will boot that kernel if you don't upgrade lilo.
Regarding the glibc, do you by any chance have changed that also?
A common cause of boot failure with lilo is that at some time in the (perhaps distant) past someone moved some of the boot files but did not re-run the lilo installer. The system can continue to boot just fine for quite a while because lilo is actually loading data that continues to exist in what is now marked as free space on the disk. Eventually, something new gets stored in some of those disk blocks, and suddenly the old, reliable kernel that you didn't change fails to boot.
Recovery requires booting from rescue media and running the lilo installer.
When you have not removed your old kernel than lilo will boot that kernel if you don't upgrade lilo.
Regarding the glibc, do you by any chance have changed that also?
Quote:
Originally Posted by rknichols
A common cause of boot failure with lilo is that at some time in the (perhaps distant) past someone moved some of the boot files but did not re-run the lilo installer. The system can continue to boot just fine for quite a while because lilo is actually loading data that continues to exist in what is now marked as free space on the disk. Eventually, something new gets stored in some of those disk blocks, and suddenly the old, reliable kernel that you didn't change fails to boot.
Recovery requires booting from rescue media and running the lilo installer.
actually i have replaced my old kernel configuration and i forgot to backup them.
then, for my question, can i place/install a new kernel or old kernel in my slackware in this situation?
should i use chroot?
actually i have replaced my old kernel configuration and i forgot to backup them.
then, for my question, can i place/install a new kernel or old kernel in my slackware in this situation?
should i use chroot?
Just install (or copy) a new kernel into the system, generate a new initrd, if necessary, chrrot into the system, update /etc/lilo.conf and run lilo.
With the Slackware DVD it is easiest to do that, you don't even need to chroot, just follow the instructions on the bootloader's page of the DVD to boot the installed system, the just install/configure the system as you would do normally with your system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.