[SOLVED] Re-Installing the Kernel.. (damaged after upgrade)
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Re-Installing the Kernel.. (damaged after upgrade)
Hello dear fellows..
How you doing all?
I've my Slackware 13 box.
Recently, I have upgraded to -current, and while the upgrade I noticed that my connection went down while it was downloading the new kernel.
I had doubts that it got damaged.
Any way, later I did:
and found every thing is up to date.
While upgrading, the system asked me to run lilo, and I did..
But after rebooting, I got the (Kernel Panic) error.
I logged back in using setup disk, and the chroot to my original system root directory.
I removed the current Kernels, and now I need to re-install it.. there I'm stuck.
Slackpkg isn't working because the box is not connecting to the internet.
Any help, or links is more than appreciated since I'm not geek enough to sort it by my own.
Also few googling didn't set me up with a solution so far.
First, double check if you are effected by the libata switch over. The text of the kernel panic would be a nice clue. It states something like failed to find device ..... forget, haven't seen one in a while
Read the *** LIBATA SWITCHOVER *** section in Changes and hints. http://slackware.osuosl.org/slackwar..._AND_HINTS.TXT
To reinstall the kernels without network connection, download the packages to a usb disk, or burn to cdrom. Chroot as you did before, mount the external media, and use upgradepkg --install-new --reinstall package-name.txz
If you connect with ethernet to the network, before you chroot in, try to bring up your network. With current releases of Slackware, the installation boot sequence is handled by udev, so modules are already loaded. Check lsmod for your NIC's module. Obtain a dhcpc address with dhcpcd eth0
You can also boot into the installed system using the installation DVD.
In a pinch, you can boot your system from here with a command like:
boot: huge.s root=/dev/sda1 rdinit= ro
In the example above, /dev/sda1 is the / Linux partition.
The "old" ide subsystem in the the linux kernel is now deprecated in favor
of the newer libata subsystem, and this affects the naming of device nodes
for almost all types of disk drives -- hard drives in particular will now
have an "sd" named node. The following information should allow you to
handle that changeover gracefully.
1. Upgrade the kernel and kernel-modules packages normally.
2. Edit /etc/fstab to reflect the change from hd* to sd*.
Old Name --> New Name
3. Run lilo. Note that you have made no edits at all to it yet, unless
you needed to edit it for the new kernel. Specifically, do not make
any changes with respect to hd* --> sd*.
4. Reboot. At the lilo prompt, press <TAB> and add an append for the
real root device (which will no longer be /dev/hd*). For example, if
the old root device was /dev/hda1, and it will now be /dev/sda1, and
the name of your kernel image is "Linux" then you would do this:
5. Once the system comes back up, then fix /etc/lilo.conf, run lilo, and
reboot again to be sure everything is correct.
Humm... Alright.. I guess that mean something..
Let me do some tries.. and get back to you
It applies to all disks. The older kernels used IDE/PATA modules which listed drives as /dev/hd*. Newer kernels have switched over to using the libata modules. Libata calls all drives /dev/sd*. Does not matter if they are SATA or IDE.
libata has modules for both SATA interfaces and IDE/PATA interfaces.
Last edited by disturbed1; 06-01-2010 at 04:41 AM.
GREAT, I finally managed to log back directly to my box..
But, I figured out, that I have many packages that was badly damaged due to connection errors while downloading these packages.
Honestly, when I started the upgrade process.. my connection wasn't doing well, and so I guess several packages was damaged.
I had to re-download and install few packages other than the kernel before I was able to log to the system.
Ok, my question now..
Can I some way, reinstall ALL packages via (slackpkg) or something like that?
Just to make sure.. every thing is replaced again with a fresh and clean copy?