Manual kernel update: System won't boot new kernel
In response to Dirty COW, I installed the 4.4.0-45 kernel as described in the answer to this question.
Output from dpkg -l | grep '4.4.0-45'
ii linux-headers-4.4.0-45 4.4.0-45.66 all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-libc-dev:amd64 4.4.0-45.66 amd64 Linux Kernel Headers for development
clearly shows it is installed and update-grub detects it
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-45-generic
Found initrd image: /boot/initrd.img-4.4.0-45-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
but even after rebooting the machine for the umpteenth time uname -r still gives me
4.2.0-38-generic
I want to know what step I missed that keeps the system from booting the new kernel.
linux ubuntu grub kernel ubuntu-16.04
edited Apr 13 '17 at 12:22
Community♦
1
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
add a comment |
In response to Dirty COW, I installed the 4.4.0-45 kernel as described in the answer to this question.
Output from dpkg -l | grep '4.4.0-45'
ii linux-headers-4.4.0-45 4.4.0-45.66 all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-libc-dev:amd64 4.4.0-45.66 amd64 Linux Kernel Headers for development
clearly shows it is installed and update-grub detects it
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-45-generic
Found initrd image: /boot/initrd.img-4.4.0-45-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
but even after rebooting the machine for the umpteenth time uname -r still gives me
4.2.0-38-generic
I want to know what step I missed that keeps the system from booting the new kernel.
linux ubuntu grub kernel ubuntu-16.04
edited Apr 13 '17 at 12:22
Community♦
1
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
1
Is it listed in the GRUB configuration? Alternatively, what's in the GRUB menu when you start up?
– l0b0
Oct 29 '16 at 10:59
@l0b0 Thanks. It kept the old kernel as default for some reason, and as this is a machine mainly managed using SSH, I didn't notice. But still, even if I reboot withGRUB_DEFAULT='gnulinux-advanced-f0724a95-d885-4cec-b74c-635d61f32c73>gnulinux-4.4.0-45-generic-advanced-f0724a95-d885-4cec-b74c-635d61f32c73'(the name gathered from the grub config file, it still boots into the old kernel.
– FallenWarrior
Oct 29 '16 at 13:45
add a comment |
In response to Dirty COW, I installed the 4.4.0-45 kernel as described in the answer to this question.
Output from dpkg -l | grep '4.4.0-45'
ii linux-headers-4.4.0-45 4.4.0-45.66 all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-libc-dev:amd64 4.4.0-45.66 amd64 Linux Kernel Headers for development
clearly shows it is installed and update-grub detects it
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-45-generic
Found initrd image: /boot/initrd.img-4.4.0-45-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
but even after rebooting the machine for the umpteenth time uname -r still gives me
4.2.0-38-generic
I want to know what step I missed that keeps the system from booting the new kernel.
linux ubuntu grub kernel ubuntu-16.04
edited Apr 13 '17 at 12:22
Community♦
1
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
In response to Dirty COW, I installed the 4.4.0-45 kernel as described in the answer to this question.
Output from dpkg -l | grep '4.4.0-45'
ii linux-headers-4.4.0-45 4.4.0-45.66 all Header files related to Linux kernel version 4.4.0
ii linux-headers-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel headers for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-45-generic 4.4.0-45.66 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-libc-dev:amd64 4.4.0-45.66 amd64 Linux Kernel Headers for development
clearly shows it is installed and update-grub detects it
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-45-generic
Found initrd image: /boot/initrd.img-4.4.0-45-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
done
but even after rebooting the machine for the umpteenth time uname -r still gives me
4.2.0-38-generic
I want to know what step I missed that keeps the system from booting the new kernel.
linux ubuntu grub kernel ubuntu-16.04
linux ubuntu grub kernel ubuntu-16.04
edited Apr 13 '17 at 12:22
Community♦
1
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
edited Apr 13 '17 at 12:22
Community♦
1
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
edited Apr 13 '17 at 12:22
Community♦
1
edited Apr 13 '17 at 12:22
Community♦
1
edited Apr 13 '17 at 12:22
Community♦
1
1
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
asked Oct 29 '16 at 10:57
FallenWarriorFallenWarrior
184
184
1
Is it listed in the GRUB configuration? Alternatively, what's in the GRUB menu when you start up?
– l0b0
Oct 29 '16 at 10:59
@l0b0 Thanks. It kept the old kernel as default for some reason, and as this is a machine mainly managed using SSH, I didn't notice. But still, even if I reboot withGRUB_DEFAULT='gnulinux-advanced-f0724a95-d885-4cec-b74c-635d61f32c73>gnulinux-4.4.0-45-generic-advanced-f0724a95-d885-4cec-b74c-635d61f32c73'(the name gathered from the grub config file, it still boots into the old kernel.
– FallenWarrior
Oct 29 '16 at 13:45
add a comment |
1
Is it listed in the GRUB configuration? Alternatively, what's in the GRUB menu when you start up?
– l0b0
Oct 29 '16 at 10:59
@l0b0 Thanks. It kept the old kernel as default for some reason, and as this is a machine mainly managed using SSH, I didn't notice. But still, even if I reboot withGRUB_DEFAULT='gnulinux-advanced-f0724a95-d885-4cec-b74c-635d61f32c73>gnulinux-4.4.0-45-generic-advanced-f0724a95-d885-4cec-b74c-635d61f32c73'(the name gathered from the grub config file, it still boots into the old kernel.
– FallenWarrior
Oct 29 '16 at 13:45
1
1
Is it listed in the GRUB configuration? Alternatively, what's in the GRUB menu when you start up?
– l0b0
Oct 29 '16 at 10:59
Is it listed in the GRUB configuration? Alternatively, what's in the GRUB menu when you start up?
– l0b0
Oct 29 '16 at 10:59
@l0b0 Thanks. It kept the old kernel as default for some reason, and as this is a machine mainly managed using SSH, I didn't notice. But still, even if I reboot with
GRUB_DEFAULT='gnulinux-advanced-f0724a95-d885-4cec-b74c-635d61f32c73>gnulinux-4.4.0-45-generic-advanced-f0724a95-d885-4cec-b74c-635d61f32c73' (the name gathered from the grub config file, it still boots into the old kernel.– FallenWarrior
Oct 29 '16 at 13:45
@l0b0 Thanks. It kept the old kernel as default for some reason, and as this is a machine mainly managed using SSH, I didn't notice. But still, even if I reboot with
GRUB_DEFAULT='gnulinux-advanced-f0724a95-d885-4cec-b74c-635d61f32c73>gnulinux-4.4.0-45-generic-advanced-f0724a95-d885-4cec-b74c-635d61f32c73' (the name gathered from the grub config file, it still boots into the old kernel.– FallenWarrior
Oct 29 '16 at 13:45
add a comment |
2 Answers
2
active
oldest
votes
You don't need to install a new kernel version to patch the dirty cow vulnerability just enable the Canonical Livepatch Service on your Ubuntu
Kernel live patching enables runtime correction of critical security
issues in your kernel without rebooting. It’s the best way to ensure
that machines are safe at the kernel level, while guaranteeing uptime,
especially for container hosts where a single machine may be running
thousands of different workloads.
(1) Go to https://ubuntu.com/livepatch and retrieve your livepatch
token, for example: d3b07384d213edec49eaa6238ad5ff00
(2) Install the livepatch snap, like this:
$ sudo snap install canonical-livepatch
(3) Enable your account with the token from step 1
$ sudo canonical-livepatch enable d3b07384d113edec49eaa6238ad5ff00
That’s it. You’re up and running! You can check your status at any
time with:
$ canonical-livepatch status
kernel: 4.4.0-38.57-generic
fully-patched: true
version: "12.2"
Now your kernel will remain securely patched, and you can reboot when
it’s convenient for you.
Or by runing the following command:
sudo apt-get update && sudo apt-get dist-upgrade
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
There is something weird happening when I try to enable it. No matter if I use regularsudoor login as root withsudo -ito gain privilege, the enable command fails with "Permission denied" on some file.
– FallenWarrior
Oct 31 '16 at 11:48
As root or allowsudoto execute root commands
– GAD3R
Oct 31 '16 at 11:50
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormallyThis is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.
– FallenWarrior
Nov 1 '16 at 10:07
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
add a comment |
Better is You boot from old kernel
And delete all new kernel files from /boot
Then
update-grub
After it you can set default old kernel
Then
sudo aptitude safe-upgrade
Hope it will help
And if not
Download boot-repair and fix some issue
I like manually but it will risky for new person
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed runupdate-grub)?
– bertieb
Jan 2 at 1:44
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1140204%2fmanual-kernel-update-system-wont-boot-new-kernel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You don't need to install a new kernel version to patch the dirty cow vulnerability just enable the Canonical Livepatch Service on your Ubuntu
Kernel live patching enables runtime correction of critical security
issues in your kernel without rebooting. It’s the best way to ensure
that machines are safe at the kernel level, while guaranteeing uptime,
especially for container hosts where a single machine may be running
thousands of different workloads.
(1) Go to https://ubuntu.com/livepatch and retrieve your livepatch
token, for example: d3b07384d213edec49eaa6238ad5ff00
(2) Install the livepatch snap, like this:
$ sudo snap install canonical-livepatch
(3) Enable your account with the token from step 1
$ sudo canonical-livepatch enable d3b07384d113edec49eaa6238ad5ff00
That’s it. You’re up and running! You can check your status at any
time with:
$ canonical-livepatch status
kernel: 4.4.0-38.57-generic
fully-patched: true
version: "12.2"
Now your kernel will remain securely patched, and you can reboot when
it’s convenient for you.
Or by runing the following command:
sudo apt-get update && sudo apt-get dist-upgrade
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
There is something weird happening when I try to enable it. No matter if I use regularsudoor login as root withsudo -ito gain privilege, the enable command fails with "Permission denied" on some file.
– FallenWarrior
Oct 31 '16 at 11:48
As root or allowsudoto execute root commands
– GAD3R
Oct 31 '16 at 11:50
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormallyThis is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.
– FallenWarrior
Nov 1 '16 at 10:07
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
add a comment |
You don't need to install a new kernel version to patch the dirty cow vulnerability just enable the Canonical Livepatch Service on your Ubuntu
Kernel live patching enables runtime correction of critical security
issues in your kernel without rebooting. It’s the best way to ensure
that machines are safe at the kernel level, while guaranteeing uptime,
especially for container hosts where a single machine may be running
thousands of different workloads.
(1) Go to https://ubuntu.com/livepatch and retrieve your livepatch
token, for example: d3b07384d213edec49eaa6238ad5ff00
(2) Install the livepatch snap, like this:
$ sudo snap install canonical-livepatch
(3) Enable your account with the token from step 1
$ sudo canonical-livepatch enable d3b07384d113edec49eaa6238ad5ff00
That’s it. You’re up and running! You can check your status at any
time with:
$ canonical-livepatch status
kernel: 4.4.0-38.57-generic
fully-patched: true
version: "12.2"
Now your kernel will remain securely patched, and you can reboot when
it’s convenient for you.
Or by runing the following command:
sudo apt-get update && sudo apt-get dist-upgrade
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
There is something weird happening when I try to enable it. No matter if I use regularsudoor login as root withsudo -ito gain privilege, the enable command fails with "Permission denied" on some file.
– FallenWarrior
Oct 31 '16 at 11:48
As root or allowsudoto execute root commands
– GAD3R
Oct 31 '16 at 11:50
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormallyThis is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.
– FallenWarrior
Nov 1 '16 at 10:07
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
add a comment |
You don't need to install a new kernel version to patch the dirty cow vulnerability just enable the Canonical Livepatch Service on your Ubuntu
Kernel live patching enables runtime correction of critical security
issues in your kernel without rebooting. It’s the best way to ensure
that machines are safe at the kernel level, while guaranteeing uptime,
especially for container hosts where a single machine may be running
thousands of different workloads.
(1) Go to https://ubuntu.com/livepatch and retrieve your livepatch
token, for example: d3b07384d213edec49eaa6238ad5ff00
(2) Install the livepatch snap, like this:
$ sudo snap install canonical-livepatch
(3) Enable your account with the token from step 1
$ sudo canonical-livepatch enable d3b07384d113edec49eaa6238ad5ff00
That’s it. You’re up and running! You can check your status at any
time with:
$ canonical-livepatch status
kernel: 4.4.0-38.57-generic
fully-patched: true
version: "12.2"
Now your kernel will remain securely patched, and you can reboot when
it’s convenient for you.
Or by runing the following command:
sudo apt-get update && sudo apt-get dist-upgrade
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
You don't need to install a new kernel version to patch the dirty cow vulnerability just enable the Canonical Livepatch Service on your Ubuntu
Kernel live patching enables runtime correction of critical security
issues in your kernel without rebooting. It’s the best way to ensure
that machines are safe at the kernel level, while guaranteeing uptime,
especially for container hosts where a single machine may be running
thousands of different workloads.
(1) Go to https://ubuntu.com/livepatch and retrieve your livepatch
token, for example: d3b07384d213edec49eaa6238ad5ff00
(2) Install the livepatch snap, like this:
$ sudo snap install canonical-livepatch
(3) Enable your account with the token from step 1
$ sudo canonical-livepatch enable d3b07384d113edec49eaa6238ad5ff00
That’s it. You’re up and running! You can check your status at any
time with:
$ canonical-livepatch status
kernel: 4.4.0-38.57-generic
fully-patched: true
version: "12.2"
Now your kernel will remain securely patched, and you can reboot when
it’s convenient for you.
Or by runing the following command:
sudo apt-get update && sudo apt-get dist-upgrade
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
answered Oct 29 '16 at 17:19
GAD3RGAD3R
2,4341226
2,4341226
There is something weird happening when I try to enable it. No matter if I use regularsudoor login as root withsudo -ito gain privilege, the enable command fails with "Permission denied" on some file.
– FallenWarrior
Oct 31 '16 at 11:48
As root or allowsudoto execute root commands
– GAD3R
Oct 31 '16 at 11:50
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormallyThis is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.
– FallenWarrior
Nov 1 '16 at 10:07
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
add a comment |
There is something weird happening when I try to enable it. No matter if I use regularsudoor login as root withsudo -ito gain privilege, the enable command fails with "Permission denied" on some file.
– FallenWarrior
Oct 31 '16 at 11:48
As root or allowsudoto execute root commands
– GAD3R
Oct 31 '16 at 11:50
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormallyThis is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.
– FallenWarrior
Nov 1 '16 at 10:07
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
There is something weird happening when I try to enable it. No matter if I use regular
sudo or login as root with sudo -i to gain privilege, the enable command fails with "Permission denied" on some file.– FallenWarrior
Oct 31 '16 at 11:48
There is something weird happening when I try to enable it. No matter if I use regular
sudo or login as root with sudo -i to gain privilege, the enable command fails with "Permission denied" on some file.– FallenWarrior
Oct 31 '16 at 11:48
As root or allow
sudo to execute root commands– GAD3R
Oct 31 '16 at 11:50
As root or allow
sudo to execute root commands– GAD3R
Oct 31 '16 at 11:50
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormally This is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.– FallenWarrior
Nov 1 '16 at 10:07
~# canonical-livepatch enable **** ; cannot bind-mount the mount namespace file /proc/3070/ns/mnt -> canonical-livepatch.mnt. errmsg: Permission denied support process for mount namespace capture exited abnormally This is the output I get when I run it as root. Sorry for bad formatting, I'm on my phone at the moment.– FallenWarrior
Nov 1 '16 at 10:07
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
take a look here insights.ubuntu.com/2016/10/31/…
– GAD3R
Nov 1 '16 at 19:01
add a comment |
Better is You boot from old kernel
And delete all new kernel files from /boot
Then
update-grub
After it you can set default old kernel
Then
sudo aptitude safe-upgrade
Hope it will help
And if not
Download boot-repair and fix some issue
I like manually but it will risky for new person
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed runupdate-grub)?
– bertieb
Jan 2 at 1:44
add a comment |
Better is You boot from old kernel
And delete all new kernel files from /boot
Then
update-grub
After it you can set default old kernel
Then
sudo aptitude safe-upgrade
Hope it will help
And if not
Download boot-repair and fix some issue
I like manually but it will risky for new person
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed runupdate-grub)?
– bertieb
Jan 2 at 1:44
add a comment |
Better is You boot from old kernel
And delete all new kernel files from /boot
Then
update-grub
After it you can set default old kernel
Then
sudo aptitude safe-upgrade
Hope it will help
And if not
Download boot-repair and fix some issue
I like manually but it will risky for new person
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
Better is You boot from old kernel
And delete all new kernel files from /boot
Then
update-grub
After it you can set default old kernel
Then
sudo aptitude safe-upgrade
Hope it will help
And if not
Download boot-repair and fix some issue
I like manually but it will risky for new person
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
answered Jan 2 at 1:35
amzker pro hackeramzker pro hacker
11
11
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed runupdate-grub)?
– bertieb
Jan 2 at 1:44
add a comment |
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed runupdate-grub)?
– bertieb
Jan 2 at 1:44
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed run
update-grub)?– bertieb
Jan 2 at 1:44
Welcome to Super User! Can you edit and explain why this suggestion works, rather than what OP did (as they did indeed run
update-grub)?– bertieb
Jan 2 at 1:44
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1140204%2fmanual-kernel-update-system-wont-boot-new-kernel%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Is it listed in the GRUB configuration? Alternatively, what's in the GRUB menu when you start up?
– l0b0
Oct 29 '16 at 10:59
@l0b0 Thanks. It kept the old kernel as default for some reason, and as this is a machine mainly managed using SSH, I didn't notice. But still, even if I reboot with
GRUB_DEFAULT='gnulinux-advanced-f0724a95-d885-4cec-b74c-635d61f32c73>gnulinux-4.4.0-45-generic-advanced-f0724a95-d885-4cec-b74c-635d61f32c73'(the name gathered from the grub config file, it still boots into the old kernel.– FallenWarrior
Oct 29 '16 at 13:45