Suse/NovellThis Forum is for the discussion of Suse 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.
What I'm trying to do:
I'm trying to update my system to 2.6.9, so I downloaded the 2.6.9 kernel source and do the following steps
- su root
- make oldconfig
- make menuconfig
- make bzImage
- make modules_install install
- cp arch/i386/boot/bzImage /boot/ (pretty sure about the path)
Then edit my grub config and I leave the original entry there in case I get a kernel panic.
I've done this three times, and I've looked at posts which I believe those are the correct steps to take. The kernel always panics (no I'm to stupid to write the error down. I'll will next time as I'm fairly certian it will fail.) Now the even better part, for whatever reason, I can't just select the original entry in grub and boot the stock kernel. It panics as well.
Does someone see and error in the sequence I execute the commands?
I'm not giving up, so I should have this compiled tonight and I will post my errors. Thanks for any/all help.
Possibly, but the strangest thing that happens is the stock kernel becomes useless as it will give me the same error when I boot it that the newly compiled one does.
I suspect posting the error will give some insight, but I have to sleep then wake up and compile.
Actually, after expanding the kernel tarball, you want to do the following in the order shown:
cp arch/i386/boot/bzImage /boot/bzImage-2.6.9
Then edit your bootloader (GrUB is what I think you are using) to point to bzImage-2.6.9 by adding a new paragraph in the menu.lst file. I simply copy the original lines that point to the vmlinuz, paste & edit a new set of lines that point to bzImage-2.6.9. This leaves the original kernal (vmlinuz) in tact, and bootable, in case you need to adjust the new kernel by recompiling. Even after getting the new kernel tuned up, I leave the original in place as a safety.
You do not have to use the System.map, nor create an initrd file.
This procedure has always worked for me on all SuSE distro's.
Ok, I did eventually get the 2.6.9 kernel compiled and was able to boot the system. With that, I happily blew away the install and reloaded 9.1 professional, Downloaded the 2.6.9 source and used my notes. With a stock 2.4.6-52, I first made a 2.6.9 without any changes and tested to make sure it was bootable, afterwards I am going to use menuconfig to make the changes. Here are the steps I did:
make menuconfig (1st compile I didn't change anything)
cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.9
mkinitrd -k vmlinux-2.6.9 -i initrd-2.6.9
Now edit the /boot/grub/menu.lst
Add this entry, you could leave out the comments or put in your own
### New 2.6.9 kernel ###
kernel (hd0,2)/boot/vmlinux-2.6.9 root=/dev/hda3
Now you WILL HAVE TO change the numbers inside the () to match the previous kernel entry as my partition layout isn't the same as yours.
Save and reboot, then boot your new kernel.
I will make another entry similar but change all the "-2.6.9" entires to -test which will be the kernel I actually used menuconfig on and changed some values.
I hope this helps at least one person.
Last edited by musicman_ace; 11-28-2004 at 03:15 AM.