Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 23

Thread: Possible menu.lst problem after kernel update

  1. #11
    Join Date
    Nov 2009
    Location
    Segur De Calafell, Spain
    Beans
    11,660
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Possible menu.lst problem after kernel update

    As long as you are booting from /dev/sda in bios, no change is needed because the last command will install grub2 to /dev/sda.

    As for the grub1 question, I'm not sure since I don't know it that much in detail. If I remember correctly, I think in the menu that popped up you needed to select 1. Maintainer's version and that should keep it up to date.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 12.04 LTS 64bit & Windows 7 Ultimate 64bit

  2. #12
    Join Date
    Aug 2007
    Beans
    244

    Re: Possible menu.lst problem after kernel update

    Just for further info running sudo update-grub gives,

    Code:
    Searching for GRUB installation directory ... found: /boot/grub
    Searching for default file ... found: /boot/grub/default
    Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
    Searching for splash image ... none found, skipping ...
    Found kernel: /vmlinuz-3.2.0-32-generic
    Found kernel: /vmlinuz-3.2.0-31-generic
    Found kernel: /vmlinuz-3.2.0-30-generic
    Found kernel: /vmlinuz-2.6.32-42-generic
    Found kernel: /vmlinuz-2.6.31-22-generic
    Found kernel: /vmlinuz-2.6.31-21-generic
    Found kernel: /vmlinuz-2.6.31-20-generic
    Found kernel: /vmlinuz-2.6.31-19-generic
    Found kernel: /vmlinuz-2.6.31-17-generic
    Found kernel: /vmlinuz-2.6.31-16-generic
    Found kernel: /vmlinuz-2.6.28-17-generic
    Found kernel: /vmlinuz-2.6.27-11-generic
    Found kernel: /memtest86+.bin
    Updating /boot/grub/menu.lst ... done
    Here is my menu.lst file after running sudo update-grub today, notice how the 3.2.31 and 3.2.32 kernels don't show up in menu.lst.

    Any answers as to why this would happen?


    Code:
    # 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        3
    
    ## 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=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    
    ## 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 12.04.1 LTS, kernel 3.2.0-30-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-3.2.0-30-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-3.2.0-30-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 3.2.0-30-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-3.2.0-30-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-3.2.0-30-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.32-42-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.32-42-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.32-42-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.32-42-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.32-42-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.32-42-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-22-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-22-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.31-22-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-22-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-22-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.31-22-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-21-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-21-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.31-21-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-21-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-21-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.31-21-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-20-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-20-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.31-20-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-20-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-20-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.31-20-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-19-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-19-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.31-19-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-19-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-19-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.31-19-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-17-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-17-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.31-17-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-17-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-17-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.31-17-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-16-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-16-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.31-16-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.31-16-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.31-16-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.31-16-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.28-17-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.28-17-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.28-17-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.28-17-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.28-17-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.28-17-generic
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.27-11-generic
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.27-11-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa quiet splash 
    initrd        /initrd.img-2.6.27-11-generic
    quiet
    
    title        Ubuntu 12.04.1 LTS, kernel 2.6.27-11-generic (recovery mode)
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /vmlinuz-2.6.27-11-generic root=UUID=1bc7dbda-9973-48d1-9c8e-21133aec5885 ro xforcevesa  single
    initrd        /initrd.img-2.6.27-11-generic
    
    title        Ubuntu 12.04.1 LTS, memtest86+
    uuid        f161f9cb-e2c7-4a05-9bb8-4f4b51025df1
    kernel        /memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    Last edited by oldfred; October 15th, 2012 at 03:11 PM. Reason: Added code tags (# in edit menu)

  3. #13
    Join Date
    Aug 2007
    Beans
    244

    Re: Possible menu.lst problem after kernel update

    Thaks Darkod, I thought that may be the case, unfortunately the question didn't come up abain when I updated the kernels.

    Does anyone know how I can change the setting to use maintainer's version.

    That was the only time I had ever been asked a question while updating a kernel.

    Thanks.

  4. #14
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Possible menu.lst problem after kernel update

    Please use code tags, highlight like a copy & click the # in edit panel to automatically add them.

    Boot-Repair also has a function to purge & reinstall grub2.

    Boot Repair -Also handles LVM, GPT, separate /boot and UEFI dual boot.:
    https://help.ubuntu.com/community/Boot-Repair
    You can repair many boot issues with this or 'Create BootInfo' report (Other Options) & post the link it creates, so we can see your exact configuration and diagnose advanced problems.


    Over the years I have gotten the system maintainers question on various configuration files. It is a real problem as if you say yes you lose all your custom settings. But your settings may not be required in the new version. If you say no, you save your settings but do not get any new settings and the software may not work correctly with old settings.

    I now just backup separately (copy into /home for regular backup of /home) all the system files in /etc or grub or elsewhere not in /home. Then always accept system maintainers version but realize I may have to manually re-edit. But I have my old version to copy from if needed.
    For info on UEFI boot install & repair:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  5. #15
    Join Date
    Aug 2007
    Beans
    244

    Re: Possible menu.lst problem after kernel update

    Thanks oldfred.

    first my current menu.lst has hidemenu enabled and only a 3 second time to bring it up, if I upgrade to grub2, will this be changed automatically so I can see the options, and will the time limit be increased, Howmany is set to all, could this be a problem for the upgrade considering I have many kernels in menu.lst.


    I've looked at the upgrade page for grub2, and as part of the gui it asks which partitions to put grub in.

    I checked gparted, and on my primary ubuntu drive I have 4 or 5 partitions,

    /dev/sda1 - /boot

    /dev/sda2 - /

    /dev/sda3 /extended

    /dev/sda5 - /home

    /dev/sda4 - /linux-swap

    the boot and grub folders for grub1 are currently in filesystem according to nautilus, so I don't know which partition they're in.

    My other 2 data disks are just 1 partition each, ie /dev/sdb1 and /dev/sdc1

    If the upgrade fails, which is the best version to use for a usb repair disk, the alternative or desktop cds.

    Thanks.

  6. #16
    Join Date
    Nov 2009
    Location
    Segur De Calafell, Spain
    Beans
    11,660
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Possible menu.lst problem after kernel update

    The bootloader always goes to the MBR of the disk which is labeled /dev/sda, without any number in it. The number stands for a partition, and the bootloader is installed on partition only in special situation. The boot process starts from the MBR hence the natural location for the bootloader is there.

    If you have only ubuntu, grub2 menu also doesn't show by default which makes sense since there is no other OS to choose. Why slow down the boot with a menu. You can make the menu show by holding Shift during the boot. Also, you can make it show permanently in the grub2 config files.

    grub2 is much smarter when old kernels are concerned. It combines them in a single submenu called previous Versions. So you can still fidn them there but the grub2 menu is not very long at the same time. There are only entries for the latest kernel, the other are in Previous Versions which makes the menu much more compact.

    In case things go bad, the live cd of 12.04 is the only thing you need to fix it.

    PS. Note that if you are using the mentioned boot-repair tool, I think you have to tick an option that you have separate /boot partition, which you do. You wouldn't need that if you install grub2 from your running system since /boot will be already mounted and the OS is aware of it. Persoanlly, since your computer boots fine right now, I would do it from within ubuntu. You use live mode and boot-repair as last resort, usually when you can't even boot.

    Your computer is bootable, you only need to remove/purge grub1 and install grub2.

    I think boot-repair in live mode gives more options for errors, especially with separate /boot. You're not repairing anything, you are simply switching one bootloader for the other.
    Last edited by darkod; October 15th, 2012 at 04:33 PM.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 12.04 LTS 64bit & Windows 7 Ultimate 64bit

  7. #17
    Join Date
    Aug 2007
    Beans
    244

    Re: Possible menu.lst problem after kernel update

    Thanks alot for the info Darkod.

  8. #18
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Possible menu.lst problem after kernel update

    I think Boot-Repair is just running the same purge & reinstall commands Darko gave back in post #9. Just be sure to have working Internet as once old version is purged you have to download the new version from Ubuntu repository.

    I like to have several repair tools in my tool box. So I always have the current version of Ubuntu liveCD, Knoppix, gparted, Boot-Repair, SuperGrub and often others as I just like to try them. I use grub2 to loopmount the ISO and have them all on one flash drive. I used to burn a lot of CDs when upgrading so I had the current repairCD of everything. Flash drive is a lot easier and saves burning a lot of CDs.
    For info on UEFI boot install & repair:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







  9. #19
    Join Date
    Aug 2007
    Beans
    244

    Re: Possible menu.lst problem after kernel update

    I read carefuly the ubuntu grub2 upgrading page and ran

    sudo apt-get install grub-pc

    This ran and gave the option to upgrade to grub2, I selected ok, it then gave me the option the add chainload to menu.lst, I selected yes, the terminal continued without giving me any other options shown in that upgrade guide, such as import data or which partition to put grub on.

    Here is the output from terminal, I want to know did everything go ok before I reboot?

    TIA

    Code:
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
      fgfs-base libproj0 linux-headers-3.2.0-30 mplayer-nogui libutouch-evemu1
      libutouch-geis1 libutouch-frame1 fgfs-scenery-base libapr1 libogdi3.2
      libcoin60 libpar2-0 libsvn1 libdap11 libgdal1-1.7.0 libpostproc-extra-51
      libgnome-desktop-2-17 fgfs-aircraft-base libepsilon0 libswscale-extra-0
      libxerces-c28 fgfs-models-base libopenthreads14 libhdf5-serial-1.8.4
      libgeos-c1 proj-data libfreexl1 hddtemp libspatialite3 proj-bin
      libutouch-grail1 libgeos-3.2.2 linux-headers-3.2.0-30-generic libhdf4-0-alt
      libaprutil1 simgear2.4.0 libopenscenegraph80 libdapclient3 libnetcdf6
    Use 'apt-get autoremove' to remove them.
    The following extra packages will be installed:
      grub-gfxpayload-lists grub-pc-bin grub2-common
    Suggested packages:
      desktop-base
    The following packages will be REMOVED:
      grub
    The following NEW packages will be installed:
      grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common
    0 upgraded, 4 newly installed, 1 to remove and 0 not upgraded.
    Need to get 1,105 kB of archives.
    After this operation, 396 kB of additional disk space will be used.
    Do you want to continue [Y/n]? y
    Get:1 http://ftp.iinet.net.au/pub/ubuntu/ precise-updates/main grub2-common amd64 1.99-21ubuntu3.4 [94.2 kB]
    Get:2 http://ftp.iinet.net.au/pub/ubuntu/ precise-updates/main grub-pc-bin amd64 1.99-21ubuntu3.4 [867 kB]
    Get:3 http://ftp.iinet.net.au/pub/ubuntu/ precise-updates/main grub-pc amd64 1.99-21ubuntu3.4 [140 kB]
    Get:4 http://ftp.iinet.net.au/pub/ubuntu/ precise/main grub-gfxpayload-lists amd64 0.6 [3,506 B]
    Fetched 1,105 kB in 1s (811 kB/s)                  
    Preconfiguring packages ...
    (Reading database ... 406525 files and directories currently installed.)
    Removing grub ...
    Processing triggers for man-db ...
    Selecting previously unselected package grub2-common.
    (Reading database ... 406480 files and directories currently installed.)
    Unpacking grub2-common (from .../grub2-common_1.99-21ubuntu3.4_amd64.deb) ...
    Selecting previously unselected package grub-pc-bin.
    Unpacking grub-pc-bin (from .../grub-pc-bin_1.99-21ubuntu3.4_amd64.deb) ...
    Selecting previously unselected package grub-pc.
    Unpacking grub-pc (from .../grub-pc_1.99-21ubuntu3.4_amd64.deb) ...
    Selecting previously unselected package grub-gfxpayload-lists.
    Unpacking grub-gfxpayload-lists (from .../grub-gfxpayload-lists_0.6_amd64.deb) ...
    Processing triggers for man-db ...
    Processing triggers for install-info ...
    Setting up grub2-common (1.99-21ubuntu3.4) ...
    Setting up grub-pc-bin (1.99-21ubuntu3.4) ...
    Setting up grub-pc (1.99-21ubuntu3.4) ...
    
    Creating config file /etc/default/grub with new version
    Generating core.img
    Saving menu.lst backup in /boot/grub/menu.lst_backup_by_grub2_postinst
    Running update-grub Legacy to hook our core.img in it
        Searching for GRUB installation directory ... found: /boot/grub
        Searching for default file ... found: /boot/grub/default
        Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
        Searching for splash image ... none found, skipping ...
        Found GRUB 2: /grub/core.img
        Found kernel: /vmlinuz-3.2.0-32-generic
        Found kernel: /vmlinuz-3.2.0-31-generic
        Found kernel: /vmlinuz-3.2.0-30-generic
        Found kernel: /vmlinuz-2.6.32-42-generic
        Found kernel: /vmlinuz-2.6.31-22-generic
        Found kernel: /vmlinuz-2.6.31-21-generic
        Found kernel: /vmlinuz-2.6.31-20-generic
        Found kernel: /vmlinuz-2.6.31-19-generic
        Found kernel: /vmlinuz-2.6.31-17-generic
        Found kernel: /vmlinuz-2.6.31-16-generic
        Found kernel: /vmlinuz-2.6.28-17-generic
        Found kernel: /vmlinuz-2.6.27-11-generic
        Found kernel: /memtest86+.bin
        Updating /boot/grub/menu.lst ... done
        
    Generating grub.cfg ...
    Found linux image: /boot/vmlinuz-3.2.0-32-generic
    Found initrd image: /boot/initrd.img-3.2.0-32-generic
    Found linux image: /boot/vmlinuz-3.2.0-31-generic
    Found initrd image: /boot/initrd.img-3.2.0-31-generic
    Found linux image: /boot/vmlinuz-3.2.0-30-generic
    Found initrd image: /boot/initrd.img-3.2.0-30-generic
    Found linux image: /boot/vmlinuz-2.6.32-42-generic
    Found initrd image: /boot/initrd.img-2.6.32-42-generic
    Found linux image: /boot/vmlinuz-2.6.31-22-generic
    Found initrd image: /boot/initrd.img-2.6.31-22-generic
    Found linux image: /boot/vmlinuz-2.6.31-21-generic
    Found initrd image: /boot/initrd.img-2.6.31-21-generic
    Found linux image: /boot/vmlinuz-2.6.31-20-generic
    Found initrd image: /boot/initrd.img-2.6.31-20-generic
    Found linux image: /boot/vmlinuz-2.6.31-19-generic
    Found initrd image: /boot/initrd.img-2.6.31-19-generic
    Found linux image: /boot/vmlinuz-2.6.31-17-generic
    Found initrd image: /boot/initrd.img-2.6.31-17-generic
    Found linux image: /boot/vmlinuz-2.6.31-16-generic
    Found initrd image: /boot/initrd.img-2.6.31-16-generic
    Found linux image: /boot/vmlinuz-2.6.28-17-generic
    Found initrd image: /boot/initrd.img-2.6.28-17-generic
    Found linux image: /boot/vmlinuz-2.6.27-11-generic
    Found initrd image: /boot/initrd.img-2.6.27-11-generic
    Found memtest86+ image: /memtest86+.bin
    done
    Setting up grub-gfxpayload-lists (0.6) ...
    david@liberator:~$

  10. #20
    Join Date
    Nov 2009
    Location
    Segur De Calafell, Spain
    Beans
    11,660
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Possible menu.lst problem after kernel update

    Yes and no, but if I start writing more you will get confused. So I will just say Yes.

    Reboot and it should work.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 12.04 LTS 64bit & Windows 7 Ultimate 64bit

Page 2 of 3 FirstFirst 123 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
  •