[SOLVED] Wrong kernel after upgrade-all - doesn't boot.
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 haven't used my slackware-laptop (StinkBad T42) for a while, and I thought it'd be a gfood idea to bring it up to date, so I gave 'slackpkg update' and then 'slackpkg upgrade-all'.
It asked me to run Lilo, and I let it. Then an error occurred, and the machine doesn't boot anymore. The boot complains about non-pae processor and tells me to use an appropriate kernel.
I have used a non-pae kernel, and the upgrade installed a pae-kernel.
The processor does support PAE, but doesn't have the flag.
Did you edit the /etc/lilo.conf before you ran lilo? Also do you use the huge or generic kernel? if you use the generic kernel you need to update your initrd.gz.
I wonder if it's enough to "re-link" vmlinuz to vmlinuz-huge-3.10.103 and run 'lilo'?
And if so, should I 'chroot' to the '/' of the slackware first?
(I'm now booting Puppy from a USB stick.)
It seemed to be enough to first boot from another device (I booted Puppy from a USB-stick), then
'rm vmlinuz' then 'ln -s vmlinuz-huge-3.10.103' then 'chroot /dev/sda1' and then 'liloconfig' with all defaults.
My Slackware is up and running again!
I wonder If I should update config and System.map as well? And maybe something else?
[edit]
Well, screen saver hangs...
Last edited by turboscrew; 09-13-2016 at 08:46 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.