Ubuntu 17.10 not booting after bootloader update (Acer laptop)

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








up vote
0
down vote

favorite












Problem:



I installed Ubuntu on my laptop computer.
It was working just fine for several weeks.
Recently – seemingly out of nowhere – I had this weird and frustrating problem that the device would not boot; just stuck in a loop, saying:



System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0001" with label "ubuntu" for file "EFIubuntushimx64.efi"

Reset System


Edit: I can’t even access GRUB at that point.



Solution:



I tried doing a clean reinstallation of Ubuntu several times.
At last I found out by trial and error that a specific update is causing the problem.



If I install Boot loader to chain-load signed boot loaders under Secure Boot (version 13-0ubuntu2) from the software updater and restart, I cannot boot up again.



(see screenshot)



So I guess just skipping this update would be a workaround …



Edit: The same thing happens if I install Secure Boot chain-loading bootloader (Microsoft-signed binary) (the second update visible on the screenshot) or if I install both of them.



Question:



Is this a critical bug?
Please help my reporting.
My technical knowledge about bootloaders and such is very limited.
Do you know which package is causing the problem?



It could also just be a problem with my installation method (see below).
But even that would be weird because it used to work before the update.



Clarification: I am not looking for information on how to report a bug.
I’d like to gather information for writing into a bug report.
More specifically:



  • Is this an error on my side (hardware, firmware, …)?

  • Is this a new or known bug in Ubuntu?

  • If so, how do I know which package is causing the problem?

My device/setup:



I installed Ubuntu in UEFI mode and then switched my BIOS to legacy.
It may sound weird but that’s the only way I got it to work.



  • Model: Acer TravelMate B117

  • BIOS: InsydeH20 Setup Utility v1.11

  • OS: Ubuntu only. No Microsoft, no custom GRUB configuration.









share|improve this question























  • is your computer a Lenovo? see bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 for the recommended repair.
    – ravery
    Mar 7 at 23:01







  • 1




    Possible duplicate of How do I report a bug?
    – David Foerster
    Mar 8 at 8:41










  • @DavidFoerster I have read this question before and I don’t think it’s a duplicate. I could not use the bug tracker because my device is not booting. And I was not sure if this is actually a bug. The guideline at help.ubuntu.com even suggests asking the community first.
    – Lilalas
    Mar 8 at 9:06










  • @Lilalas: To which answer are you referring? Only some of them exclusively suggest local bug reporting tools like ubbuntu-bug. You don't need a bootable system to report a bug and the answers to linked question don't imply that overall.
    – David Foerster
    Mar 8 at 9:36






  • 1




    Best to update UEFI/BIOS. Some older versions did not have "trust" setting. Acer Trust Settings - details, some now report that then secure boot has to be on to set trust: ubuntuforums.org/… ubuntuforums.org/showthread.php?t=2358003 & askubuntu.com/questions/862946/… & Acer Aspire E15, many details Trust settings in step 35 askubuntu.com/questions/627416/… & askubuntu.com/questions/870022/how-to-get-grub-boot-option/…
    – oldfred
    Mar 9 at 0:26














up vote
0
down vote

favorite












Problem:



I installed Ubuntu on my laptop computer.
It was working just fine for several weeks.
Recently – seemingly out of nowhere – I had this weird and frustrating problem that the device would not boot; just stuck in a loop, saying:



System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0001" with label "ubuntu" for file "EFIubuntushimx64.efi"

Reset System


Edit: I can’t even access GRUB at that point.



Solution:



I tried doing a clean reinstallation of Ubuntu several times.
At last I found out by trial and error that a specific update is causing the problem.



If I install Boot loader to chain-load signed boot loaders under Secure Boot (version 13-0ubuntu2) from the software updater and restart, I cannot boot up again.



(see screenshot)



So I guess just skipping this update would be a workaround …



Edit: The same thing happens if I install Secure Boot chain-loading bootloader (Microsoft-signed binary) (the second update visible on the screenshot) or if I install both of them.



Question:



Is this a critical bug?
Please help my reporting.
My technical knowledge about bootloaders and such is very limited.
Do you know which package is causing the problem?



It could also just be a problem with my installation method (see below).
But even that would be weird because it used to work before the update.



Clarification: I am not looking for information on how to report a bug.
I’d like to gather information for writing into a bug report.
More specifically:



  • Is this an error on my side (hardware, firmware, …)?

  • Is this a new or known bug in Ubuntu?

  • If so, how do I know which package is causing the problem?

My device/setup:



I installed Ubuntu in UEFI mode and then switched my BIOS to legacy.
It may sound weird but that’s the only way I got it to work.



  • Model: Acer TravelMate B117

  • BIOS: InsydeH20 Setup Utility v1.11

  • OS: Ubuntu only. No Microsoft, no custom GRUB configuration.









share|improve this question























  • is your computer a Lenovo? see bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 for the recommended repair.
    – ravery
    Mar 7 at 23:01







  • 1




    Possible duplicate of How do I report a bug?
    – David Foerster
    Mar 8 at 8:41










  • @DavidFoerster I have read this question before and I don’t think it’s a duplicate. I could not use the bug tracker because my device is not booting. And I was not sure if this is actually a bug. The guideline at help.ubuntu.com even suggests asking the community first.
    – Lilalas
    Mar 8 at 9:06










  • @Lilalas: To which answer are you referring? Only some of them exclusively suggest local bug reporting tools like ubbuntu-bug. You don't need a bootable system to report a bug and the answers to linked question don't imply that overall.
    – David Foerster
    Mar 8 at 9:36






  • 1




    Best to update UEFI/BIOS. Some older versions did not have "trust" setting. Acer Trust Settings - details, some now report that then secure boot has to be on to set trust: ubuntuforums.org/… ubuntuforums.org/showthread.php?t=2358003 & askubuntu.com/questions/862946/… & Acer Aspire E15, many details Trust settings in step 35 askubuntu.com/questions/627416/… & askubuntu.com/questions/870022/how-to-get-grub-boot-option/…
    – oldfred
    Mar 9 at 0:26












up vote
0
down vote

favorite









up vote
0
down vote

favorite











Problem:



I installed Ubuntu on my laptop computer.
It was working just fine for several weeks.
Recently – seemingly out of nowhere – I had this weird and frustrating problem that the device would not boot; just stuck in a loop, saying:



System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0001" with label "ubuntu" for file "EFIubuntushimx64.efi"

Reset System


Edit: I can’t even access GRUB at that point.



Solution:



I tried doing a clean reinstallation of Ubuntu several times.
At last I found out by trial and error that a specific update is causing the problem.



If I install Boot loader to chain-load signed boot loaders under Secure Boot (version 13-0ubuntu2) from the software updater and restart, I cannot boot up again.



(see screenshot)



So I guess just skipping this update would be a workaround …



Edit: The same thing happens if I install Secure Boot chain-loading bootloader (Microsoft-signed binary) (the second update visible on the screenshot) or if I install both of them.



Question:



Is this a critical bug?
Please help my reporting.
My technical knowledge about bootloaders and such is very limited.
Do you know which package is causing the problem?



It could also just be a problem with my installation method (see below).
But even that would be weird because it used to work before the update.



Clarification: I am not looking for information on how to report a bug.
I’d like to gather information for writing into a bug report.
More specifically:



  • Is this an error on my side (hardware, firmware, …)?

  • Is this a new or known bug in Ubuntu?

  • If so, how do I know which package is causing the problem?

My device/setup:



I installed Ubuntu in UEFI mode and then switched my BIOS to legacy.
It may sound weird but that’s the only way I got it to work.



  • Model: Acer TravelMate B117

  • BIOS: InsydeH20 Setup Utility v1.11

  • OS: Ubuntu only. No Microsoft, no custom GRUB configuration.









share|improve this question















Problem:



I installed Ubuntu on my laptop computer.
It was working just fine for several weeks.
Recently – seemingly out of nowhere – I had this weird and frustrating problem that the device would not boot; just stuck in a loop, saying:



System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0001" with label "ubuntu" for file "EFIubuntushimx64.efi"

Reset System


Edit: I can’t even access GRUB at that point.



Solution:



I tried doing a clean reinstallation of Ubuntu several times.
At last I found out by trial and error that a specific update is causing the problem.



If I install Boot loader to chain-load signed boot loaders under Secure Boot (version 13-0ubuntu2) from the software updater and restart, I cannot boot up again.



(see screenshot)



So I guess just skipping this update would be a workaround …



Edit: The same thing happens if I install Secure Boot chain-loading bootloader (Microsoft-signed binary) (the second update visible on the screenshot) or if I install both of them.



Question:



Is this a critical bug?
Please help my reporting.
My technical knowledge about bootloaders and such is very limited.
Do you know which package is causing the problem?



It could also just be a problem with my installation method (see below).
But even that would be weird because it used to work before the update.



Clarification: I am not looking for information on how to report a bug.
I’d like to gather information for writing into a bug report.
More specifically:



  • Is this an error on my side (hardware, firmware, …)?

  • Is this a new or known bug in Ubuntu?

  • If so, how do I know which package is causing the problem?

My device/setup:



I installed Ubuntu in UEFI mode and then switched my BIOS to legacy.
It may sound weird but that’s the only way I got it to work.



  • Model: Acer TravelMate B117

  • BIOS: InsydeH20 Setup Utility v1.11

  • OS: Ubuntu only. No Microsoft, no custom GRUB configuration.






boot uefi bootloader acer bug-reporting






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 9 at 11:04

























asked Mar 7 at 22:02









Lilalas

113




113











  • is your computer a Lenovo? see bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 for the recommended repair.
    – ravery
    Mar 7 at 23:01







  • 1




    Possible duplicate of How do I report a bug?
    – David Foerster
    Mar 8 at 8:41










  • @DavidFoerster I have read this question before and I don’t think it’s a duplicate. I could not use the bug tracker because my device is not booting. And I was not sure if this is actually a bug. The guideline at help.ubuntu.com even suggests asking the community first.
    – Lilalas
    Mar 8 at 9:06










  • @Lilalas: To which answer are you referring? Only some of them exclusively suggest local bug reporting tools like ubbuntu-bug. You don't need a bootable system to report a bug and the answers to linked question don't imply that overall.
    – David Foerster
    Mar 8 at 9:36






  • 1




    Best to update UEFI/BIOS. Some older versions did not have "trust" setting. Acer Trust Settings - details, some now report that then secure boot has to be on to set trust: ubuntuforums.org/… ubuntuforums.org/showthread.php?t=2358003 & askubuntu.com/questions/862946/… & Acer Aspire E15, many details Trust settings in step 35 askubuntu.com/questions/627416/… & askubuntu.com/questions/870022/how-to-get-grub-boot-option/…
    – oldfred
    Mar 9 at 0:26
















  • is your computer a Lenovo? see bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 for the recommended repair.
    – ravery
    Mar 7 at 23:01







  • 1




    Possible duplicate of How do I report a bug?
    – David Foerster
    Mar 8 at 8:41










  • @DavidFoerster I have read this question before and I don’t think it’s a duplicate. I could not use the bug tracker because my device is not booting. And I was not sure if this is actually a bug. The guideline at help.ubuntu.com even suggests asking the community first.
    – Lilalas
    Mar 8 at 9:06










  • @Lilalas: To which answer are you referring? Only some of them exclusively suggest local bug reporting tools like ubbuntu-bug. You don't need a bootable system to report a bug and the answers to linked question don't imply that overall.
    – David Foerster
    Mar 8 at 9:36






  • 1




    Best to update UEFI/BIOS. Some older versions did not have "trust" setting. Acer Trust Settings - details, some now report that then secure boot has to be on to set trust: ubuntuforums.org/… ubuntuforums.org/showthread.php?t=2358003 & askubuntu.com/questions/862946/… & Acer Aspire E15, many details Trust settings in step 35 askubuntu.com/questions/627416/… & askubuntu.com/questions/870022/how-to-get-grub-boot-option/…
    – oldfred
    Mar 9 at 0:26















is your computer a Lenovo? see bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 for the recommended repair.
– ravery
Mar 7 at 23:01





is your computer a Lenovo? see bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 for the recommended repair.
– ravery
Mar 7 at 23:01





1




1




Possible duplicate of How do I report a bug?
– David Foerster
Mar 8 at 8:41




Possible duplicate of How do I report a bug?
– David Foerster
Mar 8 at 8:41












@DavidFoerster I have read this question before and I don’t think it’s a duplicate. I could not use the bug tracker because my device is not booting. And I was not sure if this is actually a bug. The guideline at help.ubuntu.com even suggests asking the community first.
– Lilalas
Mar 8 at 9:06




@DavidFoerster I have read this question before and I don’t think it’s a duplicate. I could not use the bug tracker because my device is not booting. And I was not sure if this is actually a bug. The guideline at help.ubuntu.com even suggests asking the community first.
– Lilalas
Mar 8 at 9:06












@Lilalas: To which answer are you referring? Only some of them exclusively suggest local bug reporting tools like ubbuntu-bug. You don't need a bootable system to report a bug and the answers to linked question don't imply that overall.
– David Foerster
Mar 8 at 9:36




@Lilalas: To which answer are you referring? Only some of them exclusively suggest local bug reporting tools like ubbuntu-bug. You don't need a bootable system to report a bug and the answers to linked question don't imply that overall.
– David Foerster
Mar 8 at 9:36




1




1




Best to update UEFI/BIOS. Some older versions did not have "trust" setting. Acer Trust Settings - details, some now report that then secure boot has to be on to set trust: ubuntuforums.org/… ubuntuforums.org/showthread.php?t=2358003 & askubuntu.com/questions/862946/… & Acer Aspire E15, many details Trust settings in step 35 askubuntu.com/questions/627416/… & askubuntu.com/questions/870022/how-to-get-grub-boot-option/…
– oldfred
Mar 9 at 0:26




Best to update UEFI/BIOS. Some older versions did not have "trust" setting. Acer Trust Settings - details, some now report that then secure boot has to be on to set trust: ubuntuforums.org/… ubuntuforums.org/showthread.php?t=2358003 & askubuntu.com/questions/862946/… & Acer Aspire E15, many details Trust settings in step 35 askubuntu.com/questions/627416/… & askubuntu.com/questions/870022/how-to-get-grub-boot-option/…
– oldfred
Mar 9 at 0:26










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










​Turns out this was caused by the BIOS/UEFI firmware.
After updating the firmware to version v1.15, I was able to install Ubuntu in UEFI mode. (BIOS/Legacy mode still don’t work for some reason.)
I had to mark the bootloader files as trusted like @oldfred suggested.



Now everything works just fine.
After installing all Ubuntu updates, the OS still boots!



If you have an Acer, you can download the latest firmware from the Acer support website.
Unfortunately Acer does not support Linux, so you need Windows to flash the system.






share|improve this answer




















    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%2f1012872%2fubuntu-17-10-not-booting-after-bootloader-update-acer-laptop%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



    accepted










    ​Turns out this was caused by the BIOS/UEFI firmware.
    After updating the firmware to version v1.15, I was able to install Ubuntu in UEFI mode. (BIOS/Legacy mode still don’t work for some reason.)
    I had to mark the bootloader files as trusted like @oldfred suggested.



    Now everything works just fine.
    After installing all Ubuntu updates, the OS still boots!



    If you have an Acer, you can download the latest firmware from the Acer support website.
    Unfortunately Acer does not support Linux, so you need Windows to flash the system.






    share|improve this answer
























      up vote
      1
      down vote



      accepted










      ​Turns out this was caused by the BIOS/UEFI firmware.
      After updating the firmware to version v1.15, I was able to install Ubuntu in UEFI mode. (BIOS/Legacy mode still don’t work for some reason.)
      I had to mark the bootloader files as trusted like @oldfred suggested.



      Now everything works just fine.
      After installing all Ubuntu updates, the OS still boots!



      If you have an Acer, you can download the latest firmware from the Acer support website.
      Unfortunately Acer does not support Linux, so you need Windows to flash the system.






      share|improve this answer






















        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        ​Turns out this was caused by the BIOS/UEFI firmware.
        After updating the firmware to version v1.15, I was able to install Ubuntu in UEFI mode. (BIOS/Legacy mode still don’t work for some reason.)
        I had to mark the bootloader files as trusted like @oldfred suggested.



        Now everything works just fine.
        After installing all Ubuntu updates, the OS still boots!



        If you have an Acer, you can download the latest firmware from the Acer support website.
        Unfortunately Acer does not support Linux, so you need Windows to flash the system.






        share|improve this answer












        ​Turns out this was caused by the BIOS/UEFI firmware.
        After updating the firmware to version v1.15, I was able to install Ubuntu in UEFI mode. (BIOS/Legacy mode still don’t work for some reason.)
        I had to mark the bootloader files as trusted like @oldfred suggested.



        Now everything works just fine.
        After installing all Ubuntu updates, the OS still boots!



        If you have an Acer, you can download the latest firmware from the Acer support website.
        Unfortunately Acer does not support Linux, so you need Windows to flash the system.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 15 at 11:19









        Lilalas

        113




        113



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1012872%2fubuntu-17-10-not-booting-after-bootloader-update-acer-laptop%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