Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Kernel Issues from the upgrade

  1. #11
    Join Date
    Aug 2008
    Location
    South East Montana
    Beans
    6,153

    Re: Kernel Issues from the upgrade

    Well, if you are still there and going to work on this, here is what you better do;

    Rename the /boot/grub/menu.lst to menu.OLD and move it to your Desktop to be safe. Do the same thing with your grub.cfg file.

    Go to synaptic and reload it. Find grub. Remove anything you find in synaptic related to grub (.97 or 1.97).

    Staying with synaptic, install Grub2 (meta package for grub2), grub-common, and grub-pc. Be sure that you are watching the :"details" when this is being installed to see if update grub is run and to see if it is installed on your drive.

    I would, if that happened (and I am sure it would), update your machine while you are in synaptic.

    This should get you a kernel update and should run update-grub again.

    Repost your /boot/grub/grub.cfg contents. Do not reboot until this is straight.
    Dell 480 XPS 3G ram Quad Core 2.40GHz, Radeon HD 2400 PRO, Audigy1, 3x320G HDD, 320G External, Debian Testing for use, Debian Squeeze for secure use, Debian Sid for FUN

  2. #12
    Join Date
    Aug 2009
    Beans
    20

    Re: Kernel Issues from the upgrade

    Am I doin it right?

    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by /usr/sbin/grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #

    ### BEGIN /etc/grub.d/00_header ###
    load_env
    set default="0"
    if [ ${prev_saved_entry} ]; then
    saved_entry=${prev_saved_entry}
    save_env saved_entry
    prev_saved_entry=
    save_env prev_saved_entry
    fi
    insmod ext2
    set root=(hd0,6)
    search --no-floppy --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
    fi
    fi
    if [ ${recordfail} = 1 ]; then
    set timeout=-1
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###

    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/white
    ### END /etc/grub.d/05_debian_theme ###

    ### BEGIN /etc/grub.d/10_linux ###
    menuentry "Ubuntu, Linux 2.6.31-13-generic" {
    recordfail=1
    save_env recordfail
    set quiet=1
    insmod ext2
    set root=(hd0,6)
    search --no-floppy --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    linux /boot/vmlinuz-2.6.31-13-generic root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro quiet splash
    initrd /boot/initrd.img-2.6.31-13-generic
    }
    menuentry "Ubuntu, Linux 2.6.31-13-generic (recovery mode)" {
    recordfail=1
    save_env recordfail
    insmod ext2
    set root=(hd0,6)
    search --no-floppy --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    linux /boot/vmlinuz-2.6.31-13-generic root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro single
    initrd /boot/initrd.img-2.6.31-13-generic
    }
    menuentry "Ubuntu, Linux 2.6.28-15-generic" {
    recordfail=1
    save_env recordfail
    set quiet=1
    insmod ext2
    set root=(hd0,6)
    search --no-floppy --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    linux /boot/vmlinuz-2.6.28-15-generic root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro quiet splash
    initrd /boot/initrd.img-2.6.28-15-generic
    }
    menuentry "Ubuntu, Linux 2.6.28-15-generic (recovery mode)" {
    recordfail=1
    save_env recordfail
    insmod ext2
    set root=(hd0,6)
    search --no-floppy --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    linux /boot/vmlinuz-2.6.28-15-generic root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro single
    initrd /boot/initrd.img-2.6.28-15-generic
    }
    ### END /etc/grub.d/10_linux ###

    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    linux16 /boot/memtest86+.bin
    }
    menuentry "Memory test (memtest86+, serial console 115200)" {
    linux16 /boot/memtest86+.bin console=ttyS0,115200n8
    }
    ### END /etc/grub.d/20_memtest86+ ###

    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Windows Vista (loader) (on /dev/sda2)" {
    insmod ntfs
    set root=(hd0,2)
    search --no-floppy --fs-uuid --set e8bc3d20bc3ceb28
    chainloader +1
    }
    menuentry "Windows Vista (loader) (on /dev/sda3)" {
    insmod ntfs
    set root=(hd0,3)
    search --no-floppy --fs-uuid --set d8b26317b262fa00
    chainloader +1
    }
    ### END /etc/grub.d/30_os-prober ###

    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###

  3. #13
    Join Date
    Aug 2008
    Location
    South East Montana
    Beans
    6,153

    Re: Kernel Issues from the upgrade

    Oh boy, that looks really good.

    Now, there has been some problem with booting and the complete menuentry generated by 10_linux.

    If this happens to you, you will need to get back to your menu and hit e. Edit the first to lines;
    Code:
    recordfail=1
            save_env recordfail
    out. That should do it.

    If you want to have an entry that will never need to change you could do this with the Ubuntu entry in your /etc/grub.d/40_custom file;
    Code:
    echo "Adding Ubuntu9.10 on sda6" >&2
    cat << EOF
    menuentry "Ubuntu9.10 on sda6" {
            set root=(hd0,6)
            linux /vmlinuz root=/dev/sda6 so quiet splash
            initrd /initrd.img
    }
    EOF
    You need to check the drive numbers to make sure I got them right. Drop that into the 40_custom file and I would save it as 06_custom. This will put that entry at the top of the menu you see on the screen. If you leave it as 40 it will be at the bottom.

    The stuff between the " " is what you see for the title.

    The stuff between the { } is what you boot from.

    Note that this entry just refers to the partition and basically says boot anything found there.

    You can put your entries for Win Jerry Lewis Pro in that file the same way, add your title between the " " and cut and paste the working part of you entry between the { }.

    You need to go to preferences on your editor (I used gedit or screem) and make sure that text wrapping is NOT enabled.

    The { }s need to be exactly where they are above. Well every thing needs to be that way or it just won't work.

    The Ubuntu title you may want to change too. That will never need to be updated for kernels or anything else.

    If you put that in you need to run "sudo update-grub" to write it to the /boot/grub/grub.cfg file.

    Reboot. Try the 10_linux generated entry first. Hopefully it works. That way you will know you can get to the recovery mode. I would reboot again and try the custom entry (if any).

    Then I would go and just remove (synaptic is your friend) the Jaunty kernels. This will run update-grub and remove them from the menu.

    It would be great if you would post back your grub.cfg file no matter what the out come. Note that I am assuming success.
    Dell 480 XPS 3G ram Quad Core 2.40GHz, Radeon HD 2400 PRO, Audigy1, 3x320G HDD, 320G External, Debian Testing for use, Debian Squeeze for secure use, Debian Sid for FUN

  4. #14
    Join Date
    Aug 2009
    Beans
    20

    Re: Kernel Issues from the upgrade

    Quote Originally Posted by ranch hand View Post
    Oh boy, that looks really good.

    Now, there has been some problem with booting and the complete menuentry generated by 10_linux.

    If this happens to you, you will need to get back to your menu and hit e. Edit the first to lines;
    Code:
    recordfail=1
            save_env recordfail
    out. That should do it.

    If you want to have an entry that will never need to change you could do this with the Ubuntu entry in your /etc/grub.d/40_custom file;
    Code:
    echo "Adding Ubuntu9.10 on sda6" >&2
    cat << EOF
    menuentry "Ubuntu9.10 on sda6" {
            set root=(hd0,6)
            linux /vmlinuz root=/dev/sda6 so quiet splash
            initrd /initrd.img
    }
    EOF
    You need to check the drive numbers to make sure I got them right. Drop that into the 40_custom file and I would save it as 06_custom. This will put that entry at the top of the menu you see on the screen. If you leave it as 40 it will be at the bottom.

    The stuff between the " " is what you see for the title.

    The stuff between the { } is what you boot from.

    Note that this entry just refers to the partition and basically says boot anything found there.

    You can put your entries for Win Jerry Lewis Pro in that file the same way, add your title between the " " and cut and paste the working part of you entry between the { }.

    You need to go to preferences on your editor (I used gedit or screem) and make sure that text wrapping is NOT enabled.

    The { }s need to be exactly where they are above. Well every thing needs to be that way or it just won't work.

    The Ubuntu title you may want to change too. That will never need to be updated for kernels or anything else.

    If you put that in you need to run "sudo update-grub" to write it to the /boot/grub/grub.cfg file.

    Reboot. Try the 10_linux generated entry first. Hopefully it works. That way you will know you can get to the recovery mode. I would reboot again and try the custom entry (if any).

    Then I would go and just remove (synaptic is your friend) the Jaunty kernels. This will run update-grub and remove them from the menu.

    It would be great if you would post back your grub.cfg file no matter what the out come. Note that I am assuming success.
    Thanks alot! It worked fine the first time!

  5. #15
    Join Date
    Aug 2008
    Location
    South East Montana
    Beans
    6,153

    Re: Kernel Issues from the upgrade

    Better mark this as Solved then (top of page under Thread Tools).

    Glad it worked. I think that grub2 is going to be great if it ever gets out of beta.
    Dell 480 XPS 3G ram Quad Core 2.40GHz, Radeon HD 2400 PRO, Audigy1, 3x320G HDD, 320G External, Debian Testing for use, Debian Squeeze for secure use, Debian Sid for FUN

  6. #16
    Join Date
    Apr 2008
    Beans
    10,635

    Re: Kernel Issues from the upgrade

    Quote Originally Posted by ranch hand View Post
    Better mark this as Solved then (top of page under Thread Tools).

    Glad it worked. I think that grub2 is going to be great if it ever gets out of beta.
    Good job ranch hand! Thought I'd share something just as an "FYI" regarding mixed legacy-grub and grub2 files in the same grub directory.

    Of course my /boot directory is modified from playing with changing from legacy-grub to grub2 and vice versa, but note the commands in bold red, you'll notice in blue that /boot has three grub directories (two of which I renamed), and my current /boot/grub is a legacy-grub whereas /boot/grub_backup is a typical grub2:

    lance@lance-desktop:~$ ls ~ /boot
    /boot:
    abi-2.6.31-11-generic initrd.img-2.6.31-13-generic
    abi-2.6.31-12-generic memtest86+.bin
    abi-2.6.31-13-generic System.map-2.6.31-11-generic
    config-2.6.31-11-generic System.map-2.6.31-12-generic
    config-2.6.31-12-generic System.map-2.6.31-13-generic
    config-2.6.31-13-generic vmcoreinfo-2.6.31-11-generic
    grub vmcoreinfo-2.6.31-12-generic
    grub_backup vmcoreinfo-2.6.31-13-generic
    grub_legacy vmlinuz-2.6.31-11-generic

    initrd.img-2.6.31-11-generic vmlinuz-2.6.31-12-generic
    initrd.img-2.6.31-12-generic vmlinuz-2.6.31-13-generic

    /home/lance:
    Desktop Downloads Music Projects reward.ps Ubuntu One
    Documents examples.desktop Pictures Public Templates Videos
    lance@lance-desktop:~$ ls ~ /boot/grub
    /boot/grub:
    default grubenv menu.lst~ splashimages
    device.map installed-version menu.lst.backup stage1
    e2fs_stage1_5 jfs_stage1_5 minix_stage1_5 stage2
    fat_stage1_5 menu.lst reiserfs_stage1_5 xfs_stage1_5

    /home/lance:
    Desktop Downloads Music Projects reward.ps Ubuntu One
    Documents examples.desktop Pictures Public Templates Videos
    lance@lance-desktop:~$ ls ~ /boot/grub_backup
    /boot/grub_backup:
    915resolution.mod efiemu64.o lspci.mod reboot.mod
    acpi.mod efiemu.mod lua.mod reiserfs.mod
    affs.mod elf.mod lvm.mod scsi.mod
    afs_be.mod ext2.mod mdraid.mod search.mod
    afs.mod extcmd.mod memdisk.mod serial.mod
    aout.mod fat.mod memrw.mod setjmp.mod
    ata.mod font.mod minicmd.mod sfs.mod
    ata_pthru.mod fs_file.mod minix.mod sh.mod
    at_keyboard.mod fshelp.mod mmap.mod sleep.mod
    befs_be.mod fs.lst moddep.lst tar.mod
    befs.mod fs_uuid.mod msdospart.mod terminfo.mod
    biosdisk.mod gfxterm.mod multiboot.mod test.mod
    bitmap.mod gptsync.mod normal.mod tga.mod
    blocklist.mod grub.cfg ntfscomp.mod true.mod
    boot.img grubenv ntfs.mod udf.mod
    boot.mod gzio.mod ohci.mod ufs1.mod
    bsd.mod halt.mod part_acorn.mod ufs2.mod
    bufio.mod handler.lst part_amiga.mod uhci.mod
    cat.mod handler.mod part_apple.mod usb_keyboard.mod
    cdboot.img hdparm.mod part_gpt.mod usb.mod
    chain.mod hello.mod partmap.lst usbms.mod
    cmp.mod help.mod part_msdos.mod usbtest.mod
    command.lst hexdump.mod part_sun.mod vbeinfo.mod
    configfile.mod hfs.mod parttool.lst vbe.mod
    core.img hfsplus.mod parttool.mod vbetest.mod
    cpio.mod iso9660.mod password.mod vga.mod
    cpuid.mod jfs.mod pci.mod vga_text.mod
    crc.mod jpeg.mod play.mod video_fb.mod
    datehook.mod kernel.img png.mod video.mod
    date.mod keystatus.mod probe.mod videotest.mod
    datetime.mod linux16.mod pxeboot.img xfs.mod
    device.map linux.mod pxecmd.mod xnu.mod
    diskboot.img lnxboot.img pxe.mod xnu_uuid.mod
    dm_nv.mod loadenv.mod raid5rec.mod zfsinfo.mod
    drivemap.mod loopback.mod raid6rec.mod zfs.mod
    echo.mod lsmmap.mod raid.mod
    efiemu32.o ls.mod read.mod

    /home/lance:
    Desktop Downloads Music Projects reward.ps Ubuntu One
    Documents examples.desktop Pictures Public Templates Videos
    Never mind the old /boot/grub_legacy it's just an older legacy-grub leftover from playing around, and I don't have a "mixed" legacy-grub and grub2 /boot/grub to display right now, but from that output (given your knowledge) it's fairly easy to see if you're dealing with a "mixed" /boot/grub directory.

    I've found that such a "mixed" directory can result in strange "grub" behavior (like breakage), whether it's legacy-grub or grub2, especially following distribution updates to grub, grub-common, or grub-pc.

    Of course I'm as new to this as everyone else, but thought you and others might want to put the ls ~ command to good use.

    Just another tool to use

  7. #17
    Join Date
    Aug 2008
    Location
    South East Montana
    Beans
    6,153

    Re: Kernel Issues from the upgrade

    That is really cool. Wow, I have got to try that.

    I put a link to that post on the Grub2 Introduction page.
    Last edited by ranch hand; October 13th, 2009 at 10:19 PM.
    Dell 480 XPS 3G ram Quad Core 2.40GHz, Radeon HD 2400 PRO, Audigy1, 3x320G HDD, 320G External, Debian Testing for use, Debian Squeeze for secure use, Debian Sid for FUN

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

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