15 Jul
2018
15 Jul
'18
2:59 p.m.
Hi Andy,
On 15/07/2018 15:32, Andy Smith wrote:
ian@hobsoni:~$ dpkg -l | grep '^ii.*linux-image'
ii linux-image-4.4.0-112-generic 4.4.0-112.135
amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-116-generic 4.4.0-116.140
amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-130-generic 4.4.0-130.156
amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-virtual 4.4.0.130.136
amd64 This package will always depend on the latest
minimal generic kernel image.
ian@hobsoni:~$
Thanks for your help.
Ian
--
Ian Hobson
Tel (+351) 910 418 473
I assume that it failed to boot the
/boot/vmlinuz-4.4.0-127-generic
entry and you're now running in the /boot/vmlinuz-4.4.0-124-generic
entry?
(uname -a to comfirm)
ian@hobsoni:~$ uname -a
Linux hobsoni 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
ian@hobsoni:~$
So no. 124 also failed to boot, but 116 did.
ian@hobsoni:~$
cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
It's not a problem at all but you might like to comment out the two
lines starting "GRUB_HIDDEN_" so that you do actually get a grub
boot menu.
Don't forget to run "update-grub" after changing this file.
As far as I can see then, the kernel file isn't there for some
reason. Have you checked that /boot/vmlinuz-4.4.0-127-generic is
actually present?
If it's not there, and you run update-grub, does the entry for it in
/boot/grub/grub.cfg go away?
What does:
$ dpkg -l | grep '^ii.*linux-image'