Trying to Dual Boot Windows 10 and Ubuntu 18.04.1
I'm unable to successful install Ubuntu 18.04.1 on my new desktop. I have Windows 10 Home installed and running smoothly, I successfully partitioned my HDD and SSD in halves so there is plenty of space to install Ubuntu, and the ISO I burned on my 8GB flashdrive works just fine when I boot my laptop from it.
When I try to boot my desktop from it, I get the normal grub menu, but when I select Install Ubuntu it doesn't work properly.
The first thing that happens is a bunch of lines on the screen saying "Completion-Wait loop timed out".
Then it flashes and I get a much longer string of messages, most of which is letters and numbers and symbols strung together.
At the end is says "end Kernel panic - not syncing: Fatal exception in interrupt"
Now, a few times when I've tried booting my desktop, it made it all the way to the Ubuntu loading screen. That quite got my hopes up, but it crashed and went to some similar black screen full of strange messages.
Secure boot is disabled in my BIOS. I tried editing the "Install Ubuntu" command in grub and adding "nomodeset" but that didn't work.
EDIT:
I have successfully dual booted my system now and determined the source of my problem.
I'm running AMD Ryzen 3 2200g CPU and Gigabyte Radeon RX570 GPU, and they don't always play nice, I think due to the processor having integrated graphics. I removed my GPU and it booted from my ISO stick first try with no problems.
When I plug my GPU back in it won't boot up again though. I have installed the latest and greatest drivers from AMD for Ubuntu 18.04 but it still won't boot up in Ubuntu when I have my GPU connected.
dual-boot 18.04 system-installation live-usb
asked Dec 30 '18 at 23:17
G Ghost
11
New contributor
G Ghost 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 |
I'm unable to successful install Ubuntu 18.04.1 on my new desktop. I have Windows 10 Home installed and running smoothly, I successfully partitioned my HDD and SSD in halves so there is plenty of space to install Ubuntu, and the ISO I burned on my 8GB flashdrive works just fine when I boot my laptop from it.
When I try to boot my desktop from it, I get the normal grub menu, but when I select Install Ubuntu it doesn't work properly.
The first thing that happens is a bunch of lines on the screen saying "Completion-Wait loop timed out".
Then it flashes and I get a much longer string of messages, most of which is letters and numbers and symbols strung together.
At the end is says "end Kernel panic - not syncing: Fatal exception in interrupt"
Now, a few times when I've tried booting my desktop, it made it all the way to the Ubuntu loading screen. That quite got my hopes up, but it crashed and went to some similar black screen full of strange messages.
Secure boot is disabled in my BIOS. I tried editing the "Install Ubuntu" command in grub and adding "nomodeset" but that didn't work.
EDIT:
I have successfully dual booted my system now and determined the source of my problem.
I'm running AMD Ryzen 3 2200g CPU and Gigabyte Radeon RX570 GPU, and they don't always play nice, I think due to the processor having integrated graphics. I removed my GPU and it booted from my ISO stick first try with no problems.
When I plug my GPU back in it won't boot up again though. I have installed the latest and greatest drivers from AMD for Ubuntu 18.04 but it still won't boot up in Ubuntu when I have my GPU connected.
dual-boot 18.04 system-installation live-usb
asked Dec 30 '18 at 23:17
G Ghost
11
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
What kind of computer is it?
– Kristopher Ives
Dec 31 '18 at 0:03
add a comment |
I'm unable to successful install Ubuntu 18.04.1 on my new desktop. I have Windows 10 Home installed and running smoothly, I successfully partitioned my HDD and SSD in halves so there is plenty of space to install Ubuntu, and the ISO I burned on my 8GB flashdrive works just fine when I boot my laptop from it.
When I try to boot my desktop from it, I get the normal grub menu, but when I select Install Ubuntu it doesn't work properly.
The first thing that happens is a bunch of lines on the screen saying "Completion-Wait loop timed out".
Then it flashes and I get a much longer string of messages, most of which is letters and numbers and symbols strung together.
At the end is says "end Kernel panic - not syncing: Fatal exception in interrupt"
Now, a few times when I've tried booting my desktop, it made it all the way to the Ubuntu loading screen. That quite got my hopes up, but it crashed and went to some similar black screen full of strange messages.
Secure boot is disabled in my BIOS. I tried editing the "Install Ubuntu" command in grub and adding "nomodeset" but that didn't work.
EDIT:
I have successfully dual booted my system now and determined the source of my problem.
I'm running AMD Ryzen 3 2200g CPU and Gigabyte Radeon RX570 GPU, and they don't always play nice, I think due to the processor having integrated graphics. I removed my GPU and it booted from my ISO stick first try with no problems.
When I plug my GPU back in it won't boot up again though. I have installed the latest and greatest drivers from AMD for Ubuntu 18.04 but it still won't boot up in Ubuntu when I have my GPU connected.
dual-boot 18.04 system-installation live-usb
asked Dec 30 '18 at 23:17
G Ghost
11
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm unable to successful install Ubuntu 18.04.1 on my new desktop. I have Windows 10 Home installed and running smoothly, I successfully partitioned my HDD and SSD in halves so there is plenty of space to install Ubuntu, and the ISO I burned on my 8GB flashdrive works just fine when I boot my laptop from it.
When I try to boot my desktop from it, I get the normal grub menu, but when I select Install Ubuntu it doesn't work properly.
The first thing that happens is a bunch of lines on the screen saying "Completion-Wait loop timed out".
Then it flashes and I get a much longer string of messages, most of which is letters and numbers and symbols strung together.
At the end is says "end Kernel panic - not syncing: Fatal exception in interrupt"
Now, a few times when I've tried booting my desktop, it made it all the way to the Ubuntu loading screen. That quite got my hopes up, but it crashed and went to some similar black screen full of strange messages.
Secure boot is disabled in my BIOS. I tried editing the "Install Ubuntu" command in grub and adding "nomodeset" but that didn't work.
EDIT:
I have successfully dual booted my system now and determined the source of my problem.
I'm running AMD Ryzen 3 2200g CPU and Gigabyte Radeon RX570 GPU, and they don't always play nice, I think due to the processor having integrated graphics. I removed my GPU and it booted from my ISO stick first try with no problems.
When I plug my GPU back in it won't boot up again though. I have installed the latest and greatest drivers from AMD for Ubuntu 18.04 but it still won't boot up in Ubuntu when I have my GPU connected.
dual-boot 18.04 system-installation live-usb
dual-boot 18.04 system-installation live-usb
asked Dec 30 '18 at 23:17
G Ghost
11
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 30 '18 at 23:17
G Ghost
11
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Jan 2 at 4:59
asked Dec 30 '18 at 23:17
G Ghost
11
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 30 '18 at 23:17
G Ghost
11
asked Dec 30 '18 at 23:17
G Ghost
11
11
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
G Ghost is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
What kind of computer is it?
– Kristopher Ives
Dec 31 '18 at 0:03
add a comment |
What kind of computer is it?
– Kristopher Ives
Dec 31 '18 at 0:03
What kind of computer is it?
– Kristopher Ives
Dec 31 '18 at 0:03
What kind of computer is it?
– Kristopher Ives
Dec 31 '18 at 0:03
add a comment |
1 Answer
1
active
oldest
votes
Some systems have strange support for UEFI modes which can be resolved by either updating the system firmware or worked around by either running with a special parameter or running in "legacy" mode to disabled UEFI features.
If you want to keep UEFI mode and try to boot Linux, add this to your boot options in GRUB like you tried with the nomodeset option:
amd_iommu=off
Instead if you want to avoid the whole UEFI problem simply enable "legacy" mode in in your BIOS options. Note that if you enable legacy mode you may have to create a different USB thumb drive when booting.
Source: https://bbs.archlinux.org/viewtopic.php?id=224265
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
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
});
}
});
G Ghost is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1105714%2ftrying-to-dual-boot-windows-10-and-ubuntu-18-04-1%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
Some systems have strange support for UEFI modes which can be resolved by either updating the system firmware or worked around by either running with a special parameter or running in "legacy" mode to disabled UEFI features.
If you want to keep UEFI mode and try to boot Linux, add this to your boot options in GRUB like you tried with the nomodeset option:
amd_iommu=off
Instead if you want to avoid the whole UEFI problem simply enable "legacy" mode in in your BIOS options. Note that if you enable legacy mode you may have to create a different USB thumb drive when booting.
Source: https://bbs.archlinux.org/viewtopic.php?id=224265
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
add a comment |
Some systems have strange support for UEFI modes which can be resolved by either updating the system firmware or worked around by either running with a special parameter or running in "legacy" mode to disabled UEFI features.
If you want to keep UEFI mode and try to boot Linux, add this to your boot options in GRUB like you tried with the nomodeset option:
amd_iommu=off
Instead if you want to avoid the whole UEFI problem simply enable "legacy" mode in in your BIOS options. Note that if you enable legacy mode you may have to create a different USB thumb drive when booting.
Source: https://bbs.archlinux.org/viewtopic.php?id=224265
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
add a comment |
Some systems have strange support for UEFI modes which can be resolved by either updating the system firmware or worked around by either running with a special parameter or running in "legacy" mode to disabled UEFI features.
If you want to keep UEFI mode and try to boot Linux, add this to your boot options in GRUB like you tried with the nomodeset option:
amd_iommu=off
Instead if you want to avoid the whole UEFI problem simply enable "legacy" mode in in your BIOS options. Note that if you enable legacy mode you may have to create a different USB thumb drive when booting.
Source: https://bbs.archlinux.org/viewtopic.php?id=224265
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
Some systems have strange support for UEFI modes which can be resolved by either updating the system firmware or worked around by either running with a special parameter or running in "legacy" mode to disabled UEFI features.
If you want to keep UEFI mode and try to boot Linux, add this to your boot options in GRUB like you tried with the nomodeset option:
amd_iommu=off
Instead if you want to avoid the whole UEFI problem simply enable "legacy" mode in in your BIOS options. Note that if you enable legacy mode you may have to create a different USB thumb drive when booting.
Source: https://bbs.archlinux.org/viewtopic.php?id=224265
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
answered Dec 31 '18 at 0:08
Kristopher Ives
1,8181016
1,8181016
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
add a comment |
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
If Widnows is UEFI on gpt drive, do not enable CSM/Legacy/BIOS boot mode. Windows & Ubuntu need to be in same boot mode either both UEFI or both BIOS.
– oldfred
Dec 31 '18 at 4:34
add a comment |
G Ghost is a new contributor. Be nice, and check out our Code of Conduct.
G Ghost is a new contributor. Be nice, and check out our Code of Conduct.
G Ghost is a new contributor. Be nice, and check out our Code of Conduct.
G Ghost is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1105714%2ftrying-to-dual-boot-windows-10-and-ubuntu-18-04-1%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
What kind of computer is it?
– Kristopher Ives
Dec 31 '18 at 0:03