Cannot boot into Linux off live USB
I am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop.
I cannot boot up ANY Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts:
GNU GRUB version 2.02~beta2-9ubuntu1
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.
grub>
When I type in "boot" I get the error: you need to load the kernel first.
Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?
linux boot grub2 dual-boot live-usb
add a comment |
I am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop.
I cannot boot up ANY Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts:
GNU GRUB version 2.02~beta2-9ubuntu1
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.
grub>
When I type in "boot" I get the error: you need to load the kernel first.
Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?
linux boot grub2 dual-boot live-usb
Did you tinker with legacy support for USB in BIOS? BTW please read the help→tour and leave out distractions and chit-chat in your posts, that will be appreciated by all future readers.
– Anthon
Aug 25 '15 at 10:14
@Anthon Thanks for the heads up. No I have not changed any USB settings in the BIOS. The only USB options in there are: USB Emulation, USB Powershare, USB Wake Support and USB debug.
– Sylvoo
Aug 25 '15 at 12:29
I would at least set USB emulation to on if it is not already set, I assumed that GRUB would use the BIOS to read the data from USB, but I am not 100% sure if it does (if not, some new USB chipset might be the problem).
– Anthon
Aug 25 '15 at 12:35
Your laptop has partly succeeded in its attempt to boot the live USB otherwise you wouldn't see the GRUB prompt. But GRUB hasn't been able to load the kernel so it can't go any further. Usually that sort of message happens when the kernel &/or other essential boot files aren't where GRUB expects them, or if the disk they're on is unreadable for some reason. My guess is that the system has "ejected" the USB after it's started to boot from it. You can see what partitions are available using the GRUB2ls
command (but I don't know the details since I use GRUB Legacy).
– PM 2Ring
Aug 25 '15 at 12:48
Another option that may be worth trying is to use a Live USB that uses a different bootloader, eg Grub4DOS or syslinux. Puppy Linux is a very compact distro (~130 MB) that uses syslinux by default. It's slightly non-standard so it doesn't play well with generic software that creates live USBs from bootable .iso file (like UNetbootin). But it's easy to create a live USB in a running Puppy system.
– PM 2Ring
Aug 25 '15 at 12:54
add a comment |
I am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop.
I cannot boot up ANY Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts:
GNU GRUB version 2.02~beta2-9ubuntu1
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.
grub>
When I type in "boot" I get the error: you need to load the kernel first.
Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?
linux boot grub2 dual-boot live-usb
I am trying to dual boot Linux on my laptop (Dell XPS 15) which is running Windows 10 Pro. I did not have any problem dual booting the two operating systems on my desktop.
I cannot boot up ANY Linux Distro, I have tried Mint, Ubuntu and Elementary OS. Whenever I try to boot from a live USB, I get the this message on all attempts:
GNU GRUB version 2.02~beta2-9ubuntu1
Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists are possible device or file completions.
grub>
When I type in "boot" I get the error: you need to load the kernel first.
Secure boot is disabled, and I have tried both in legacy and UEFI BIOS mode. I have never come across this error before, what causes it?
linux boot grub2 dual-boot live-usb
linux boot grub2 dual-boot live-usb
edited Aug 25 '15 at 10:15
Anthon
60.4k17102165
60.4k17102165
asked Aug 25 '15 at 10:02
SylvooSylvoo
3114
3114
Did you tinker with legacy support for USB in BIOS? BTW please read the help→tour and leave out distractions and chit-chat in your posts, that will be appreciated by all future readers.
– Anthon
Aug 25 '15 at 10:14
@Anthon Thanks for the heads up. No I have not changed any USB settings in the BIOS. The only USB options in there are: USB Emulation, USB Powershare, USB Wake Support and USB debug.
– Sylvoo
Aug 25 '15 at 12:29
I would at least set USB emulation to on if it is not already set, I assumed that GRUB would use the BIOS to read the data from USB, but I am not 100% sure if it does (if not, some new USB chipset might be the problem).
– Anthon
Aug 25 '15 at 12:35
Your laptop has partly succeeded in its attempt to boot the live USB otherwise you wouldn't see the GRUB prompt. But GRUB hasn't been able to load the kernel so it can't go any further. Usually that sort of message happens when the kernel &/or other essential boot files aren't where GRUB expects them, or if the disk they're on is unreadable for some reason. My guess is that the system has "ejected" the USB after it's started to boot from it. You can see what partitions are available using the GRUB2ls
command (but I don't know the details since I use GRUB Legacy).
– PM 2Ring
Aug 25 '15 at 12:48
Another option that may be worth trying is to use a Live USB that uses a different bootloader, eg Grub4DOS or syslinux. Puppy Linux is a very compact distro (~130 MB) that uses syslinux by default. It's slightly non-standard so it doesn't play well with generic software that creates live USBs from bootable .iso file (like UNetbootin). But it's easy to create a live USB in a running Puppy system.
– PM 2Ring
Aug 25 '15 at 12:54
add a comment |
Did you tinker with legacy support for USB in BIOS? BTW please read the help→tour and leave out distractions and chit-chat in your posts, that will be appreciated by all future readers.
– Anthon
Aug 25 '15 at 10:14
@Anthon Thanks for the heads up. No I have not changed any USB settings in the BIOS. The only USB options in there are: USB Emulation, USB Powershare, USB Wake Support and USB debug.
– Sylvoo
Aug 25 '15 at 12:29
I would at least set USB emulation to on if it is not already set, I assumed that GRUB would use the BIOS to read the data from USB, but I am not 100% sure if it does (if not, some new USB chipset might be the problem).
– Anthon
Aug 25 '15 at 12:35
Your laptop has partly succeeded in its attempt to boot the live USB otherwise you wouldn't see the GRUB prompt. But GRUB hasn't been able to load the kernel so it can't go any further. Usually that sort of message happens when the kernel &/or other essential boot files aren't where GRUB expects them, or if the disk they're on is unreadable for some reason. My guess is that the system has "ejected" the USB after it's started to boot from it. You can see what partitions are available using the GRUB2ls
command (but I don't know the details since I use GRUB Legacy).
– PM 2Ring
Aug 25 '15 at 12:48
Another option that may be worth trying is to use a Live USB that uses a different bootloader, eg Grub4DOS or syslinux. Puppy Linux is a very compact distro (~130 MB) that uses syslinux by default. It's slightly non-standard so it doesn't play well with generic software that creates live USBs from bootable .iso file (like UNetbootin). But it's easy to create a live USB in a running Puppy system.
– PM 2Ring
Aug 25 '15 at 12:54
Did you tinker with legacy support for USB in BIOS? BTW please read the help→tour and leave out distractions and chit-chat in your posts, that will be appreciated by all future readers.
– Anthon
Aug 25 '15 at 10:14
Did you tinker with legacy support for USB in BIOS? BTW please read the help→tour and leave out distractions and chit-chat in your posts, that will be appreciated by all future readers.
– Anthon
Aug 25 '15 at 10:14
@Anthon Thanks for the heads up. No I have not changed any USB settings in the BIOS. The only USB options in there are: USB Emulation, USB Powershare, USB Wake Support and USB debug.
– Sylvoo
Aug 25 '15 at 12:29
@Anthon Thanks for the heads up. No I have not changed any USB settings in the BIOS. The only USB options in there are: USB Emulation, USB Powershare, USB Wake Support and USB debug.
– Sylvoo
Aug 25 '15 at 12:29
I would at least set USB emulation to on if it is not already set, I assumed that GRUB would use the BIOS to read the data from USB, but I am not 100% sure if it does (if not, some new USB chipset might be the problem).
– Anthon
Aug 25 '15 at 12:35
I would at least set USB emulation to on if it is not already set, I assumed that GRUB would use the BIOS to read the data from USB, but I am not 100% sure if it does (if not, some new USB chipset might be the problem).
– Anthon
Aug 25 '15 at 12:35
Your laptop has partly succeeded in its attempt to boot the live USB otherwise you wouldn't see the GRUB prompt. But GRUB hasn't been able to load the kernel so it can't go any further. Usually that sort of message happens when the kernel &/or other essential boot files aren't where GRUB expects them, or if the disk they're on is unreadable for some reason. My guess is that the system has "ejected" the USB after it's started to boot from it. You can see what partitions are available using the GRUB2
ls
command (but I don't know the details since I use GRUB Legacy).– PM 2Ring
Aug 25 '15 at 12:48
Your laptop has partly succeeded in its attempt to boot the live USB otherwise you wouldn't see the GRUB prompt. But GRUB hasn't been able to load the kernel so it can't go any further. Usually that sort of message happens when the kernel &/or other essential boot files aren't where GRUB expects them, or if the disk they're on is unreadable for some reason. My guess is that the system has "ejected" the USB after it's started to boot from it. You can see what partitions are available using the GRUB2
ls
command (but I don't know the details since I use GRUB Legacy).– PM 2Ring
Aug 25 '15 at 12:48
Another option that may be worth trying is to use a Live USB that uses a different bootloader, eg Grub4DOS or syslinux. Puppy Linux is a very compact distro (~130 MB) that uses syslinux by default. It's slightly non-standard so it doesn't play well with generic software that creates live USBs from bootable .iso file (like UNetbootin). But it's easy to create a live USB in a running Puppy system.
– PM 2Ring
Aug 25 '15 at 12:54
Another option that may be worth trying is to use a Live USB that uses a different bootloader, eg Grub4DOS or syslinux. Puppy Linux is a very compact distro (~130 MB) that uses syslinux by default. It's slightly non-standard so it doesn't play well with generic software that creates live USBs from bootable .iso file (like UNetbootin). But it's easy to create a live USB in a running Puppy system.
– PM 2Ring
Aug 25 '15 at 12:54
add a comment |
1 Answer
1
active
oldest
votes
You say ANY distro fails... as such, the completeness of your question leaves much to be desired, until such time as you describe your preparation of this USB stick. Your point of being stuck half-way into Grub is familiar-- I was having success putting Mint on a thumbdrive via Unetbootin (though actually I had to find a tweak and edit the menu.lst file manually to get it to use the USB instead of looking for a CD, since I was using a .iso (CD) image source) but that stopped working when I tried Mint 18.x which apparently switched to syslinux from the simpler Grub in the 17.x with which I had had success.
Searching a bit, I notice the Arch brainiacs seem to favour Gummiboot for UEFI environments: https://www.reddit.com/r/archlinux/comments/2l5rvk/syslinux_or_grub/
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
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%2funix.stackexchange.com%2fquestions%2f225331%2fcannot-boot-into-linux-off-live-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You say ANY distro fails... as such, the completeness of your question leaves much to be desired, until such time as you describe your preparation of this USB stick. Your point of being stuck half-way into Grub is familiar-- I was having success putting Mint on a thumbdrive via Unetbootin (though actually I had to find a tweak and edit the menu.lst file manually to get it to use the USB instead of looking for a CD, since I was using a .iso (CD) image source) but that stopped working when I tried Mint 18.x which apparently switched to syslinux from the simpler Grub in the 17.x with which I had had success.
Searching a bit, I notice the Arch brainiacs seem to favour Gummiboot for UEFI environments: https://www.reddit.com/r/archlinux/comments/2l5rvk/syslinux_or_grub/
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
add a comment |
You say ANY distro fails... as such, the completeness of your question leaves much to be desired, until such time as you describe your preparation of this USB stick. Your point of being stuck half-way into Grub is familiar-- I was having success putting Mint on a thumbdrive via Unetbootin (though actually I had to find a tweak and edit the menu.lst file manually to get it to use the USB instead of looking for a CD, since I was using a .iso (CD) image source) but that stopped working when I tried Mint 18.x which apparently switched to syslinux from the simpler Grub in the 17.x with which I had had success.
Searching a bit, I notice the Arch brainiacs seem to favour Gummiboot for UEFI environments: https://www.reddit.com/r/archlinux/comments/2l5rvk/syslinux_or_grub/
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
add a comment |
You say ANY distro fails... as such, the completeness of your question leaves much to be desired, until such time as you describe your preparation of this USB stick. Your point of being stuck half-way into Grub is familiar-- I was having success putting Mint on a thumbdrive via Unetbootin (though actually I had to find a tweak and edit the menu.lst file manually to get it to use the USB instead of looking for a CD, since I was using a .iso (CD) image source) but that stopped working when I tried Mint 18.x which apparently switched to syslinux from the simpler Grub in the 17.x with which I had had success.
Searching a bit, I notice the Arch brainiacs seem to favour Gummiboot for UEFI environments: https://www.reddit.com/r/archlinux/comments/2l5rvk/syslinux_or_grub/
You say ANY distro fails... as such, the completeness of your question leaves much to be desired, until such time as you describe your preparation of this USB stick. Your point of being stuck half-way into Grub is familiar-- I was having success putting Mint on a thumbdrive via Unetbootin (though actually I had to find a tweak and edit the menu.lst file manually to get it to use the USB instead of looking for a CD, since I was using a .iso (CD) image source) but that stopped working when I tried Mint 18.x which apparently switched to syslinux from the simpler Grub in the 17.x with which I had had success.
Searching a bit, I notice the Arch brainiacs seem to favour Gummiboot for UEFI environments: https://www.reddit.com/r/archlinux/comments/2l5rvk/syslinux_or_grub/
edited Sep 14 '16 at 23:18
answered Sep 7 '16 at 2:02
Mark A. WilliamsMark A. Williams
62
62
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
add a comment |
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
Please try to better format your answers. You should also avoid asking questions in an answer. That is usually done in comments. For the moment, since you don't have sufficient reputation to comment, you should stick to questions that can be answered directly.
– Julie Pelletier
Sep 7 '16 at 2:29
add a comment |
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.
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%2funix.stackexchange.com%2fquestions%2f225331%2fcannot-boot-into-linux-off-live-usb%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
Did you tinker with legacy support for USB in BIOS? BTW please read the help→tour and leave out distractions and chit-chat in your posts, that will be appreciated by all future readers.
– Anthon
Aug 25 '15 at 10:14
@Anthon Thanks for the heads up. No I have not changed any USB settings in the BIOS. The only USB options in there are: USB Emulation, USB Powershare, USB Wake Support and USB debug.
– Sylvoo
Aug 25 '15 at 12:29
I would at least set USB emulation to on if it is not already set, I assumed that GRUB would use the BIOS to read the data from USB, but I am not 100% sure if it does (if not, some new USB chipset might be the problem).
– Anthon
Aug 25 '15 at 12:35
Your laptop has partly succeeded in its attempt to boot the live USB otherwise you wouldn't see the GRUB prompt. But GRUB hasn't been able to load the kernel so it can't go any further. Usually that sort of message happens when the kernel &/or other essential boot files aren't where GRUB expects them, or if the disk they're on is unreadable for some reason. My guess is that the system has "ejected" the USB after it's started to boot from it. You can see what partitions are available using the GRUB2
ls
command (but I don't know the details since I use GRUB Legacy).– PM 2Ring
Aug 25 '15 at 12:48
Another option that may be worth trying is to use a Live USB that uses a different bootloader, eg Grub4DOS or syslinux. Puppy Linux is a very compact distro (~130 MB) that uses syslinux by default. It's slightly non-standard so it doesn't play well with generic software that creates live USBs from bootable .iso file (like UNetbootin). But it's easy to create a live USB in a running Puppy system.
– PM 2Ring
Aug 25 '15 at 12:54