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.
By halo14 at 2005-05-31 08:07
I just installed Slackware-current and the 220.127.116.11 kernel from Disc #2 from the latest (5-18-05) Slackware-current set. It was MUCH easier than I had expected it to be, so I thought I would share for other Slackware users who may want a 2.6 kernel without the hassle of compiling a new one.
I used the one from the CD because it's a good general base, and for whatever reason, I just couldn't get a decent kernel compiled on Slack. So here's how I did it, basically, it's nothing more than what it tells you to do in the README.initrd file.
The latest Slackware discs all include an optional 2.6 kernel so this should work the same on the 10.1 discs as well. I just like to use Slackware-current because it's still very stable. More so than 'stable' versions of distro's like Fedora, Mandrake, etc.. in my experience.
Step 1 - Installation
Install Slackware. I generally don't try to install a trimmed down version from the start. Rather, I install everything except KDE and GNOME(which isn't even available on the new discs).
Step 2 - Mount Disc #2 and cd to 2.6 kernel directory
After the installation is complete, login as root and mount the Slackware installation disc #2.
Step 3 - Install 2.6 kernel files Here is where you'll find the 'README.initrd' file which explains how to install the 2.6 kernel if you are using anything other than ext2 filesystem.
You can 'ls' to see the available files, but you want to be sure you have the kernel, kernel modules, and makeinitrd(included in the installation if you choose everything) installed.
Now, I used pkgtool to make sure I had 'mkinitrd' installed, you may want to do the same. If it's not installed, install it at this time.
Step 4 - Make initrd for necessary modules
Okay, the point of initrd is an initial ramdisk file system with which to load modules the kernel will need in order to boot. This includes things like filesystem modules, disc controller modules, etc. Since I'm running an IDE system with reiserfs, the only thing I need initrd to load is the reiserfs modules.
mkinitrd -c -k 18.104.22.168 -m reiserfs
This will do two things. It will create the /boot/initrd-tree containing the initrd filesystem. It will also create the actual initrd(initrd.gz). Another example, if you are using ext3 filesystems: