Problems updating Slackware 9.1 2.4.x kernel to 2.6.6
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Problems updating Slackware 9.1 2.4.x kernel to 2.6.6
I'm trying to update my Slackware kernel from 2.4.22 to 2.6.6. I have the full source code downloaded and this is what I have been told to do (but I haven't done anything yet):
cd /usr/src
rm linux
tar -zxvf linux-2.6.6
ln -s /usr/src/linux-2.6.6 /usr/src/linux
cd linux
make mrproper
cp /usr/src/linux-2.4.22/.config /usr/src/linux
make menuconfig
(I guess for previous kernels you were supposed to do a "make dep" and then "make clean" here, but with 2.6.x and on you don't have to. Please correct me if this info is wrong)
The next step is supposed to be "/sbin/mkinitrd /boot/initrd-2.6.6.img 2.6.6" but I've discovered that the mkinitrd utility doesn't even exsist for Slackware and you have to manually create the image file. Problem is, I have no idea how to do this and can't find that information anywhere.
Some of this doesn't seem right to me, but then again I don't know jack about Slackware (or Unix/Linux in general for that matter). Currently I have Windows XP and Slackware with the 2.4.22 kernel dual booting flawlessly on a Dell 5100, but the last time I tried to use these commands I ended up with a kernel panic. Can anyone help me out? Let me know if you need more info or if there are typo's somewhere in the commands.
In lilo , i change the original kernel from vmlinuz to vmlinuz-ide-2.4.22(you can find this in /boot) for the old kernel as back up if my new one fails. Add an identical sets of lilo lines for my new kernel, naming the right file name (vmlinuz-2.6.6) as i did on top.
Make sure all your compilers and whatnot are up to date, thought they should be with 9.1, except for module-utils. I'm not sure what else, I think that's all i had to update...get that from slack current.
In fact, I'd recommend using swaret or something to get up to current, but i don't think that's absolutely necessary.
I'd use the guide from shilo...worked for me http://www.linuxquestions.org/questi...=slackware+sys
Be sure to create a sys directory and mount it in fstab. It's also in the guide. Good luck!
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
My 2.6 version you don't have to make modules. It does it itself when you issues make.
That was the only difference between the steps of kernels 2.4 to 2.6
install the source
cd /usr/src
ln -s /usr/src/linux-2.6.# linux
make mrproper
make clean
make your_flavor_config
make dep
nohuo make bzImage 1>kernel.out 2>modules.err &
less kernel.out #check for errors
less modules.err #check for errors
#if all is well
make modules_install
then do the standard copies to the /boot
edit /etc/lilo.conf
lilo
reboot
And cross your fingers cause building and installing 2.6.# seems to break alot of stuff...
IMO 2.6 is buggy at least to slack. To much requires recompile or re-install after a kernel upgrade to 2.6
one suggestion - don't delete the existing kernel, and add a new entry to lilo.conf instead of editing the existing one, plus add a "prompt" option to lilo.conf if you don't have one - then lilo will give you an option of which kernel to boot, and it gives you a way out if the new kernel won't boot for some reason.
Originally posted by Nichole_knc My 2.6 version you don't have to make modules. It does it itself when you issues make.
That was the only difference between the steps of kernels 2.4 to 2.6
install the source
cd /usr/src
ln -s /usr/src/linux-2.6.# linux
make mrproper
make clean
make your_flavor_config
make dep
nohuo make bzImage 1>kernel.out 2>modules.err &
less kernel.out #check for errors
less modules.err #check for errors
#if all is well
make modules_install
then do the standard copies to the /boot
edit /etc/lilo.conf
lilo
reboot
And cross your fingers cause building and installing 2.6.# seems to break alot of stuff...
IMO 2.6 is buggy at least to slack. To much requires recompile or re-install after a kernel upgrade to 2.6
I had no issues w/ Slack 9.1 & 2.6.X . All I updated is core utilities just because I got over the uname -a being wrong.
L8tr
Feend
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.