[SOLVED] Can't boot into -current partition after slackpkg upgrade-all, after kernel upgraded
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Can't boot into -current partition after slackpkg upgrade-all, after kernel upgraded
I can't boot into my -current partition after slackpkg upgrade-all.
I am having 2 hard disc, first is purely for windows 7 where it come with the original purchase. i add another hard disc to install OperatingSystem for the use of Slackware stable and -current.
i boot in -current or stable by a usb pendrive as i yet to know how to chainload the OS with windows 7 in HD1, and i don't want to disturb the MBR in windows partition. That's why i add another HD but i can't load slackware directly thru HD2, must use a usb bootup pendrive.
My problem now is i can't boot into my -current partition after slackpkg upgrade-all, i can't even use the previous -current installer CD nor the bootup pendrive. i know it is due to the new kernel upgrade but how to rescure myself now?
first, you will have to boot using the installer again (it can be pendrive or CD)
mount your root partition and chroot to the partition
next, reinstall your kernel and this time, make sure you create an initrd. It has a great documentation which is placed on /boot directory. You should read it first.
don't forget to add the initrd line in your /etc/lilo.conf and execute /sbin/lilo to re-read the configuration file
I think that the issue is that you was using an huge kernel and now you switched to generic on the update.
I would solve this way (and stick with the huge kernel)
Boot slackware cdrom
mount /dev/<root> /mnt
change the System.map config and vmlinuz links from generic to huge
I'm not clear if ever slackware booted after you added an additional hard drive. If not, then adding of an additional hard drive may have moved the slackware hard drive from number 2 to number 3 hard drive. Try switching the cables on the new hard drive with the cables on the slackware hard drive, If it doesn't work then put them back the way the cables were to prevent futher problems.
I'm not clear if ever slackware booted after you added an additional hard drive.
No, it doesn't boot. Since i don't want to disturb the MBR in win7 hard drive, i boot into slackware in the second hard drive with pendrive.
As for now i have mess up with the kernel after updated to the new version i can't boot in with the old kernel in the previous pendrive.
Anyway, now i managed to boot-in thru the latest iso installer CD downloaded from mirror site.