Updating Fedora Core 4 Kernel: 2.6.11 to 2.6.17

Last month before I got vacation, I had a self chance to updating the fedora core 4 kernel from it's standard version 2.6.11 into the latest 2.6.17 on my laptop. I had done this since there were problems appeared in branches computers relating to unknown hardware devices detection in older kernel. And this is the step by step ways to do (the indonesian version you could find at this page):

1. Download the latest kernel version at here (40 MB)
2. From console (or terminal in X), install the rpm ball by command
rpm -ivh kernel-2.6.17...

3. Then after, a new directory exist at /usr/src/redhat
cd /usr/src/redhat/SOURCES

4. Find linux-2.6.17.tar.bz2 file in the current directory, unpack the tar ball by command
tar xjfv linux-2.6.17.tar.bz2

5. Make a new link to the new kernel
ln -s /usr/src/redhat/SOURCES/linux-2.6.17 /usr/src/linux

6. Type this to change to the directory
cd /usr/src/linux

7. This removes the current .config and other files
make mrproper

8. For ncurses GUI in the terminal
make menuconfig

9. Don't forget to add module support and kernel support for future hardware in menuconfig. Exit and Save to build the config file.
10. To clean the sources for they compile correctly
make clean

11. To make the kernel image, compile and creates compressed image of kernel
make bzImage

12. Compile selected modules
make modules

13. To install newly compile modules (default heads to /lib/modules/linux.2.6.17)
make modules_install

14. Copy the newly created kernel to /boot
cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.17

15. Also copy the newly created System.map to /boot
cp /usr/src/linux/System.map /boot/System.map-2.6.17

16. Make the new link to vmlinuz
ln -s /boot/vmlinuz-2.6.17 /boot/vmlinuz

17. Alse make the new link to System.map
ln -s /boot/System.map-2.6.17 /boot/System.map

18. Create the new one initrd.img according to latest kernel installed
/sbin/mkinitrd /boot/initrd-2.6.17.img 2.6.17

19. Edit the grub.conf found at /boot/grub.conf
File Before:
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.11-1.1369_FC4)
root (hd0,0)
kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
initrd
/boot/initrd-2.6.11-1.1369_FC4.img
title windows
rootnoverify (hd0,4)
chainloader +1
File After:
default=0
timeout=5
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Kernel Anyar FC4 (2.6.17)
root (hd0,0)
kernel
/boot/vmlinuz-2.6.17 ro root=LABEL=/ rhgb quiet
initrd
/boot/initrd-2.6.17.img

title Fedora Core (2.6.11-1.1369_FC4)
root
(hd0,0)
kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.11-1.1369_FC4.img
title windows
rootnoverify
(hd0,4)
chainloader +1
(The changes are followed by the bold marked, go editing the files within the rules)
20. Exit and save grub.conf. Re-install it
/sbin/grub-install hd0

21. Finish! Reboot
22. Finally, prove that you have a new kernel
uname -r
If you are doing the right thing, your system will replied with this one
2.6.17

Sincerelly,

Eko Wahyudiharto
PS: If you've benefit from this blog,
you can support it by making a small contribution.

Enter your email address:

Delivered by FeedBurner

Post a Comment Bookmark and Share

 

  1. Anonymous Ananthi said,

    Monday, February 09, 2009 2:05:00 AM

    Hello sir,
    I tried all the steps that was given by you. But instead of copying the kernel in /usr/src/redhat/SOURCE i did it in /home every thing went with out any problem. But when i boot my system i am getting an error like Error 1:Filename must be either an absolute pathname or blocklist. my grub.conf is given below
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,5)
    # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=1
    timeout=5
    splashimage=(hd0,5)/grub/splash.xpm.gz
    hiddenmenu
    title Fedora (2.6.27.8)
    root (hd0,5)
    kernel /vmlinuz-2.6.27.8 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.27.8.img
    title Fedora (2.6.21-1.3194.fc7)
    root (hd0,5)
    kernel /vmlinuz-2.6.21-1.3194.fc7 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
    initrd /initrd-2.6.21-1.3194.fc7.img
    title Other
    rootnoverify (hd0,0)
    chainloader +1
    When i search through google i got as it is due to the logical partitioning but is it right or am i went wrong on any procedure.
    Sir kindly help me to finish up my work.
    thank you. Kindly reply me at ananthalakshminatesan@gmail.com
    regards,
    AnanthiNatesan

  2. Blogger Eko Wahyudiharto said,

    Monday, February 09, 2009 11:29:00 AM

    I don't know for sure but you told me that you did copying the kernel in /home. Is your kernel compilation successful yet?

    In my opinion, there is no any relation about the use of logical partition on your Linux with this kernel updating progress.

  3. Blogger AnanthaLakshmi said,

    Tuesday, February 10, 2009 2:23:00 AM

    yes my kernel compilation is successfull. Without that how can i get System.map and vmlinuz.

  4. Blogger AnanthaLakshmi said,

    Tuesday, February 10, 2009 2:25:00 AM

    Error 1:Filename must be either an absolute pathname or blocklist.
    Sir what does this error exactly meant?
    thanks for your reply sir.

  5. Blogger Eko Wahyudiharto said,

    Tuesday, February 10, 2009 2:13:00 PM

    Well, it;s kinda weird situation, but I'm afraid that this may caused by your compilation on your current home directory.

    However, I can't define your problem further. But I'm suspicious to your partition either. Can you boot the system with single mode instead?

  6. Blogger AnanthaLakshmi said,

    Wednesday, February 11, 2009 1:50:00 AM

    hello sir,
    i tried the above things in /usr/src/redhat/SOURCE and when i boot the system i got the following error now it may be possible for you to find the solution.
    ERROR...........
    Reading all physical volumes. This may take a while.....
    No volume groups found
    Activating logical volumes
    Volume group "volgroup 00" not found
    creating root device
    mounting root filesystem
    mount:Could not find filesystem '/dev/root'
    setting up otherfilesystem
    setting up newrootfs
    setuproot :moving /dev failed: No such file or directory
    no fstab.sys, mounting internal defaults
    setuproot error mounting /proc: No such file or directory
    setuproot eror mounting /sys:No such file or directory
    switching to new root and running init
    unmounting old /dev
    unmounting old /proc
    unmounting old /sys
    switchroot: mount failed :No such file or directory
    Booting has failed
    kernel panic-not syncing: Attempted to kill init

  7. Blogger AnanthaLakshmi said,

    Wednesday, February 11, 2009 1:51:00 AM

    sir,
    Hope so now u can help me to analyse where i went wrong
    regards,
    Ananthi

  8. Blogger Eko Wahyudiharto said,

    Wednesday, February 11, 2009 8:56:00 AM

    Ok then, now it's turn to fatal error (kernel panic message). It's positively caused by fault(?) on your current partition & I'm afraid you need to re-install the system again.

    Just for suggestion, if you try to re-install it, don't let the installer create partition automatically - so that it wouldn't create a weird partition likes /dev/VolGroup00/LogVol00. If you define custom, it will create partition name such as /dev/hda1 (which #1 refer to your partition number) & - once again - this could be your problem.

    Anyway, before do this, let you try to open the system with single mode or safe boot. Can it loaded?

  9. Blogger AnanthaLakshmi said,

    Wednesday, February 25, 2009 12:56:00 PM

    Hello Sir,
    I finished doing that work. One thing that i forget to say is i am not upgrading my kernel but i am practicing to customize a kernel for embedded board before that i want to do it desktop. The initrd image that was created using mkinitrd will work only upgrating the kernel but for me nothing to do with upgrading kernel. I am using the older version of kernel. And one thing that i found was there is nothing installation problem. Thank for your co-operation sir. May i know what u r doing sir.
    regards,
    AnanthiNatesan.

  10. Blogger Eko Wahyudiharto said,

    Wednesday, February 25, 2009 4:05:00 PM

    @Ananthi: Is this your FB profile link? http://www.facebook.com/people/Ananthalakshmi-S/517063197

  11. Blogger AnanthaLakshmi said,

    Wednesday, February 25, 2009 4:10:00 PM

    No sir that is not mine. I don't use face book but i use orkut often with the name AnanthiNatesan. If u wish u can join with me. My id is ananthalakshminatesan@gmail.com

  12. Blogger Eko Wahyudiharto said,

    Wednesday, February 25, 2009 4:42:00 PM

    And me ==> kokocamp[at]gmail.com

  13. Blogger kaushik said,

    Sunday, July 26, 2009 2:28:00 PM

    Hi Ananthi,

    I am trying to update Fedora kernel 2.6.15 to 2.6.17 using given procedure by you.

    I got "no rules found" error while doing "make bzimage"

    Please, help me. thanks in advance.

  14. Anonymous Ananthi said,

    Wednesday, July 29, 2009 3:13:00 PM

    Dear Koushik,
    Its not make bzimage its make bzImage. Now hope so you will get.
    May i know what u r doing. if u want any help u can get me thr' ananthalakshminatesan@gmail.com

  15. Anonymous Troll_Dragon said,

    Tuesday, October 27, 2009 3:13:00 AM

    Hey Eko Wahyudiharto!

    Great Instructions worked like a charm!

    Thanks!

Post a Comment

Leave comments here...