Bug#767836: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Processed: Seems to come from the kernel upgrade)

[Thue Janus Kristensen <thuejk@gmail.com>]

Yes, you are correct, thanks!

Just for other people's reference, it seems that grub settings are ignored on digital ocean, and that you instead have to specify which kernel is booted from the Digital Ocean control panel, loaded from outside the droplet. That doesn't seem like a terribly smart setup to me, since it apparently use the kernel modules installed in the droplet, which obviously can be incompatible with the kernel.

From https://www.digitalocean.com/community/questions/can-t-seem-to-load-fuse-module?comment=17236 :

1) log into the digital ocean control panel

2) go to the droplet that has this issue.

3) go to settings, then kernel

4) change it to the latest kernel. i.e. for me its: * Debian 7.0 x64 vmlinuz-3.2.0-4-amd64 (3.2.60-1+deb7u3)

5) power down your droplet

6) power up.

Regards, Thue

2014-11-03 19:44 GMT+01:00 Ben Hutchings <ben@decadent.org.uk>:

On Mon, 2014-11-03 at 18:13 +0100, Thue Janus Kristensen wrote:
> I did reboot after the kernel upgrade.
>
>
> I just installed the new kernel again, rebooted, and now get the error
> again. This bug seems is not fixed by rebooting after the kernel
> upgrade.

Your boot loader is still loading the old kernel.  That's a problem in
your boot loader configuration, not the new kernel.

Ben.

--
Ben Hutchings
Power corrupts.  Absolute power is kind of neat.
                           - John Lehman, Secretary of the US Navy 1981-1987