Printable View
hows it goin people. I have a question for you about updating the linux kernel.
I'm running RH8.0 and the latest kernel RPM is 2.4.19.8
However some people have told me that the latest kernel version is 2.4.20.0. I also saw the same info
on google. Has anyone upgraded to that kernel. If so how would I do it. Im pretty sure that there is no RPM
for it yet. If you can point me to a nice tutorial on updating the kernel from source that would be nice, Thanks
I wonder why you would like to get kernel 2.4.20. Unless there is a certain problem that is fixed in the new kernel, I wouldn't recommend installing the new kernel.
However, there is a tutorial, called Kernel-HOWTO which explains what a kernel is, where you can get the latest version, how to configure and install the new kernel :
http://www.linux.org/docs/ldp/howto/Kernel-HOWTO.html
You can find the latest kernel-sources on www.kernel.org
Please be carefull when configuring/installing a new kernel. I suggest that you make a backup of your current kernel, before you replace it with a new one. (normaly the current kernel is in /boot/vmlinuz, but check your /etc/lilo.conf or other bootloader-configfile for the file that is used.)
Make sure you have a rescue-disk or put your new testkernel on disk an test it by booting from the disk. If something is wrong you will be able to reboot linux with your current kernel.
Another advise about configuring your kernel: A lot of modules (ie. drivers) can be chosen to be compiled in the kernel. You don't need all of them. Choose only those which you really need, if in doubt read the helpfile. For example : If you have a NIC (network interface card) of type x, you only need to include the module correspondig to this NIC. Don't select the other modules for NIC's. This will make your kernel bigger and size is limited. So only choose those modules that you really need.
You can also compile source code seperatly (as modules). These modules can be loaded during startup.
Good luck.
IMHO the easiest way is this way..
-----------------------------------------------------------
.: DISCLAIMER :.
If any of these actions harm your linux system, It's your own fault...
I am no responsible for the wellbeing of your system.
=================================
fire up a nice console..
and type the bold words (or copy by clicking your left button and selecting the text and then in the console press the midle mouse button)
su this sets you up as superuser (root) and asks for the root password
cd /usr/src/ places you in the folder where kernels are stored
wget http://www.kernel.org/pub/linux/kern...-2.4.20.tar.gz this downloads the current kernel 2.4.20
tar -xzvf linux-2.4.20.tar.gz unzips the current kernel
rm linux this removes the symbolic link to the current kernel sources
ln -s linux-2.4.20 linux makes a new symbolic link to the kernel sources
cd linux places you in the kernel source directory
cp ../linux-2.4.19/.config . copy's the old kernel configuration to the current folder (.)
make oldconfig configures the new kernel just like the old was configured, and asks you how new features are to be setup
make menuconfig is optional to check the configuration and make changes if and when desired
make dep modules modules_install install makes the dependencies, modules installs the modules and makes and installs the kernel
that's all..
hi,
I've got kernel 2.4.20 for my RH Linux 7.3. Haven't try yet for RH Linux 8.
After install new kernel..I have to tweak my boot loader (lilo). You might need to changed your boot loader configuration (but I'm not really sure for RH Linux 8..maybe same as RH LInux 7.3).
I have dialup connection for my internet connection..and that new kernel took me 5 hours to download+compile it.If you have have fast connection..you're lucky...
Good luck..
SweetAngel,
I would like to add that there is a possibility to update the sourcecode of the kernel, without having to download the entire source-code.
Every time a new kernel is released, for example v2.4.19 to v2.4.20, you can get this new version entirely or by applying a patch which will upgrade your current kernel-version to the next version.
This means that you must have a complete version of the kernel, to be able to upgrade (patch).
If you want to patch to the newest kernel-version, but your current kernel is older than one patch (example, new kernel version is 2.4.20, your kernel-version is 2.4.12), you have to apply all patches in the correct order, to get to the newest version. (2.4.12 -> patch13 -> 2.4.13 -> ... patch20 -> 2.4.20)
Please correct me if I'm wrong, but there are no patches for upgrading from for example 2.2.x to 2.4.x. In case of a major version-upgrade, you will have to download the entire source-code.
This quote explains how to patch your current kernel:
This is a quote from: http://www.kernel.org/pub/linux/kernel/READMEQuote:
- You can also upgrade between 2.0.xx releases by patching. Each
patch that is released for 2.0.xx contains only bugfixes. No
new features will be added to the Linux kernel until the 2.1.xx
development effort begins. To install by patching, get all the
newer patch files and do
cd /usr/src
gzip -cd patchXX.gz | patch -p0
(repeat xx for all versions bigger than the version of your current
source tree, _in_order_) and you should be ok. You may want to remove
the backup files (xxx~ or xxx.orig), and make sure that there are no
failed patches (xxx# or xxx.rej). If there are, either you or me has
made a mistake.
Alternatively, the script patch-kernel can be used to automate this
process. It determines the current kernel version and applies any
patches found.
cd /usr/src
linux/scripts/patch-kernel
You right about that...the reason I'had download entire source code..cause I wanna learn and "dive in" to Linux/*nix ..more seriously. And BTW I've already done both..Download entire source code or Applying path...Quote:
I would like to add that there is a possibility to update the sourcecode of the kernel, without having to download the entire source-code.
Every time a new kernel is released, for example v2.4.19 to v2.4.20, you can get this new version entirely or by applying a patch which will upgrade your current kernel-version to the next version.
My mandrake Linux 9 have new kernel too (2.4.20) and I've been working on kernel 2.5.52(I haven't finished it yet..yupe...I know still unstable, I just wanna play around with this kernel things), but apparently...it's hard to get 2.5.52 on...
Sweet_angel,
You probably know, but this might be usefull for others :
There are always two recent versions of the kernel. A stable version that can be used by most linux users and a development version where new features are added/tested. The version number is structured x.y.z, where the y indicates if it is a stable or a development version. If y is odd, then it is a development version. When it is even, it is a stable version. (for example : current kernel versions : 2.4.20 (stable) or 2.5.53 (development))
In the development version, new features are created. When the kernel development team (or Linus Torvalds, I'm not sure) decides there will be a new kernelversion, all new features are integrated in version x.(y+2).0 and this becomes the new stable version. At the same moment a new development version is created. For example : current stable version is 2.4.20, current development version is 2.5.53, if a new version is created the stable version will start at 2.6.0, the new development version will start at 2.7.0 .
ruleant --
The reason why i need the latest kernel is that it allows you to do some really useful bandwith control.
Ok I used the tutorial at kernel.org and the README that came with the kernel.tar.gz however i still have some problems. The new kernel will not bootup. I luckily did not erase the old kernel so i didnt lose anything. When I boot up and LILO asks which kernel to boot with, if i choose the the new one it will just automatically reboot. Does anyone have any ideas what this could be? This was my experimental machine, it had RH 7.2 on it. My guess was that it has something to do with lilo.conf but i dont know what it could be. I appreciate your help
Basicly you need to changed your boot loader from grub to lilo first..(if your default boot loader is grub).Quote:
The new kernel will not bootup. I luckily did not erase the old kernel so i didnt lose anything. When I boot up and LILO asks which kernel to boot with, if i choose the the new one it will just automatically reboot. Does anyone have any ideas what this could be? This was my experimental machine, it had RH 7.2 on it. My guess was that it has something to do with lilo.conf but i dont know what it could be. I appreciate your help
I didn't erased my old kernel...what you do..is just edit your lilo configuration
open your lilo configuration use your favorit editor (I like using vi).
vi /etc/lilo.conf and then just add your new kernel...
image=/boot/vmlinuz-2.2* <<< you will see something like this...this is your old kernel
label=linux
read-only
root=/dev/hda1
image=/boot/vmlinuz-2.4.20 << copy the one you already have (the old kernel from above)and
label=2420 just changed it to 2420
read-only
root=/dev/hda1
After that reboot...and you will see your new kernel with label "2420"...and your old kernel still there with label "linux" ...just choose with kernel you want boot up..and click that.
sweet_angel--Quote:
image=/boot/vmlinuz-2.2* <<< you will see something like this...this is your old kernel
label=linux
read-only
root=/dev/hda1
image=/boot/vmlinuz-2.4.20 << copy the one you already have (the old kernel from above)and
label=2420 just changed it to 2420
read-only
root=/dev/hda1
The above is exactly what i had in /etc/lilo.conf....but it is not booting up. It is possible that lilo is not my default boot
loader...how would i switch it to lilo
thanks for your help
by typing lilo..
that loads the /etc/lilo.conf configurtion and the Linux Loader to the selected part of your harddisk (MBR or something)..
just ( as super user (root) ) type: lilo
that should do the trick ;)
jinX-- Thanks for you input. LILO is my default boot loader but this new kernel is still not booting up. I'm almost ready
to give up. I followed exactly the readme of kernel-2.4.20.tar.gz but no luck. Did anyone else have any problems
installing the latest stable kernel. If so please let me know how you fixed it. Thanks guys
Does your new kernel start booting and hangs up during startup,
or doesn't it start at all?
If you misconfigured your kernel, it might happen that some things don't work - like network, soundcard, ... - or when you forget to include the code for using the ext2-filesystem, the kernel won't be able to mount the root partition (for example : /dev/hda1). Your linux system won't be able to start up. This are just examples of what can go wrong. There are a lot more reasons it might not work. I would advise you to check the configuration files for your kernel.
Another possibility is that the kernel didn't finish compiling. Due to misconfiguring or because the kernel is too big (this can happen :-) ). If your kernel is compiled (command 'make', without options), it should end without errors.
Maybe something went wrong when applying LILO. If you execute 'lilo', a list appears with all possible bootoptions. The default bootoption gets a star (*). If this list doesn't appear, or when an error message is present, your MBR wasn't changed, so it will still boot with the old configuration.
Please excuse me if I misinterpreted your descriptions. I hope this will get you on the way...
BTW: I use kernel 2.4.19, without any problems, so I suppose 2.4.20 should work allright. Unless you have just discovered a bug ... :-)
Quote:
Does your new kernel start booting and hangs up during startup,
it goes to the lilo prompt and waits for me to choose which kernel i want to bootup with. If I choose 2.4.7-10(RH 7.2 original kernel), it works fine. However, if i choose 2.4.20 it will say
loading kernel............................................ then the machine will automatically reboot.
After I run 'bzImage' I get a warning at the end saying that the image file is too big to fit on a disk. I assumed this meant i could not run 'bzDisk' Is this a correct assumption?Quote:
Another possibility is that the kernel didn't finish compiling. Due to misconfiguring or because the kernel is too big (this can happen :-) ). If your kernel is compiled (command 'make', without options), it should end without errors.
Yes, I use 2.4.19.8 on my other machine and it fine. I don't think I discovered a bug, but just a frustrated newbie...Quote:
BTW: I use kernel 2.4.19, without any problems, so I suppose 2.4.20 should work allright. Unless you have just discovered a bug ... :-)
Thanks for your suggestions.
Your lilo configuration is right.....you set it right...the problem is :Quote:
it goes to the lilo prompt and waits for me to choose which kernel i want to bootup with. If I choose 2.4.7-10(RH 7.2 original kernel), it works fine. However, if i choose 2.4.20 it will say
loading kernel............................................ then the machine will automatically reboot.
Your new kernel 2.4.20 "not install" in your RH LINUX.. because this one:
[/quote] After I run 'bzImage' I get a warning at the end saying that the image file is too big to fit on a disk. I assumed this meant i could not run 'bzDisk' Is this a correct assumption? [/quote]
You can use this command (make bzImage or make zImage) only if you have "high-density floppy".
So my advice try..to compile it again..
Try this first :
1. $ su
enter root's password
2. # cd /usr/src
3. # wget -c http://www.kernel.org/pub/linux/ker...-2.4.20.tar.bz2
4. # tar -xvjf linux-2.4.20.tar.bz2 (if you using tar.gz just do normal tar xvzf linux-2.4.20.tar.gz)
5. # rm -f linux-2.4 linux
6. # ln -s linux-2.4.20 linux-2.4
7. # ln -s linux-2.4 linux
8. # cd linux
9. # cp /boot/config-2.4.7-10 .config
10. # make xconfig ( customised your one..save and exit..)
11. # make dep
12. # make clean
13. # make bzImage <<<<<< first of all...do it again use this command if still get "warning" use this command " make zlilo"
14. # make modules
15. # make modules_install
16. # make install
17 # /sbin/reboot
I believe this method will work.... please let me know..how it goes
Hello people
I just wanted to put a final end to this thread, sweet_angel suggested it, so that it may serve as a tutorial for anyone else who has this same problem. Well the advice sweet_angel worked. It turned out the kernel wasnt booting because I had bad sectors on my harddrive or something. So the problem is easily solved by transfering the new image kernel onto a floppy with the
"make bzdisk" command. The hard part is troubleshooting and realizing that the harddrive is the problem.
Anyways thanks to all who advised.
Peace