Eliminating newer Kernel images

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








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.



enter image description here



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.










share|improve this question



























    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.



    enter image description here



    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.










    share|improve this question

























      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.



      enter image description here



      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.










      share|improve this question















      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.



      enter image description here



      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






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 4 at 5:07

























      asked Apr 2 at 5:56









      Abel Tom

      325213




      325213




















          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.






          share|improve this answer




















          • 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










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          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',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          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






























          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.






          share|improve this answer




















          • 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














          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.






          share|improve this answer




















          • 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












          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.






          share|improve this answer












          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          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
















          • 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

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          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













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491