Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11
I am a newbie to linux I have been using 2.6.18-8.el5 kernel version with my CentOS 5 I want to compile a new kernel - 2.6.24 I have compiled the ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jan 2008
    Posts
    3

    Cannot boot new kernel


    I am a newbie to linux
    I have been using 2.6.18-8.el5 kernel version with my CentOS 5
    I want to compile a new kernel - 2.6.24
    I have compiled the kernel by
    =>downloading the source
    =>copying the working .config to /usr/src/kernel/linux-2.6.24
    =>make menuconfig, (and save)
    =>make
    => make modules
    => make modules_install
    => make install

    I can see the kernel image, the intird image and the grub updated

    When I try to reboot through the new kernel is
    gives message
    Cannot find filesystem /dev/root
    ...
    ..
    and some kernel panic message

    Anyone please help me debug the problem

    Awaiting a response

    Thank you,
    Gary

  2. #2
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    Hi and Welcome !

    I can see the kernel image, the intird image and the grub updated
    Post the contents of grub.conf file and output of this
    Code:
    ls /boot
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  3. #3
    Just Joined!
    Join Date
    Jan 2008
    Posts
    3
    Pasting the contents of the grub.conf
    -----------------------------------------------------------------------------------------------------------------------------------
    10 default=3
    11 timeout=5
    12 splashimage=(hd0,1)/boot/grub/splash.xpm.gz
    13 hiddenmenu
    14 title CentOS (2.6.23.12)
    15 root (hd0,1)
    16 kernel /boot/vmlinuv-2.6.23.12 ro root=LABEL=/ rhgb
    17 initrd /boot/initrd-2.6.23.12.img
    18 title CentOS (2.6.24-rc5)
    19 root (hd0,1)
    20 kernel /boot/vmlinuz-2.6.24-rc5 ro root=LABEL=/ rhgb quiet
    21 initrd /boot/initrd-2.6.24-rc5.img
    22 title CentOS (2.6.18-8.1.15.el5xen)
    23 root (hd0,1)
    24 kernel /boot/xen.gz-2.6.18-8.1.15.el5
    25 module /boot/vmlinuz-2.6.18-8.1.15.el5xen ro root=LABEL=/ rhgb quiet
    26 module /boot/initrd-2.6.18-8.1.15.el5xen.img
    27 title CentOS (2.6.18-8.el5)
    28 root (hd0,1)
    29 kernel /boot/vmlinuz-2.6.18-8.el5 ro root=LABEL=/ rhgb quiet
    30 initrd /boot/initrd-2.6.18-8.el5.img
    31 title CentOS (2.6.24-rc5)My installation
    32 root (hd0,1)
    33 kernel /boot/vmlinuz-2.6.24-rc5 ro root=LABEL=/ rhgb quiet
    34 initrd /boot/initrd-2.6.24-rc5.img
    35 title Other
    36 rootnoverify (hd0,0)
    37 chainloader +1
    ---------------------------------------------------------------------------------------------------------------------------------
    The problem occurs with 2.6.23.12, 2.6.24-rc5 and(2.6.24-rc5)My installation


    The output of ls -a /boot is
    --------------------------------------------------------------------------------------------------------------------------
    .
    ..
    config-2.6.18-8.1.15.el5xen
    config-2.6.18-8.el5
    grub
    initrd-2.6.18-8.1.15.el5xen.img
    initrd-2.6.18-8.el5.img
    initrd-2.6.23.12.img
    initrd-2.6.24.img
    initrd-2.6.24-rc5.img
    initrd.img-2.6.24
    initrd.img-2.6.24-rc5
    message
    mkinitramfs
    newkernel
    symvers-2.6.18-8.1.15.el5xen.gz
    symvers-2.6.18-8.el5.gz
    System.map
    System.map-2.6.18-8.1.15.el5xen
    System.map-2.6.18-8.el5
    System.map-2.6.23.12
    System.map-2.6.24-rc5
    System.map-2.6.24-rc5.old
    vmlinuz
    vmlinuz-2.6.18-8.1.15.el5xen
    vmlinuz-2.6.18-8.el5
    vmlinuz-2.6.23.12
    vmlinuz-2.6.24
    vmlinuz-2.6.24-rc5
    vmlinuz-2.6.24-rc5.old
    xen.gz-2.6.18-8.1.15.el5
    xen-syms-2.6.18-8.1.15.el5
    ------------------------------------------------------------------------------------------------------------------------
    Regards,
    Gaurav

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Jan 2008
    Posts
    3
    Hi devils_casper
    Any suggestion?
    Any other information you need?
    Note that the current running kernel is different from the one i am compiling.
    Please give me pointers in debugging this problem.
    Regards,
    Gary

  6. #5
    Just Joined!
    Join Date
    Nov 2008
    Posts
    11

    solution to this?

    hi! i have exactly the same problem.

    did you find a solution for this?
    i have the same distro as you

  7. #6
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    Quote Originally Posted by adriangolding View Post
    hi! i have exactly the same problem.

    did you find a solution for this?
    i have the same distro as you
    Hi and Welcome !

    Post the contents of grub.conf file and output of fdisk -l command here.
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  8. #7
    Just Joined!
    Join Date
    Nov 2008
    Posts
    11

    my grub.conf and fdisk

    hello: grub.conf :


    # 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,1)
    # kernel /vmlinuz-version ro root=/dev/sda3
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=2
    timeout=5
    splashimage=(hd0,1)/grub/splash.xpm.gz
    hiddenmenu
    title CentOS (2.6.24)
    root (hd0,1)
    kernel /vmlinuz-2.6.24 ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.24.img
    title CentOS (2.6.24.7)
    root (hd0,1)
    kernel /vmlinuz-2.6.24.7 ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.24.7.img
    title CentOS (2.6.18-8.el5)
    root (hd0,1)
    kernel /vmlinuz-2.6.18-8.el5 ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.18-8.el5.img

    ---------

    fdisk -l :

    Disk /dev/sda: 250.0 GB, 250000000000 bytes
    255 heads, 63 sectors/track, 30394 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes

    Device Boot Start End Blocks Id System
    /dev/sda1 1 6 48163+ de Dell Utility
    /dev/sda2 * 7 19 104422+ 83 Linux
    /dev/sda3 20 10218 81923467+ 83 Linux
    /dev/sda4 10219 30394 162063720 5 Extended
    /dev/sda5 10219 11238 8193118+ 82 Linux swap / Solaris

    --------

    it is a very strange problem: it was going into init 5 and i can see the CentOs graphical loading screen and it starts to load all the modules but right after it loads the last module (i think its smartd), all these while its in the graphical mode, it suddenly goes to the login localhost screen (init 3).

    i logged in as root and tried to enter 'init 5' but nothing happens. no error messages or any thing happening.

    thank you for your quick reply ..

  9. #8
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    It looks like Display problem only.
    What the output of startx command? Post the output of this too :
    Code:
    su -
    /sbin/lspci | grep -i vga
    grep -i driver /etc/X11/xorg.conf
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  10. #9
    Just Joined!
    Join Date
    Nov 2008
    Posts
    11

    lspci and xorg.conf printout

    startx:

    xauth: creating new authority file /root/.serverauth.3489

    Fatal server error:
    Server is already active for display 0
    If this server is no longer running, remove /tmp/.X0-lock and start again

    lspci output:

    00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2)

    xorg.conf:

    Driver "kbd"
    Driver "vesa"

    thank you - adrian

  11. #10
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    Boot up in Single User Mode and execute startx command. Post output here.

    Highlight CentOS title In GRUB Menu and press 'e'. Select 'kernel' line and press 'e' again. Add <space> 3 at the end of line and hit 'Enter' key.
    Press 'b' and CentOS will boot up in command line mode and drop you at Login Prompt.

    e -- Select kernel line -- e -- 3 -- Enter key -- b

    Log in as root and execute this
    Code:
    startx
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •