system bootOrder not found
I tried to install Ubuntu 18.04 on Acer TravelMate P278-MG, but it bootloops
1. It starts up, shows Acer logo
2. It says:
System BootOrder not found. Initializing defaults.
Creating boot entry "BootXXXX" with label "ubuntu" for the file "EFIubuntushimx.efi"
Reset System
Where XXXX - number, depending on the BIOS configuration(I tried Legacy, UEFI with SecureBoot on and off, different boot devices(there is Linplus lite boot device, which is strange))
3. goto 1.
uefi 18.04 bios
add a comment |
I tried to install Ubuntu 18.04 on Acer TravelMate P278-MG, but it bootloops
1. It starts up, shows Acer logo
2. It says:
System BootOrder not found. Initializing defaults.
Creating boot entry "BootXXXX" with label "ubuntu" for the file "EFIubuntushimx.efi"
Reset System
Where XXXX - number, depending on the BIOS configuration(I tried Legacy, UEFI with SecureBoot on and off, different boot devices(there is Linplus lite boot device, which is strange))
3. goto 1.
uefi 18.04 bios
add a comment |
I tried to install Ubuntu 18.04 on Acer TravelMate P278-MG, but it bootloops
1. It starts up, shows Acer logo
2. It says:
System BootOrder not found. Initializing defaults.
Creating boot entry "BootXXXX" with label "ubuntu" for the file "EFIubuntushimx.efi"
Reset System
Where XXXX - number, depending on the BIOS configuration(I tried Legacy, UEFI with SecureBoot on and off, different boot devices(there is Linplus lite boot device, which is strange))
3. goto 1.
uefi 18.04 bios
I tried to install Ubuntu 18.04 on Acer TravelMate P278-MG, but it bootloops
1. It starts up, shows Acer logo
2. It says:
System BootOrder not found. Initializing defaults.
Creating boot entry "BootXXXX" with label "ubuntu" for the file "EFIubuntushimx.efi"
Reset System
Where XXXX - number, depending on the BIOS configuration(I tried Legacy, UEFI with SecureBoot on and off, different boot devices(there is Linplus lite boot device, which is strange))
3. goto 1.
uefi 18.04 bios
uefi 18.04 bios
asked Jun 1 at 20:32
Ilya Savitsky
1814
1814
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I found the solution on another forum. Two steps. Select a UEFI file as trusted and given it a custom name. Then go to the boot menu and select it as first priority as described below.
PROBLEM SOLVED! It turned out the problem was in the bios settings. I switched "secure boot" on which unlocked few more options. One of them was "Select an UEFI file as trusted for executing" that's in the "security" tab. After that it showed me HDD0, I hitted enter and "EFI" showed up. After another ENTER it showed 3 folders "ubuntu", "microsoft" and "boot". The ubuntu folder contained "shimx64.efi", "grubx64.efi" and "MokManager.efi" I'm not very familiar what all of them were, but I chosed "shimx64.efi" which was then added as "trusted for executing". I went back to the boot tab and found "EFI boot0: ubuntu" or something like it. That's because I named the "trusted" UEFI file "ubuntu". I moved it up to first priority and everything worked like a charm. Thanks for the advices, they made me search for my own mistakes in the bios configuration.
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
add a comment |
I want to add something to Melebius' answer for users with HP UEFI/BIOS:
In those cases, there is no option to choose a trusted UEFI file, however, there exists the option for a "custom boot" under the "boot options" menu. You have to add custom boot path and enter "EFIubuntushimx64.efi". Then you have to change the boot priority and put "custom boot" on top of the list.
add a comment |
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',
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%2faskubuntu.com%2fquestions%2f1042747%2fsystem-bootorder-not-found%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
I found the solution on another forum. Two steps. Select a UEFI file as trusted and given it a custom name. Then go to the boot menu and select it as first priority as described below.
PROBLEM SOLVED! It turned out the problem was in the bios settings. I switched "secure boot" on which unlocked few more options. One of them was "Select an UEFI file as trusted for executing" that's in the "security" tab. After that it showed me HDD0, I hitted enter and "EFI" showed up. After another ENTER it showed 3 folders "ubuntu", "microsoft" and "boot". The ubuntu folder contained "shimx64.efi", "grubx64.efi" and "MokManager.efi" I'm not very familiar what all of them were, but I chosed "shimx64.efi" which was then added as "trusted for executing". I went back to the boot tab and found "EFI boot0: ubuntu" or something like it. That's because I named the "trusted" UEFI file "ubuntu". I moved it up to first priority and everything worked like a charm. Thanks for the advices, they made me search for my own mistakes in the bios configuration.
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
add a comment |
I found the solution on another forum. Two steps. Select a UEFI file as trusted and given it a custom name. Then go to the boot menu and select it as first priority as described below.
PROBLEM SOLVED! It turned out the problem was in the bios settings. I switched "secure boot" on which unlocked few more options. One of them was "Select an UEFI file as trusted for executing" that's in the "security" tab. After that it showed me HDD0, I hitted enter and "EFI" showed up. After another ENTER it showed 3 folders "ubuntu", "microsoft" and "boot". The ubuntu folder contained "shimx64.efi", "grubx64.efi" and "MokManager.efi" I'm not very familiar what all of them were, but I chosed "shimx64.efi" which was then added as "trusted for executing". I went back to the boot tab and found "EFI boot0: ubuntu" or something like it. That's because I named the "trusted" UEFI file "ubuntu". I moved it up to first priority and everything worked like a charm. Thanks for the advices, they made me search for my own mistakes in the bios configuration.
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
add a comment |
I found the solution on another forum. Two steps. Select a UEFI file as trusted and given it a custom name. Then go to the boot menu and select it as first priority as described below.
PROBLEM SOLVED! It turned out the problem was in the bios settings. I switched "secure boot" on which unlocked few more options. One of them was "Select an UEFI file as trusted for executing" that's in the "security" tab. After that it showed me HDD0, I hitted enter and "EFI" showed up. After another ENTER it showed 3 folders "ubuntu", "microsoft" and "boot". The ubuntu folder contained "shimx64.efi", "grubx64.efi" and "MokManager.efi" I'm not very familiar what all of them were, but I chosed "shimx64.efi" which was then added as "trusted for executing". I went back to the boot tab and found "EFI boot0: ubuntu" or something like it. That's because I named the "trusted" UEFI file "ubuntu". I moved it up to first priority and everything worked like a charm. Thanks for the advices, they made me search for my own mistakes in the bios configuration.
I found the solution on another forum. Two steps. Select a UEFI file as trusted and given it a custom name. Then go to the boot menu and select it as first priority as described below.
PROBLEM SOLVED! It turned out the problem was in the bios settings. I switched "secure boot" on which unlocked few more options. One of them was "Select an UEFI file as trusted for executing" that's in the "security" tab. After that it showed me HDD0, I hitted enter and "EFI" showed up. After another ENTER it showed 3 folders "ubuntu", "microsoft" and "boot". The ubuntu folder contained "shimx64.efi", "grubx64.efi" and "MokManager.efi" I'm not very familiar what all of them were, but I chosed "shimx64.efi" which was then added as "trusted for executing". I went back to the boot tab and found "EFI boot0: ubuntu" or something like it. That's because I named the "trusted" UEFI file "ubuntu". I moved it up to first priority and everything worked like a charm. Thanks for the advices, they made me search for my own mistakes in the bios configuration.
edited Aug 21 at 8:22
Melebius
4,38251838
4,38251838
answered Jun 7 at 14:46
pHIL
461
461
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
add a comment |
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
You are my savior! Thanks!
– drnextgis
Jul 27 at 4:48
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
this worked for me too, except in my case, the F12 boot menu was disabled in the BIOS, so I had to enable that before I could see the option in the F12 menu at boot; also, if selecting erase secure boot settings, erase has effect only upon exiting BIOS setup and saving changes and rebooting; in my case, only 2 options can be added, and the only way to change one or both is to erase (clear) them and then add another
– jmarina
Sep 9 at 13:26
add a comment |
I want to add something to Melebius' answer for users with HP UEFI/BIOS:
In those cases, there is no option to choose a trusted UEFI file, however, there exists the option for a "custom boot" under the "boot options" menu. You have to add custom boot path and enter "EFIubuntushimx64.efi". Then you have to change the boot priority and put "custom boot" on top of the list.
add a comment |
I want to add something to Melebius' answer for users with HP UEFI/BIOS:
In those cases, there is no option to choose a trusted UEFI file, however, there exists the option for a "custom boot" under the "boot options" menu. You have to add custom boot path and enter "EFIubuntushimx64.efi". Then you have to change the boot priority and put "custom boot" on top of the list.
add a comment |
I want to add something to Melebius' answer for users with HP UEFI/BIOS:
In those cases, there is no option to choose a trusted UEFI file, however, there exists the option for a "custom boot" under the "boot options" menu. You have to add custom boot path and enter "EFIubuntushimx64.efi". Then you have to change the boot priority and put "custom boot" on top of the list.
I want to add something to Melebius' answer for users with HP UEFI/BIOS:
In those cases, there is no option to choose a trusted UEFI file, however, there exists the option for a "custom boot" under the "boot options" menu. You have to add custom boot path and enter "EFIubuntushimx64.efi". Then you have to change the boot priority and put "custom boot" on top of the list.
answered Dec 20 at 11:05
Xeno
162
162
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2faskubuntu.com%2fquestions%2f1042747%2fsystem-bootorder-not-found%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