The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Kernel just wont update

Discussion in 'General Discussion' started by tmellon, Jul 18, 2002.

  1. tmellon

    tmellon Well-Known Member

    Joined:
    Aug 15, 2001
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Sarasota, FL
    I've tried everything to get the kernel on my server to update -- and no luck.

    I'm currently running at: 2.4.9-34.

    I tried installing 2.4.18, and nothing has happened.

    I'm very sure I'm doing this right (I've done it successfully on other servers before - thou its been a while) - but this one just doesn't want to cooperate with me.

    I've followed everything over at: http://www.tldp.org/HOWTO/Kernel-HOWTO.html - to a &T& and still nothing.

    And yes, I've rebooted -- still reading at 2.4.9.34.

    I'm running RedHat 7.2

    Anyone want to assist me? Please?

    Thanks a million!!
    -
    Tonya
    -
     
  2. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    find what you have to download by

    rpm –qa | grep ‘kernel’

    After downloading the kernel and its dependencies if you want to update an RPM release of Kernel use this command

    rpm –ivh kernel*.rpm

    Let’s consider that you have kernel 2.4.9-34 on your system
    And want to upgrade to kernel 2.4.18
    By using above command you’ll have both kernel on your box, RPM (Red hat Package Manager) automatically makes any necessary changes to GRUB boot loader if you have GRUB then change default to new kernel by editing /etc/grub.conf , Graceful Restarting your server will bring up new kernel but if you have LILO boot loader you have to update its configuration manually

    i.e.
    [quote:81fb67ec6a][i:81fb67ec6a]example /etc/lilo.conf contains[/i:81fb67ec6a]

    prompt
    timeout=50
    default=linux
    boot=/dev/sda
    disk=/dev/sda
    bios=0x80

    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear

    image=/boot/vmlinuz-2.4.9-34
    label=linux
    initrd=/boot/initrd-2.4.9-34.img
    read-only
    root=/dev/sda6

    [/quote:81fb67ec6a]

    you have to change it to this

    [quote:81fb67ec6a][i:81fb67ec6a]/etc/lilo.conf[/i:81fb67ec6a]

    prompt
    timeout=50
    [b:81fb67ec6a]default=linux1[/b:81fb67ec6a]
    boot=/dev/sda
    disk=/dev/sda
    bios=0x80

    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear

    image=/boot/vmlinuz-2.4.9-34
    label=linux
    initrd=/boot/initrd-2.4.9-34.img
    read-only
    root=/dev/sda6
    [b:81fb67ec6a]
    image=/boot/vmlinuz-2.4.18
    label=linux1
    initrd=/boot/initrd-2.4.18.img
    read-only
    root=/dev/sda6
    [/b:81fb67ec6a]
    [/quote:81fb67ec6a]
    then use this command to apply the changes
    lilo –v -v

    after restarting and if everything is fine then you can remove the old kernel first make sure you have new kernel up and running by using

    uname –a

    then remove the old kernel by using

    rpm –e kernel-2.4.9-34

    and you have to modify lilo again

    [quote:81fb67ec6a][i:81fb67ec6a]change /etc/lilo.conf to[/i:81fb67ec6a]

    prompt
    timeout=50
    [b:81fb67ec6a]default=linux[/b:81fb67ec6a]
    boot=/dev/sda
    disk=/dev/sda
    bios=0x80

    map=/boot/map
    install=/boot/boot.b
    message=/boot/message
    linear

    [b:81fb67ec6a]
    image=/boot/vmlinuz-2.4.18
    label=linux
    initrd=/boot/initrd-2.4.18.img
    read-only
    root=/dev/sda6
    [/b:81fb67ec6a]
    [/quote:81fb67ec6a]
    and run this command

    lilo –v –v

    that’s it

    If you need GRUB details just post a request
     
  3. tmellon

    tmellon Well-Known Member

    Joined:
    Aug 15, 2001
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Sarasota, FL
    Yes, Grub details would be great... I'm not using Lilo
     
  4. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:2593d2ca54][i:2593d2ca54]Originally posted by tmellon[/i:2593d2ca54]

    Yes, Grub details would be great... I'm not using Lilo
    [/quote:2593d2ca54]


    This is the instruction of Kernel upgrade using GRUB boot loader

    By considering that your current kernel version is 2.4.9-34 and want to upgrade to kernel 2.4.18 after downloading the files use this command

    rpm –ivh kernel*.rpm

    Then /etc/grub.conf looks like this
    [quote:2593d2ca54][i:2593d2ca54]/etc/grub.conf[/i:2593d2ca54]

    # 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,0)
    # kernel /vmlinuz-version ro root=/dev/sda6
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=0
    timeout=10
    splashimage=(hd0,0)/grub/splash.xpm.gz

    title Red Hat Linux (2.4.9-34)
    root (hd0,0)
    kernel /vmlinuz-2.4.9-34 ro root=/dev/sda6
    initrd /initrd-2.4.9-34.img

    title Red Hat Linux (2.4.18)
    root (hd0,0)
    kernel /vmlinuz-2.4.18 ro root=/dev/sda6
    initrd /initrd-2.4.18.img

    [/quote:2593d2ca54]
    You have to change it to this
    [quote:2593d2ca54][i:2593d2ca54]/etc/grub.conf[/i:2593d2ca54]

    # 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,0)
    # kernel /vmlinuz-version ro root=/dev/sda6
    # initrd /initrd-version.img
    #boot=/dev/sda
    [b:2593d2ca54]default=1[/b:2593d2ca54]
    timeout=10
    splashimage=(hd0,0)/grub/splash.xpm.gz

    title Red Hat Linux (2.4.9-34)
    root (hd0,0)
    kernel /vmlinuz-2.4.9-34 ro root=/dev/sda6
    initrd /initrd-2.4.9-34.img

    [b:2593d2ca54]
    title Red Hat Linux (2.4.18)
    root (hd0,0)
    kernel /vmlinuz-2.4.18 ro root=/dev/sda6
    initrd /initrd-2.4.18.img
    [/b:2593d2ca54]
    [/quote:2593d2ca54]
    Graceful restart your server and if everything is fine after that
    Use this command to see new kernel version

    uname –a

    Then uninstall the old kernel by this command

    rpm –e kernel-2.4.9-34

    And make /etc/grub.conf as follows

    [quote:2593d2ca54][i:2593d2ca54]/etc/grub.conf[/i:2593d2ca54]

    # 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,0)
    # kernel /vmlinuz-version ro root=/dev/sda6
    # initrd /initrd-version.img
    #boot=/dev/sda
    [b:2593d2ca54]default=0[/b:2593d2ca54]
    timeout=10
    splashimage=(hd0,0)/grub/splash.xpm.gz

    [b:2593d2ca54]
    title Red Hat Linux (2.4.18)
    root (hd0,0)
    kernel /vmlinuz-2.4.18 ro root=/dev/sda6
    initrd /initrd-2.4.18.img
    [/b:2593d2ca54]
    [/quote:2593d2ca54]

    that’s it

    Attention: if you tried GRUB but your new kernel is not up and running may be you have LILO boot loader as your default loader.
     
  5. tmellon

    tmellon Well-Known Member

    Joined:
    Aug 15, 2001
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Sarasota, FL
    Thanks for the help, I appreciate it!! :)

    I'll give it a try this afternoon, and report my findings.

    Thanks again!!
    Tonya
     
  6. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    itf-

    here's a quick and stupid question:

    remotely, if you've got machines with grub AND lilo, how do you tell what the system is using as the boot loader? can you tell from within the OS half a continent away? or is the only way to summon a lackey to watch the screen during a restart to see what's booting the kernels ?

    thanks much!
     
  7. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:032ed46ff4][i:032ed46ff4]Originally posted by feanor[/i:032ed46ff4]


    itf-

    here's a quick and stupid question:

    remotely, if you've got machines with grub AND lilo, how do you tell what the system is using as the boot loader? can you tell from within the OS half a continent away? or is the only way to summon a lackey to watch the screen during a restart to see what's booting the kernels ?

    thanks much!
    [/quote:032ed46ff4]
    Type this command and read the result. (in Red Hat if you haven't manually installed boot loader software)

    cat /root/anaconda-ks.cfg | grep 'bootloader'


    If you need more details don't hesitate to post a request.
     
  8. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    exciting:


    root@server [/]# cat /root/anaconda-ks.cfg | grep 'bootloader'
    bootloader


    It doesn't seem that variable/setting is defined?
    I am going to immerse myself in some anaconda docs now.

    thanks....
     
  9. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:5960b88ac5][i:5960b88ac5]Originally posted by feanor[/i:5960b88ac5]


    exciting:


    root@server [/]# cat /root/anaconda-ks.cfg | grep 'bootloader'
    bootloader


    It doesn't seem that variable/setting is defined?
    I am going to immerse myself in some anaconda docs now.

    thanks....
    [/quote:5960b88ac5]

    root@server [/]# cat /root/anaconda-ks.cfg | grep 'bootloader'
    bootloader

    it means GRUB is your default bootloader

    if you see this instead you have LILO

    root@server [/]# cat /root/anaconda-ks.cfg | grep 'bootloader'
    bootloader --useLilo


    However there are some practical methods to detect boot loader too
     
  10. tmellon

    tmellon Well-Known Member

    Joined:
    Aug 15, 2001
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Sarasota, FL
    I was just told that kernel 2.4.18-5 isn't EXT3 compatible...

    Is there a kernel that is?
    *sigh*
     
  11. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:35e806a3ef][i:35e806a3ef]Originally posted by tmellon[/i:35e806a3ef]

    I was just told that kernel 2.4.18-5 isn't EXT3 compatible...

    Is there a kernel that is?
    *sigh*[/quote:35e806a3ef]

    It is impossible, refer to Red Hat
    It seems that you've done something wrong
    Kernel 2.4.18-5 is for Red Hat 7.3
    Make sure you downloaded the right version from red hat
    What version of red Hat do you have?

    If you have an older version of Linux and kernel 2.4.18 is not available through Red Hat upgrade site you have to install an original version from kernel.org or it is recommended to install GRSecurity

    or even Upgrade to Red Hat 7.3 if you would like
     
  12. thesoul

    thesoul Member

    Joined:
    Mar 16, 2002
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    What does this mean?

    stdin: is not a tty
     
  13. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:e940f75c9f][i:e940f75c9f]Originally posted by thesoul[/i:e940f75c9f]

    What does this mean?

    stdin: is not a tty[/quote:e940f75c9f]

    If you prefer a short answer read this:

    It doesn't matter just ignore it

    (means: standard input is not a tty - due to SSH)

    But if you need more technical details just send a request.
     
  14. tmellon

    tmellon Well-Known Member

    Joined:
    Aug 15, 2001
    Messages:
    64
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Sarasota, FL
    Sorry for the late reply.

    I have 7.2 on the server.
    I was told by my noc, that 2.4.18 isn't compatible with the EXT3 filesystem/7.2. (after the server didn't reboot - and $75 later to fix it)

    But I was told by someone else that I should have no problems upgrading to 2.4.18 on 7.2. And one of my friends has the kernel on his 7.2 machine...

    :/

    I tried install GRSecurity - but for some reason it just didn't want to work for me. :/ dunno...
     
  15. itf

    itf Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    624
    Likes Received:
    0
    Trophy Points:
    16
    [quote:331601e2d5][i:331601e2d5]Originally posted by tmellon[/i:331601e2d5]

    Sorry for the late reply.

    I have 7.2 on the server.
    I was told by my noc, that 2.4.18 isn't compatible with the EXT3 filesystem/7.2. (after the server didn't reboot - and $75 later to fix it)

    But I was told by someone else that I should have no problems upgrading to 2.4.18 on 7.2. And one of my friends has the kernel on his 7.2 machine...

    :/

    I tried install GRSecurity - but for some reason it just didn't want to work for me. :/ dunno...[/quote:331601e2d5]
    I wrote how to upgrade; not which version you should use, there are many users on the cpanel using different versions of Redhat but the upgrade process are the same, Redhat 7.2 can not run with EXT3 and 2.4.18 kernel at the same time (i wrote i.e in my posts means in example) most of 7.2 installations are on EXT2 file system due to using GRSecurity, you didn't wrote that you are EXT3 user, you have to forgot one of them, EXT3 or 2.4.18 Kernel or upgrade to Redhat 7.3 (but please remember that after upgrading Redhat to 7.3 you have to reinstall Cpanel if you are in a production environment backup is critical)
    also if you have Redhat 7.2 with EXT2 file system and want 2.4.18 kernel it is recommended to install GRSecurity Kernel. (Do not use 2.4.18 kernels for 7.3)

    Please accept a piece of advice answers are coming from your question when you read the answers you have to consider that these are the answers just subject to that question nothing more.

    Attention: Do not maintain your Kernel or system scripts if you are not an experienced Linux user or Administrator.
     
Loading...

Share This Page