Announcement

**vinnywright** · Mar 14, 2010, 05:43 PM

Re: kernel update problems

try

Code:

sudo update-grub

it should be run as part of the install prosess of a new kernel but if not do it your self.

but first check /boot and make shure you have initrd.img for eatch kernel as hear

initrd.img-2.6.31-16-generic vmlinuz-2.6.31-16-generic
initrd.img-2.6.31-17-generic vmlinuz-2.6.31-17-generic
initrd.img-2.6.31-19-generic vmlinuz-2.6.31-19-generic
initrd.img-2.6.31-20-generic vmlinuz-2.6.31-20-generic

VINNY

**sisqonrw** · Mar 14, 2010, 05:49 PM

Re: kernel update problems

in /boot i have:

initrd.img-2.6.31-15-generic
initrd.img-2.6.31-16-generic
initrd.img-2.6.31-17-generic
initrd.img-2.6.31-19-generic
initrd.img-2.6.31-20-generic

and get this:

Code:

sudo update-grub
[sudo] password for salsero:
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-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.31-15-generic
Found kernel: /memtest86+.bin
Updating /boot/grub/menu.lst ... done

**vinnywright** · Mar 14, 2010, 05:55 PM

Re: kernel update problems

ok so reboot and see if thay are thare!!

VINNY

**aqeeliz** · Mar 15, 2010, 01:31 AM

Re: kernel update problems

Same thing here, if I recall correctly, it started happening after I upgraded to karmic. When I run

Code:

$ sudo update-grub

I get output similar to sisqonrw's but it doesn't actually update my menu.lst.

I just update my menu.lst by hand now, copy the previous entries and change the version number to new kernel. (Not the best solution, but as kernel updates aren't very common I wasn't really bothered to search for solution)

**sisqonrw** · Mar 15, 2010, 03:27 AM

Re: kernel update problems

Hi aqeeliz,

i do not want to make a misstake. here my menu.lst

Code:

splashimage (hd0,6)/grub/splashimages/105103-dark-air.xpm.gz
default 0
timeout 10

### 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=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,6)

## 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 9.10, kernel 2.6.31-16-generic
root (hd0,6)
kernel /vmlinuz-2.6.31-16-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro quiet splash
initrd /initrd.img-2.6.31-16-generic

title Ubuntu 9.10, kernel 2.6.31-16-generic (recovery mode)
root (hd0,6)
kernel /vmlinuz-2.6.31-16-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro single
initrd /initrd.img-2.6.31-16-generic

title Ubuntu 9.10, kernel 2.6.31-15-generic
root (hd0,6)
kernel /vmlinuz-2.6.31-15-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro quiet splash
initrd /initrd.img-2.6.31-15-generic

title Ubuntu 9.10, kernel 2.6.31-15-generic (recovery mode)
root (hd0,6)
kernel /vmlinuz-2.6.31-15-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro single
initrd /initrd.img-2.6.31-15-generic

title Ubuntu 9.10, memtest86+
root (hd0,6)
kernel /memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

title Other operating systems:
root

title Windows Vista/Longhorn (loader)
root (hd0,1)
chainloader +1
savedefault
makeactive

can you edit for me, please?

**dibl** · Mar 15, 2010, 04:19 AM

Re: kernel update problems

Originally posted by sisqonrw

i am using Karmic KDE 4.3.2

There's something missing from your story. 9.10 comes with Grub 2, which does not use a /boot/grub/menu.lst file. How did you manage to install legacy grub? Was this system updated from 9.04? Or did you use a utility of some kind to install a boot menu?

**dibl** · Mar 15, 2010, 04:25 AM

Re: kernel update problems

Originally posted by sisqonrw

splashimage (hd0,6)/grub/splashimages/105103-dark-air.xpm.gz
default 0
timeout 10

### 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=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,6)

## 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 9.10, kernel 2.6.31-20-generic
root (hd0,6)
kernel /vmlinuz-2.6.31-20-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro quiet splash
initrd /initrd.img-2.6.31-20-generic

title Ubuntu 9.10, kernel 2.6.31-20-generic (recovery mode)
root (hd0,6)
kernel /vmlinuz-2.6.31-20-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro single
initrd /initrd.img-2.6.31-20-generic

title Ubuntu 9.10, kernel 2.6.31-15-generic
root (hd0,6)
kernel /vmlinuz-2.6.31-15-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro quiet splash
initrd /initrd.img-2.6.31-15-generic

title Ubuntu 9.10, kernel 2.6.31-15-generic (recovery mode)
root (hd0,6)
kernel /vmlinuz-2.6.31-15-generic root=UUID=f154c0b9-aa26-42c0-bcfd-48eaba892706 ro single
initrd /initrd.img-2.6.31-15-generic

title Ubuntu 9.10, memtest86+
root (hd0,6)
kernel /memtest86+.bin

### END DEBIAN AUTOMAGIC KERNELS LIST

title Other operating systems:
root

title Windows Vista/Longhorn (loader)
root (hd0,1)
chainloader +1
savedefault
makeactive

These edits will let you boot the new kernel.

But, there is something wrong with your system if sudo update-grub is not updating it -- I'm not sure about your configuration since you seem to have some part of legacy grub on a 9.10 system which normally installs Grub 2.

**sisqonrw** · Mar 15, 2010, 04:26 AM

Re: kernel update problems

on my system is following installed, see attatchmend

Attached Files

**dibl** · Mar 15, 2010, 04:33 AM

Re: kernel update problems

If your only concern is to boot the new kernel, the edit I showed above should take care of that.

**sisqonrw** · Mar 15, 2010, 05:13 AM

Re: kernel update problems

so i should edit the 6 position. what about the UUID?
is it riskly to edit the 6 positon? will it work without any problems?

**aqeeliz** · Mar 15, 2010, 09:09 AM

Re: kernel update problems

Originally posted by sisqonrw

so i should edit the 6 position. what about the UUID?
is it riskly to edit the 6 positon? will it work without any problems?

You don't need to change anything else. UUID is the address of your root (/) partition, it remains the same.
There is always a risk when editing system files, but if you just edit those 6 positions it will work fine. It is still recommended to make backup of any system file you edit.

Announcement

kernel update problems

kernel update problems

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment