I'm trying to update my Slackware 10.2 Kernel from 2.4.31 to 2.6.13 using the pre-compiled kernel from the second Slackware installation cd. I followed every step in the README.initrd, and have done this a few times, and I keep getting the same error whenever I try to boot to the updated kernel from LILO. Goes something like this:




Now this is what I did to update to 2.6:

Then from the boot folder:

I then precided to update my lilo.conf:


Then I rebooted my system, selected the Linux_2.6 from LILO and got that error as it loaded. I've done this multiple times with multiple variations of this method, and got the same thing every time. Any idea how to fix this, or a better method of updated my kernel to 2.6? Any help would be appreciated, thank you.

I think this line should be something like;
initrd=/boot/initrd-generic-2.6.13.img
See if this helps;
http://www.tuxmachines.org/node/2652
You can cd to /boot then ls to see what is there ...

Why deal with initrd?

It's just another layer of complexity. Try to recompile your own kernel following Shilo's sticky: How I did it all.

Just remember to make sure you include your filesystem in the compile, and not as a module. The kernel needs this info long before the modules load.

The other advantage to compiling your own kernel is you only include what you/your hardware needs.

Hi There,

I run Slackware 10.1 - w.kernel 2.4.29 and recently upgraded to kernels 2.6.15 and ..14

I downloaded the kernal from: kernal.org

I then followed 2 artilces (mostly) on the web - the forum is not allowing me to post URLS untill i have made at least 5 posts.

If you are interested in the articles email me and i will give you the links. Both demonstrated compiling the new kernal without messing with the old one + adding two entries into LILO.conf file so as to retain the OLD settings and test the NEW kernel..

Worked a treat for me

//Graz
graz@veritel.com.au

I hope this helps..

Okay, I just tried compliling my own kernel 2.6.15 using the "How I did it all" sticky and it just gave me the same error. Maybe I'm not selecting the right options in the gconfig?

Sounds more like a fstab issue. Make sure it matches for your root partition.
Also make sure you note cwwilson721 comments re selecting all your filesystem types in the kernel.

use install cd check your partition table with cfdisk make sure your root is proper address. try booting to your root with test26.s kernel that or boot the installation cd then mount and chroot your install partition rerun lilo. had that same problem forget what all I had to juggle. was a pita. I had my /proc directory screwed up. had to reinstall a directory packages.

except for my newest computer I have been running 2.6 flawlessly for months. newest computer bleeding edge bound to be some probs. did a full install which installs a 2.4.x kernal and accessories went to delete the 2.4.x items got same problem you describe. had to shuffle some packages.

I've had some problems with 2.6 myself (from the SlackwareCD2/test).
I've tried to choose it as kernel when installing Slackware.
From there on, i've never succeeded to go into the GUI, and my wireless keyboard stopped working etc..
So i gave up on it.

I just tried compiling again with the 2.6.15 from the kernel website, and I went into the "make menuconfig" and I went through every option and read the help on it, selected everything that looked important, selected all my filesystem types in the kernel. It got a little farther booting, but still got a kernel panic.

Could you post the error, not the kernel panic but the part that happens right before. Also make sure your chipset is compiled in also.

Try recompile your 2.6.xx kernel with option something about RAMDISK except EXPERIMENTAL.
If you use Reiserfs, you should activate all of Reiserfs feature except EXPERIMENTAL as builtin kernel.

after that.. do it usually.

I hope it works.