0

So i have 3.13.0-34 & 3.13.0-33 & 3.13.0-24 all installed but the system constantly sticks with 3.13.0-24.

update-grub does not seem to change this. grub configuration says boot entry 0. I'm at a bit of a loss what to do next but want to keep my kernel updated when I do a dist-upgrade, currently it installs the newer kernel packages but never uses anything but 3.13.0-24.

The output of uname -a.

$ uname -a
Linux <hostname> 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

The contents of /boot.

$ ls /boot
abi-3.13.0-24-generic         memtest86+.bin
abi-3.13.0-33-generic         memtest86+.elf
abi-3.13.0-34-generic         memtest86+_multiboot.bin
config-3.13.0-24-generic      System.map-3.13.0-24-generic
config-3.13.0-33-generic      System.map-3.13.0-33-generic
config-3.13.0-34-generic      System.map-3.13.0-34-generic
grub                          vmlinuz-3.13.0-24-generic
initrd.img-3.13.0-24-generic  vmlinuz-3.13.0-33-generic
initrd.img-3.13.0-33-generic  vmlinuz-3.13.0-34-generic
initrd.img-3.13.0-34-generic

Here is the grub.cfg info requested.

$ grep Ubuntu /boot/grub/grub.cfg
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
        menuentry 'Ubuntu, with Linux 3.13.0-34-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-34-generic-advanced-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
        menuentry 'Ubuntu, with Linux 3.13.0-34-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-34-generic-recovery-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
        menuentry 'Ubuntu, with Linux 3.13.0-33-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-33-generic-advanced-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
        menuentry 'Ubuntu, with Linux 3.13.0-33-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-33-generic-recovery-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
        menuentry 'Ubuntu, with Linux 3.13.0-24-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-24-generic-advanced-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {
        menuentry 'Ubuntu, with Linux 3.13.0-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.13.0-24-generic-recovery-050e1e34-39e6-4072-a03e-ae0bf90ba13a' {

and the output of "sudo update-grub".

$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-34-generic
Found initrd image: /boot/initrd.img-3.13.0-34-generic
Found linux image: /boot/vmlinuz-3.13.0-33-generic
Found initrd image: /boot/initrd.img-3.13.0-33-generic
Found linux image: /boot/vmlinuz-3.13.0-24-generic
Found initrd image: /boot/initrd.img-3.13.0-24-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin 
done
Improve this question
10
  • Can you confirm that all three versions are present in the output of grep Ubuntu /boot/grub/grub.cfg?
    – Oli ♦
    Aug 18, 2014 at 10:19
  • Added requested output to the question because the comment mangled the output.
    – Kurgol
    Aug 18, 2014 at 10:28
  • possible duplicate of my question: I solved this, just read my comment here
    – αғsнιη
    Aug 18, 2014 at 10:40
  • That's great. Unfortunately (for the purposes of diagnostics) that all looks normal. Two more ideas though. Are you sure you've done a proper reboot since installing those? A lot of people hibernate without thinking about it and some things (like the crashkernel setup) hotwire the reboot sequence so you never get back to grub. Do a proper shutdown, power off and start up. Failing that, what happens if you manually select the latest version at the grub screen (hold left shift while booting)?
    – Oli ♦
    Aug 18, 2014 at 10:42
  • 1
    What about manual interactive selection?
    – Oli ♦
    Aug 18, 2014 at 10:48

1 Answer 1

Reset to default
1

It turns out that the hosting company I use (Digital Ocean) have a control panel through their website that allows you to set the kernel. It also appears that their site does not in any way respect the OS choices made about which kernel the system will boot.

Resolved by choosing kernel through their control panel. This is only affecting my droplets on their service, not live local machines (tested and confirmed).

According to https://www.digitalocean.com/community/tutorials/how-to-update-a-digitalocean-server-s-kernel this applies only to "old" droplets (I don't know how old :-)). That page also shows the steps to make those droplets respect the OS selected kernel.

Improve this answer
0

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .