UEFI Stub booting not working











up vote
0
down vote

favorite












I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:



# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose


I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.



However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).



So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?






boot uefi







share|improve this question
























  • Paste the output of efibootmgr and tree $esp (for your ESP, obviously).
    – jasonwryan
    Nov 29 at 2:57












  • @jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
    – Tyler Durden
    Nov 29 at 3:19










  • You chroot in from the live media and paste from there. Instead of tree you can use ls -R.
    – jasonwryan
    Nov 29 at 4:50










  • @jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
    – Tyler Durden
    Nov 29 at 12:39










  • You chroot in from the archiso...
    – jasonwryan
    Nov 29 at 16:39















up vote
0
down vote

favorite












I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:



# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose


I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.



However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).



So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?






boot uefi







share|improve this question
























  • Paste the output of efibootmgr and tree $esp (for your ESP, obviously).
    – jasonwryan
    Nov 29 at 2:57












  • @jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
    – Tyler Durden
    Nov 29 at 3:19










  • You chroot in from the live media and paste from there. Instead of tree you can use ls -R.
    – jasonwryan
    Nov 29 at 4:50










  • @jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
    – Tyler Durden
    Nov 29 at 12:39










  • You chroot in from the archiso...
    – jasonwryan
    Nov 29 at 16:39













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:



# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose


I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.



However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).



So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?






boot uefi







share|improve this question















I am trying to boot Arch Linux via an EFI Stub. I created an EFI partition (formatted as FAT32), a swap partition and a main partition on which I installed the Arch Linux core package group. I then used the efibootmgr to configure my motherboard to use the EFI partition to boot using the command as follows:



# efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "mysystem" --loader /vmlinuz-linux --unicode 'root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX rw initrd=initramfs-linux.img' --verbose


I know that this worked because the boot option "mysystem" is showing up in my motherboard's BIOS boot options and it lists the SSD involved so I know the PARTUUID I used is correct.



However, when I tell the machine to boot this way it pauses briefly and then fails (either going back to the BIOS setup or giving an error message depending on how it was initiated).



So, either the EFI partition is empty for some reason or the files there are not matching the settings in the efibootmgr instruction. But I do not know how to diagnose this further. How do I even find out the contents of the EFI partition in the first place?






boot uefi




boot uefi






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 29 at 2:58









jasonwryan

48.7k14134184




48.7k14134184










asked Nov 29 at 2:51









Tyler Durden

1,52841849




1,52841849












  • Paste the output of efibootmgr and tree $esp (for your ESP, obviously).
    – jasonwryan
    Nov 29 at 2:57












  • @jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
    – Tyler Durden
    Nov 29 at 3:19










  • You chroot in from the live media and paste from there. Instead of tree you can use ls -R.
    – jasonwryan
    Nov 29 at 4:50










  • @jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
    – Tyler Durden
    Nov 29 at 12:39










  • You chroot in from the archiso...
    – jasonwryan
    Nov 29 at 16:39


















  • Paste the output of efibootmgr and tree $esp (for your ESP, obviously).
    – jasonwryan
    Nov 29 at 2:57












  • @jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
    – Tyler Durden
    Nov 29 at 3:19










  • You chroot in from the live media and paste from there. Instead of tree you can use ls -R.
    – jasonwryan
    Nov 29 at 4:50










  • @jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
    – Tyler Durden
    Nov 29 at 12:39










  • You chroot in from the archiso...
    – jasonwryan
    Nov 29 at 16:39
















Paste the output of efibootmgr and tree $esp (for your ESP, obviously).
– jasonwryan
Nov 29 at 2:57






Paste the output of efibootmgr and tree $esp (for your ESP, obviously).
– jasonwryan
Nov 29 at 2:57














@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19




@jasonwryan That is not easy to do because the system is not booting, so I do not have web access for it yet. The command "tree $esp" results in the error "zsh: command not found: tree".
– Tyler Durden
Nov 29 at 3:19












You chroot in from the live media and paste from there. Instead of tree you can use ls -R.
– jasonwryan
Nov 29 at 4:50




You chroot in from the live media and paste from there. Instead of tree you can use ls -R.
– jasonwryan
Nov 29 at 4:50












@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39




@jasonwryan ls -R $esp results in showing a single file: install.txt which is the file in the root directory of the archiso ramdisk.
– Tyler Durden
Nov 29 at 12:39












You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39




You chroot in from the archiso...
– jasonwryan
Nov 29 at 16:39















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484813%2fuefi-stub-booting-not-working%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484813%2fuefi-stub-booting-not-working%23new-answer', 'question_page');
}
);

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







-

Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Image
4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
Read more

Can't connect RFCOMM socket: Host is down

Image
up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
Read more

Kernel panic - not syncing: Fatal Exception in Interrupt

Image
0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
Read more