Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
ok mates, I have a really big problem..
I upgraded kernel million times on debian based linux, both tarball and .deb installers, but can someone help me with step by step installing on slackware. did it few times, but it got a kernel panic :P couldn't even start.
keywords: slackware 13.37 amd64, kernel is version 3.1.1 packed in tar.bz2 from kernel.org
thanks!
I just did an upgrade about an hour ago from the 2.6.37.6 kernel to the 3.2.0-rc2 kernel on Slackware 13.37 64bit edition in VMware. These are the steps that I took, hopefully you'll find them useful.
In the terminal:
Code:
#Downloads the file into /tmp and extracts it to /usr/src/
cd /tmp/
wget [kerneldotorg]/pub/linux/kernel/v3.0/testing/linux-3.2-rc2.tar.bz2
tar -C /usr/src -jxvf linux-3.2-rc2.tar.bz2
cd /usr/src/
#removes sym link and sets it to new path
rm linux
ln -s linux-3.2-rc2 linux
#I decided to copy my old config settings across, you don't need to do this. If you choose this option, it'll then present you with new options now available in the new kernel.
zcat /proc/config.gz > /usr/src/linux/.config
cd linux
make oldconfig
#Make any last changes here before compiling
make menuconfig
make
make modules_install
#Copies the files to /boot and makes a backup of your old System.map and vmlinuz files to System.old and vmlinuz.old
make install
#Simply restart and you're in your new kernel!
The readme in the kernel's source directory will tell you _not_ to use the /usr/src directory for the build, because it messes with the compiler. Otherwise, Basica has the steps there below for some one that can get it right on the first try. Leave the old stuff alone until you get the new one working for sure, is my recommendation.
Getting the configuration right took me about 15 tries when I did it, mostly because I didn't include module support and the configuration tools wouldn't take my changes properly. I strongly recommend setting the 'Alt-Print Screen' switch to true, so you can get some debug information from those kernel panics. And keep a boot disk handy so you can set up your boot loader when it's time to take a break from kernel building.
The readme in the kernel's source directory will tell you _not_ to use the /usr/src directory for the build, because it messes with the compiler. Otherwise, Basica has the steps there below for some one that can get it right on the first try. Leave the old stuff alone until you get the new one working for sure, is my recommendation.
Getting the configuration right took me about 15 tries when I did it, mostly because I didn't include module support and the configuration tools wouldn't take my changes properly. I strongly recommend setting the 'Alt-Print Screen' switch to true, so you can get some debug information from those kernel panics. And keep a boot disk handy so you can set up your boot loader when it's time to take a break from kernel building.
Best Regards,
New Ink -- Henry
Thanks Basica for code, I will maybe get some balls to do it
Henry, for your 15 tries I got on my sixth try and lost some nerves.. last time I killed lilo, and now I made a fine dualboot with w7(because games and family needs - retards don't know how to use slackware or even ubuntu, blah blah blah)
but thank you. I will try it six times more and 3 more times to get your highscore even if next time it will work, just for pleasure hahaha
No problem, hopefully it works out for you. I won't argue with the compilation directory location as I was simply following steps from a couple of different places (including the one linked before my initial post) and they all did the work in the /usr/src directory. It worked fine for me but YMMV.
I was quite happy as this was my first successful compile. The last time I tried to do it was back in Ubuntu 4.10 (I've been playing with Linux on and off for a while, more off than on though) and I couldn't get it to boot afterwards either, I tried 3 times before giving up, especially since I had an old computer at the time, the compile times were pretty long. Now, even inside a VM, it took ~30mins which isn't too bad as I can still use my PC and do other things to pass the time
What I find useful, especially if you're feeling a little bit defeated is to try and take as many variables out of the equation as possible. In other words, use your old config file that you obviously know works, use the default settings and then go from there. It'll most likely work off the bat and will give you a little bit of a mental and positive boost From there, just keep upping the ante. Also, I'm doing this in a VM environment so if I screw anything up majorly, I'm just a few seconds aware from my restore point to have at it again which makes it easier to experiment and use trial and error with things when you don't have to worry about spending an hour or so (maybe more) getting everything working again, or simply reinstalling the system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.