Why does computer show device mapping table on EFI shell after Ubuntu installation?
up vote
2
down vote
favorite
I am trying to install Ubuntu on a single board computer. I booted from a USB drive with the correct image on there and went through the menus that installed Ubuntu. Once the computer restarted I unplugged the USB drive and got the following menu:
EFI Menu After Ubuntu Installation
I don't know why it's not booting into Ubuntu itself and if I try to restart the installation process the Ubuntu installer recognizes that there is an existing installation. Based on the limited research I've done online, I think I need to do something to the partitions, although I'm not sure what or why.
I've tried using GRUB by keeping the USB in to do the steps in the this link, but I can't get very far due to my inability to find the files/folders specified.
boot system-installation usb uefi
edited Dec 27 '17 at 7:22
karel
56k11124142
asked Sep 8 '17 at 19:59
Omnomnious
1112
add a comment |
up vote
2
down vote
favorite
I am trying to install Ubuntu on a single board computer. I booted from a USB drive with the correct image on there and went through the menus that installed Ubuntu. Once the computer restarted I unplugged the USB drive and got the following menu:
EFI Menu After Ubuntu Installation
I don't know why it's not booting into Ubuntu itself and if I try to restart the installation process the Ubuntu installer recognizes that there is an existing installation. Based on the limited research I've done online, I think I need to do something to the partitions, although I'm not sure what or why.
I've tried using GRUB by keeping the USB in to do the steps in the this link, but I can't get very far due to my inability to find the files/folders specified.
boot system-installation usb uefi
edited Dec 27 '17 at 7:22
karel
56k11124142
asked Sep 8 '17 at 19:59
Omnomnious
1112
Have you run boot-repair? That's the first thing to try. Search this site for detailed procedure.
– Organic Marble
Sep 9 '17 at 10:54
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I am trying to install Ubuntu on a single board computer. I booted from a USB drive with the correct image on there and went through the menus that installed Ubuntu. Once the computer restarted I unplugged the USB drive and got the following menu:
EFI Menu After Ubuntu Installation
I don't know why it's not booting into Ubuntu itself and if I try to restart the installation process the Ubuntu installer recognizes that there is an existing installation. Based on the limited research I've done online, I think I need to do something to the partitions, although I'm not sure what or why.
I've tried using GRUB by keeping the USB in to do the steps in the this link, but I can't get very far due to my inability to find the files/folders specified.
boot system-installation usb uefi
edited Dec 27 '17 at 7:22
karel
56k11124142
asked Sep 8 '17 at 19:59
Omnomnious
1112
I am trying to install Ubuntu on a single board computer. I booted from a USB drive with the correct image on there and went through the menus that installed Ubuntu. Once the computer restarted I unplugged the USB drive and got the following menu:
EFI Menu After Ubuntu Installation
I don't know why it's not booting into Ubuntu itself and if I try to restart the installation process the Ubuntu installer recognizes that there is an existing installation. Based on the limited research I've done online, I think I need to do something to the partitions, although I'm not sure what or why.
I've tried using GRUB by keeping the USB in to do the steps in the this link, but I can't get very far due to my inability to find the files/folders specified.
boot system-installation usb uefi
boot system-installation usb uefi
edited Dec 27 '17 at 7:22
karel
56k11124142
asked Sep 8 '17 at 19:59
Omnomnious
1112
edited Dec 27 '17 at 7:22
karel
56k11124142
asked Sep 8 '17 at 19:59
Omnomnious
1112
edited Dec 27 '17 at 7:22
karel
56k11124142
edited Dec 27 '17 at 7:22
karel
56k11124142
edited Dec 27 '17 at 7:22
karel
56k11124142
56k11124142
asked Sep 8 '17 at 19:59
Omnomnious
1112
asked Sep 8 '17 at 19:59
Omnomnious
1112
asked Sep 8 '17 at 19:59
Omnomnious
1112
1112
Have you run boot-repair? That's the first thing to try. Search this site for detailed procedure.
– Organic Marble
Sep 9 '17 at 10:54
add a comment |
Have you run boot-repair? That's the first thing to try. Search this site for detailed procedure.
– Organic Marble
Sep 9 '17 at 10:54
Have you run boot-repair? That's the first thing to try. Search this site for detailed procedure.
– Organic Marble
Sep 9 '17 at 10:54
Have you run boot-repair? That's the first thing to try. Search this site for detailed procedure.
– Organic Marble
Sep 9 '17 at 10:54
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
As a temporary workaround, try typing these commands at the EFI shell (the Shell> prompt in your image):
fs0:
cd EFIubuntu
shimx64.efi
This sequence should launch GRUB, which in turn should launch Ubuntu. There are a number of reasons why this might fail, but chances are good that it will work.
Once Ubuntu is booting, run the Boot Repair utility and select the "Create BootInfo Summary" option. (DO NOT click "Recommended Repair," at least not yet!) When asked whether to upload the report, click "Yes," and then post the URL provided here. This will give us more details about your configuration, which is required to base a more permanent answer on more than guesswork.
If you can't get Ubuntu to boot using my workaround, you can run Boot Repair from the Ubuntu installer booted into its "try before installing" mode.
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
add a comment |
up vote
0
down vote
Thanks, I have the same issue(on a Dell Chromebook 13 7310) and your response has finally gotten me into ubuntu, you rock.
only issue is that after reboot it repeats the problem. options to add flags in the "Boot Repair" utility weren't available.
here is the info.
http://paste.ubuntu.com/26262059/
After some google searching I found a response that made the solution permanent via copying a file.
some explanation would be nice on this workaround as it's not very clear to me how it worked.
https://askubuntu.com/a/906821/310848
thanks again for all your help :)
answered Dec 27 '17 at 6:07
Tu Et Brute
1
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',
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%2f954042%2fwhy-does-computer-show-device-mapping-table-on-efi-shell-after-ubuntu-installati%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
up vote
0
down vote
As a temporary workaround, try typing these commands at the EFI shell (the Shell> prompt in your image):
fs0:
cd EFIubuntu
shimx64.efi
This sequence should launch GRUB, which in turn should launch Ubuntu. There are a number of reasons why this might fail, but chances are good that it will work.
Once Ubuntu is booting, run the Boot Repair utility and select the "Create BootInfo Summary" option. (DO NOT click "Recommended Repair," at least not yet!) When asked whether to upload the report, click "Yes," and then post the URL provided here. This will give us more details about your configuration, which is required to base a more permanent answer on more than guesswork.
If you can't get Ubuntu to boot using my workaround, you can run Boot Repair from the Ubuntu installer booted into its "try before installing" mode.
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
add a comment |
up vote
0
down vote
As a temporary workaround, try typing these commands at the EFI shell (the Shell> prompt in your image):
fs0:
cd EFIubuntu
shimx64.efi
This sequence should launch GRUB, which in turn should launch Ubuntu. There are a number of reasons why this might fail, but chances are good that it will work.
Once Ubuntu is booting, run the Boot Repair utility and select the "Create BootInfo Summary" option. (DO NOT click "Recommended Repair," at least not yet!) When asked whether to upload the report, click "Yes," and then post the URL provided here. This will give us more details about your configuration, which is required to base a more permanent answer on more than guesswork.
If you can't get Ubuntu to boot using my workaround, you can run Boot Repair from the Ubuntu installer booted into its "try before installing" mode.
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
add a comment |
up vote
0
down vote
up vote
0
down vote
As a temporary workaround, try typing these commands at the EFI shell (the Shell> prompt in your image):
fs0:
cd EFIubuntu
shimx64.efi
This sequence should launch GRUB, which in turn should launch Ubuntu. There are a number of reasons why this might fail, but chances are good that it will work.
Once Ubuntu is booting, run the Boot Repair utility and select the "Create BootInfo Summary" option. (DO NOT click "Recommended Repair," at least not yet!) When asked whether to upload the report, click "Yes," and then post the URL provided here. This will give us more details about your configuration, which is required to base a more permanent answer on more than guesswork.
If you can't get Ubuntu to boot using my workaround, you can run Boot Repair from the Ubuntu installer booted into its "try before installing" mode.
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
As a temporary workaround, try typing these commands at the EFI shell (the Shell> prompt in your image):
fs0:
cd EFIubuntu
shimx64.efi
This sequence should launch GRUB, which in turn should launch Ubuntu. There are a number of reasons why this might fail, but chances are good that it will work.
Once Ubuntu is booting, run the Boot Repair utility and select the "Create BootInfo Summary" option. (DO NOT click "Recommended Repair," at least not yet!) When asked whether to upload the report, click "Yes," and then post the URL provided here. This will give us more details about your configuration, which is required to base a more permanent answer on more than guesswork.
If you can't get Ubuntu to boot using my workaround, you can run Boot Repair from the Ubuntu installer booted into its "try before installing" mode.
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
answered Sep 11 '17 at 18:24
Rod Smith
35k43870
35k43870
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
add a comment |
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
Thanks but I'm beginning to suspect that the hardware I'm using is faulty. I noticed that the motherboard is reset even when Ubuntu isn't installing and so I'm thinking there's either a watchdog that is resetting the system after a specific time or the hardware is just messed up and I need a new board. Either way I'll update you with what I find.
– Omnomnious
Sep 12 '17 at 19:26
add a comment |
up vote
0
down vote
Thanks, I have the same issue(on a Dell Chromebook 13 7310) and your response has finally gotten me into ubuntu, you rock.
only issue is that after reboot it repeats the problem. options to add flags in the "Boot Repair" utility weren't available.
here is the info.
http://paste.ubuntu.com/26262059/
After some google searching I found a response that made the solution permanent via copying a file.
some explanation would be nice on this workaround as it's not very clear to me how it worked.
https://askubuntu.com/a/906821/310848
thanks again for all your help :)
answered Dec 27 '17 at 6:07
Tu Et Brute
1
add a comment |
up vote
0
down vote
Thanks, I have the same issue(on a Dell Chromebook 13 7310) and your response has finally gotten me into ubuntu, you rock.
only issue is that after reboot it repeats the problem. options to add flags in the "Boot Repair" utility weren't available.
here is the info.
http://paste.ubuntu.com/26262059/
After some google searching I found a response that made the solution permanent via copying a file.
some explanation would be nice on this workaround as it's not very clear to me how it worked.
https://askubuntu.com/a/906821/310848
thanks again for all your help :)
answered Dec 27 '17 at 6:07
Tu Et Brute
1
add a comment |
up vote
0
down vote
up vote
0
down vote
Thanks, I have the same issue(on a Dell Chromebook 13 7310) and your response has finally gotten me into ubuntu, you rock.
only issue is that after reboot it repeats the problem. options to add flags in the "Boot Repair" utility weren't available.
here is the info.
http://paste.ubuntu.com/26262059/
After some google searching I found a response that made the solution permanent via copying a file.
some explanation would be nice on this workaround as it's not very clear to me how it worked.
https://askubuntu.com/a/906821/310848
thanks again for all your help :)
answered Dec 27 '17 at 6:07
Tu Et Brute
1
Thanks, I have the same issue(on a Dell Chromebook 13 7310) and your response has finally gotten me into ubuntu, you rock.
only issue is that after reboot it repeats the problem. options to add flags in the "Boot Repair" utility weren't available.
here is the info.
http://paste.ubuntu.com/26262059/
After some google searching I found a response that made the solution permanent via copying a file.
some explanation would be nice on this workaround as it's not very clear to me how it worked.
https://askubuntu.com/a/906821/310848
thanks again for all your help :)
answered Dec 27 '17 at 6:07
Tu Et Brute
1
answered Dec 27 '17 at 6:07
Tu Et Brute
1
answered Dec 27 '17 at 6:07
Tu Et Brute
1
answered Dec 27 '17 at 6:07
Tu Et Brute
1
1
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%2f954042%2fwhy-does-computer-show-device-mapping-table-on-efi-shell-after-ubuntu-installati%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
Have you run boot-repair? That's the first thing to try. Search this site for detailed procedure.
– Organic Marble
Sep 9 '17 at 10:54