Eliminating newer Kernel images
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
2
down vote
favorite
A few weeks ago, i had my Ubuntu 17.10 with kernel version 4.13.0-37. I accidentally deleted a few important packages like network-manager
, and i could not connect to internet at all when i booted. So i decided to install Ubuntu 16.04 with kernel version 4.4.0-21-generic from DVD keeping my $HOME
intact. It worked. I can boot when i select the 4.4.0-21-generic option from my GRUB2 menu.
When i try to boot from the kernel 4.13.0-37, it goes into emergency mode, and i tried this solution here. I still booted in emergency mode, e2fsck
said that root filesystem is clean.
My question is how can i eliminate the newer versions of the kernel, will i ever be able to upgrade from 4.4.0-21-generic.
Edit 1:
I did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted only after it upgraded from 4.4.0-21-generic.
boot grub2 upgrade kernel 17.10
add a comment |Â
up vote
2
down vote
favorite
A few weeks ago, i had my Ubuntu 17.10 with kernel version 4.13.0-37. I accidentally deleted a few important packages like network-manager
, and i could not connect to internet at all when i booted. So i decided to install Ubuntu 16.04 with kernel version 4.4.0-21-generic from DVD keeping my $HOME
intact. It worked. I can boot when i select the 4.4.0-21-generic option from my GRUB2 menu.
When i try to boot from the kernel 4.13.0-37, it goes into emergency mode, and i tried this solution here. I still booted in emergency mode, e2fsck
said that root filesystem is clean.
My question is how can i eliminate the newer versions of the kernel, will i ever be able to upgrade from 4.4.0-21-generic.
Edit 1:
I did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted only after it upgraded from 4.4.0-21-generic.
boot grub2 upgrade kernel 17.10
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
A few weeks ago, i had my Ubuntu 17.10 with kernel version 4.13.0-37. I accidentally deleted a few important packages like network-manager
, and i could not connect to internet at all when i booted. So i decided to install Ubuntu 16.04 with kernel version 4.4.0-21-generic from DVD keeping my $HOME
intact. It worked. I can boot when i select the 4.4.0-21-generic option from my GRUB2 menu.
When i try to boot from the kernel 4.13.0-37, it goes into emergency mode, and i tried this solution here. I still booted in emergency mode, e2fsck
said that root filesystem is clean.
My question is how can i eliminate the newer versions of the kernel, will i ever be able to upgrade from 4.4.0-21-generic.
Edit 1:
I did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted only after it upgraded from 4.4.0-21-generic.
boot grub2 upgrade kernel 17.10
A few weeks ago, i had my Ubuntu 17.10 with kernel version 4.13.0-37. I accidentally deleted a few important packages like network-manager
, and i could not connect to internet at all when i booted. So i decided to install Ubuntu 16.04 with kernel version 4.4.0-21-generic from DVD keeping my $HOME
intact. It worked. I can boot when i select the 4.4.0-21-generic option from my GRUB2 menu.
When i try to boot from the kernel 4.13.0-37, it goes into emergency mode, and i tried this solution here. I still booted in emergency mode, e2fsck
said that root filesystem is clean.
My question is how can i eliminate the newer versions of the kernel, will i ever be able to upgrade from 4.4.0-21-generic.
Edit 1:
I did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted only after it upgraded from 4.4.0-21-generic.
boot grub2 upgrade kernel 17.10
boot grub2 upgrade kernel 17.10
edited Apr 4 at 5:07
asked Apr 2 at 5:56
Abel Tom
325213
325213
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
I too have some strange issue with Kernel version 4.13.0-37 which came as update for Ubuntu 16.04. But removing kernel is not prescribed option.Because it also removes other important linux header packages when you run sudo apt autoremove
. This results in removing network-manager and many more.
I found possible solution is to edit Grub2 boot order.
https://help.ubuntu.com/community/Grub2/Setup#Configuring_GRUB_2
To change boot order of kernel edit (GRUB_DEFAULT=0)
gksudo gedit /etc/default/grub
the first index starts from 0. So set the value as
GRUB_DEFAULT="1>9"
for second menu (Advanced) and 10th kernel option
I hope this will fix the problem till you received new kernel update.
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I too have some strange issue with Kernel version 4.13.0-37 which came as update for Ubuntu 16.04. But removing kernel is not prescribed option.Because it also removes other important linux header packages when you run sudo apt autoremove
. This results in removing network-manager and many more.
I found possible solution is to edit Grub2 boot order.
https://help.ubuntu.com/community/Grub2/Setup#Configuring_GRUB_2
To change boot order of kernel edit (GRUB_DEFAULT=0)
gksudo gedit /etc/default/grub
the first index starts from 0. So set the value as
GRUB_DEFAULT="1>9"
for second menu (Advanced) and 10th kernel option
I hope this will fix the problem till you received new kernel update.
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
add a comment |Â
up vote
1
down vote
I too have some strange issue with Kernel version 4.13.0-37 which came as update for Ubuntu 16.04. But removing kernel is not prescribed option.Because it also removes other important linux header packages when you run sudo apt autoremove
. This results in removing network-manager and many more.
I found possible solution is to edit Grub2 boot order.
https://help.ubuntu.com/community/Grub2/Setup#Configuring_GRUB_2
To change boot order of kernel edit (GRUB_DEFAULT=0)
gksudo gedit /etc/default/grub
the first index starts from 0. So set the value as
GRUB_DEFAULT="1>9"
for second menu (Advanced) and 10th kernel option
I hope this will fix the problem till you received new kernel update.
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I too have some strange issue with Kernel version 4.13.0-37 which came as update for Ubuntu 16.04. But removing kernel is not prescribed option.Because it also removes other important linux header packages when you run sudo apt autoremove
. This results in removing network-manager and many more.
I found possible solution is to edit Grub2 boot order.
https://help.ubuntu.com/community/Grub2/Setup#Configuring_GRUB_2
To change boot order of kernel edit (GRUB_DEFAULT=0)
gksudo gedit /etc/default/grub
the first index starts from 0. So set the value as
GRUB_DEFAULT="1>9"
for second menu (Advanced) and 10th kernel option
I hope this will fix the problem till you received new kernel update.
I too have some strange issue with Kernel version 4.13.0-37 which came as update for Ubuntu 16.04. But removing kernel is not prescribed option.Because it also removes other important linux header packages when you run sudo apt autoremove
. This results in removing network-manager and many more.
I found possible solution is to edit Grub2 boot order.
https://help.ubuntu.com/community/Grub2/Setup#Configuring_GRUB_2
To change boot order of kernel edit (GRUB_DEFAULT=0)
gksudo gedit /etc/default/grub
the first index starts from 0. So set the value as
GRUB_DEFAULT="1>9"
for second menu (Advanced) and 10th kernel option
I hope this will fix the problem till you received new kernel update.
answered Apr 2 at 12:57
Aravind
398115
398115
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
add a comment |Â
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
I did not do what you sugeested yet, but, i did an update&&upgrade today, and the kernel updated to 4.4.0-116, and i could boot from this kernel image, what i do not understand is, this image was already existing on my filesystem, but it booted after it upgraded from 4.4.0-21-generic.
â Abel Tom
Apr 4 at 5:08
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1021225%2feliminating-newer-kernel-images%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
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