Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Kernel Issues from the upgrade

  1. #1
    Join Date
    Aug 2009
    Beans
    20

    Kernel Issues from the upgrade

    When I first upgraded to 9.10 from 9.04 I had no idea why I lost support for audio, my trackpad, and graphics intensives like compiz fusion. I then realized that it was because Grub 2 was booting with kernel 2.6.28-15 and not 2.6.31-15.

    When I edited the parameters in Grub 2 to the new kernel everything was running fine. But then when I tried editing /boot/grub/menu.lst from 2.28 to 2.31 and saved it, restarted...It still booted in to 2.28

    I've tried using update-grub and that didn't help anything. I logged in to root and tried physically removing all the 2.28 files from /boot and the only thing that did was make it so I can't boot up at all without first editing the boot parameters to boot from 2.31.

    Any help/suggestions?

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

    Re: Kernel Issues from the upgrade

    Well that is confusing.

    Let us see, you changed something in grub2 and you edited the /boot/grub/menu.lst.

    Ah, the source of the confusion is that in grub2 there is no /boot/grub/menu.lst.

    So what is going on?
    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

  3. #3
    Join Date
    Jul 2005
    Location
    England
    Beans
    13,577

    Re: Kernel Issues from the upgrade

    I recall reading about this problem of the grub change to grub2 elsewhere in the forum. It seems that a distro upgrade from 9.04 with legacy grub, to 9.10 with grub2 can cause the system a bit of a headache. Maybe you need to consider a separate /boot partition, or something similar, but how you can add that to an existing OS, I am afraid I don't know.

  4. #4
    Join Date
    Oct 2009
    Location
    Go north!
    Beans
    84

    Re: Kernel Issues from the upgrade

    Quote Originally Posted by megaman2000 View Post
    When I first upgraded to 9.10 from 9.04 I had no idea why I lost support for audio, my trackpad, and graphics intensives like compiz fusion. I then realized that it was because Grub 2 was booting with kernel 2.6.28-15 and not 2.6.31-15.

    When I edited the parameters in Grub 2 to the new kernel everything was running fine. But then when I tried editing /boot/grub/menu.lst from 2.28 to 2.31 and saved it, restarted...It still booted in to 2.28

    I've tried using update-grub and that didn't help anything. I logged in to root and tried physically removing all the 2.28 files from /boot and the only thing that did was make it so I can't boot up at all without first editing the boot parameters to boot from 2.31.

    Any help/suggestions?
    Before you Borked it by removal of items, you likely needed to choose the kernel you wanted to boot either manually or by making it the first (default) option. See you after the re-install ! <g>.
    rippin

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

    Re: Kernel Issues from the upgrade

    You are also going to have trouble booting intl 2.6.31-15, at least I think so.
    Code:
    krap@krap-desktop:~$ uname -a
    Linux krap-desktop 2.6.31-13-generic #44-Ubuntu SMP Sat Oct 10 15:27:14 UTC 2009 x86_64 GNU/Linux
    All of my 9.10 installs are running on that except for one that I have left on 31-12 just in case of problems.
    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. #6
    Join Date
    Aug 2009
    Beans
    20

    Re: Kernel Issues from the upgrade

    Quote Originally Posted by rippin View Post
    Before you Borked it by removal of items, you likely needed to choose the kernel you wanted to boot either manually or by making it the first (default) option. See you after the re-install ! <g>.
    I saved all the old kernel files to a folder on the desktop. If I replace them have I averted borking, or is it too late?

  7. #7
    Join Date
    Oct 2009
    Location
    Go north!
    Beans
    84

    Re: Kernel Issues from the upgrade

    Quote Originally Posted by megaman2000 View Post
    I saved all the old kernel files to a folder on the desktop. If I replace them have I averted borking, or is it too late?
    Good on you! You smartly saved your rear With the right permissions, you can likely bail yourself out. Can you post your menu.1st?
    rippin

  8. #8
    Join Date
    Aug 2009
    Beans
    20

    Re: Kernel Issues from the upgrade

    Quote Originally Posted by rippin View Post
    Good on you! You smartly saved your rear With the right permissions, you can likely bail yourself out. Can you post your menu.1st?
    Did you mean menu.lst? that's the only one I can find :l

    # menu.lst - See: grub(8), info grub, update-grub(8)
    # grub-install(8), grub-floppy(8),
    # grub-md5-crypt, /usr/share/doc/grub
    # and /usr/share/doc/grub-doc/.

    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default 0

    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout 10

    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    #hiddenmenu

    # Pretty colours
    #color cyan/blue white/blue

    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret

    #
    # examples
    #
    # title Windows 95/98/NT/2000
    # root (hd0,0)
    # makeactive
    # chainloader +1
    #
    # title Linux
    # root (hd0,1)
    # kernel /vmlinuz root=/dev/hda2 ro
    #

    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below

    ## DO NOT UNCOMMENT THEM, Just edit them to your needs

    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ## kopt_2_6_8=root=/dev/hdc1 ro
    ## kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro

    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=463ec3fe-d467-4213-84d4-c46c2a79072d

    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ## alternative=false
    # alternative=true

    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ## lockalternative=false
    # lockalternative=false

    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash

    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ## lockold=true
    # lockold=false

    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=

    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0

    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ## altoptions=(recovery) single
    # altoptions=(recovery mode) single

    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ## howmany=7
    # howmany=all

    ## specify if running in Xen domU or have grub detect automatically
    ## update-grub will ignore non-xen kernels when running in domU and vice versa
    ## e.g. indomU=detect
    ## indomU=true
    ## indomU=false
    # indomU=detect

    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ## memtest86=false
    # memtest86=true

    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false

    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false

    ## ## End Default Options ##

    title Ubuntu karmic (development branch), kernel 2.6.31-13-generic
    uuid 463ec3fe-d467-4213-84d4-c46c2a79072d
    kernel /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
    quiet

    title Ubuntu karmic (development branch), kernel 2.6.31-13-generic (recovery mode)
    uuid 463ec3fe-d467-4213-84d4-c46c2a79072d
    kernel /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

    title Ubuntu karmic (development branch), kernel 2.6.28-15-generic
    uuid 463ec3fe-d467-4213-84d4-c46c2a79072d
    kernel /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
    quiet

    title Ubuntu karmic (development branch), kernel 2.6.28-15-generic (recovery mode)
    uuid 463ec3fe-d467-4213-84d4-c46c2a79072d
    kernel /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

    title Chainload into GRUB 2
    root 463ec3fe-d467-4213-84d4-c46c2a79072d
    kernel /boot/grub/core.img

    title Ubuntu karmic (development branch), memtest86+
    uuid 463ec3fe-d467-4213-84d4-c46c2a79072d
    kernel /boot/memtest86+.bin
    quiet

    ### END DEBIAN AUTOMAGIC KERNELS LIST

    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title Other operating systems:
    root


    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda2
    title Windows Vista (loader)
    rootnoverify (hd0,1)
    savedefault
    makeactive
    chainloader +1


    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sda3
    title Windows Vista (loader)
    rootnoverify (hd0,2)
    savedefault
    makeactive
    chainloader +1
    Last edited by megaman2000; October 12th, 2009 at 11:57 PM.

  9. #9
    Join Date
    Apr 2008
    Location
    Southern California, USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Kernel Issues from the upgrade

    Your going to have to output your grub2 menu. Found at "/boot/grub/grub.cfg", so we can see what's what and where its booting from.
    boot_info_script | AMD64 Athlon X2 Dual-Core - nVidia Geforce 6150 SE - 4GB DDR3

  10. #10
    Join Date
    Aug 2009
    Beans
    20

    Re: Kernel Issues from the upgrade

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

    ### BEGIN /etc/grub.d/00_header ###
    set default=0
    set timeout=5
    set root=(hd0,6)
    search --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    if font /usr/share/grub/ascii.pff ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    terminal gfxterm
    fi
    ### END /etc/grub.d/00_header ###

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

    ### BEGIN /etc/grub.d/10_hurd ###
    ### END /etc/grub.d/10_hurd ###

    ### BEGIN /etc/grub.d/10_linux ###
    set root=(hd0,6)
    search --fs-uuid --set 463ec3fe-d467-4213-84d4-c46c2a79072d
    menuentry "Ubuntu, linux 2.6.28-15-generic" {
    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 (single-user mode)" {
    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
    }
    menuentry "Ubuntu, linux 2.6.28-11-generic" {
    linux /boot/vmlinuz-2.6.28-11-generic root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro quiet splash
    initrd /boot/initrd.img-2.6.28-11-generic
    }
    menuentry "Ubuntu, linux 2.6.28-11-generic (single-user mode)" {
    linux /boot/vmlinuz-2.6.28-11-generic root=UUID=463ec3fe-d467-4213-84d4-c46c2a79072d ro single
    initrd /boot/initrd.img-2.6.28-11-generic
    }
    ### END /etc/grub.d/10_linux ###

    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    linux /boot/memtest86+.bin
    }
    menuentry "Memory test (memtest86+, serial console 115200)" {
    linux /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)" {
    set root=(hd0,2)
    chainloader +1
    }
    menuentry "Windows Vista (loader) (on /dev/sda3)" {
    set root=(hd0,3)
    chainloader +1
    }
    ### END /etc/grub.d/30_os-prober ###

    ### BEGIN /etc/grub.d/40_custom ###
    # This file is an example on how to add custom entries
    ### END /etc/grub.d/40_custom ###

Page 1 of 2 12 LastLast

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
  •