Ubuntu 18.04 boots to blank purple screen
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
My first install of Ubuntu was 16.04 with the only problems being with Ubuntu not wanting to play nice with my Nvidia graphics card. I later upgraded to 17.10 with no problems. I just now upgraded to 18.04. All appeared to go fine until the upgrade process finished and it asked to restart. I said okay. The system then rebooted to a blank purple screen.
If I forcibly power down and then turn power on I get to a grub menu. I can get in if I select an alternate boot option but when I shut down, the next time I boot up I'm right back at the blank purple screen.
On one of these alternate boots, I went in to XDiagnostics and turned on the options for extra debug logging and turned off the bootloader graphics. I can now see that Ubuntu apparently goes into an infinite hang on "a start job is running for detect the available gpus and deal with any system changes"
Is there a definitive fix for this?
If there is not a fix for this then how can I downgrade the install (without loss of data) to 17.10 which worked just fine?
Thanks.
boot nvidia 18.04 gpu
asked May 15 '18 at 5:52
JimJim
113
add a comment |
My first install of Ubuntu was 16.04 with the only problems being with Ubuntu not wanting to play nice with my Nvidia graphics card. I later upgraded to 17.10 with no problems. I just now upgraded to 18.04. All appeared to go fine until the upgrade process finished and it asked to restart. I said okay. The system then rebooted to a blank purple screen.
If I forcibly power down and then turn power on I get to a grub menu. I can get in if I select an alternate boot option but when I shut down, the next time I boot up I'm right back at the blank purple screen.
On one of these alternate boots, I went in to XDiagnostics and turned on the options for extra debug logging and turned off the bootloader graphics. I can now see that Ubuntu apparently goes into an infinite hang on "a start job is running for detect the available gpus and deal with any system changes"
Is there a definitive fix for this?
If there is not a fix for this then how can I downgrade the install (without loss of data) to 17.10 which worked just fine?
Thanks.
boot nvidia 18.04 gpu
asked May 15 '18 at 5:52
JimJim
113
Seem like this might be the same issue as inscribed here: askubuntu.com/questions/1036406/…
– dhuyvetter
May 15 '18 at 8:36
Similar but not the same. Searching tells me this is a wide spread problem that really needs to be addressed. I find it surprising that this error is happening since my Nvidia card is 4 years old and Nvidia is a key player in the GPU market.
– Jim
May 16 '18 at 17:17
add a comment |
My first install of Ubuntu was 16.04 with the only problems being with Ubuntu not wanting to play nice with my Nvidia graphics card. I later upgraded to 17.10 with no problems. I just now upgraded to 18.04. All appeared to go fine until the upgrade process finished and it asked to restart. I said okay. The system then rebooted to a blank purple screen.
If I forcibly power down and then turn power on I get to a grub menu. I can get in if I select an alternate boot option but when I shut down, the next time I boot up I'm right back at the blank purple screen.
On one of these alternate boots, I went in to XDiagnostics and turned on the options for extra debug logging and turned off the bootloader graphics. I can now see that Ubuntu apparently goes into an infinite hang on "a start job is running for detect the available gpus and deal with any system changes"
Is there a definitive fix for this?
If there is not a fix for this then how can I downgrade the install (without loss of data) to 17.10 which worked just fine?
Thanks.
boot nvidia 18.04 gpu
asked May 15 '18 at 5:52
JimJim
113
My first install of Ubuntu was 16.04 with the only problems being with Ubuntu not wanting to play nice with my Nvidia graphics card. I later upgraded to 17.10 with no problems. I just now upgraded to 18.04. All appeared to go fine until the upgrade process finished and it asked to restart. I said okay. The system then rebooted to a blank purple screen.
If I forcibly power down and then turn power on I get to a grub menu. I can get in if I select an alternate boot option but when I shut down, the next time I boot up I'm right back at the blank purple screen.
On one of these alternate boots, I went in to XDiagnostics and turned on the options for extra debug logging and turned off the bootloader graphics. I can now see that Ubuntu apparently goes into an infinite hang on "a start job is running for detect the available gpus and deal with any system changes"
Is there a definitive fix for this?
If there is not a fix for this then how can I downgrade the install (without loss of data) to 17.10 which worked just fine?
Thanks.
boot nvidia 18.04 gpu
boot nvidia 18.04 gpu
asked May 15 '18 at 5:52
JimJim
113
asked May 15 '18 at 5:52
JimJim
113
asked May 15 '18 at 5:52
JimJim
113
asked May 15 '18 at 5:52
JimJim
113
asked May 15 '18 at 5:52
JimJim
113
113
Seem like this might be the same issue as inscribed here: askubuntu.com/questions/1036406/…
– dhuyvetter
May 15 '18 at 8:36
Similar but not the same. Searching tells me this is a wide spread problem that really needs to be addressed. I find it surprising that this error is happening since my Nvidia card is 4 years old and Nvidia is a key player in the GPU market.
– Jim
May 16 '18 at 17:17
add a comment |
Seem like this might be the same issue as inscribed here: askubuntu.com/questions/1036406/…
– dhuyvetter
May 15 '18 at 8:36
Similar but not the same. Searching tells me this is a wide spread problem that really needs to be addressed. I find it surprising that this error is happening since my Nvidia card is 4 years old and Nvidia is a key player in the GPU market.
– Jim
May 16 '18 at 17:17
Seem like this might be the same issue as inscribed here: askubuntu.com/questions/1036406/…
– dhuyvetter
May 15 '18 at 8:36
Seem like this might be the same issue as inscribed here: askubuntu.com/questions/1036406/…
– dhuyvetter
May 15 '18 at 8:36
Similar but not the same. Searching tells me this is a wide spread problem that really needs to be addressed. I find it surprising that this error is happening since my Nvidia card is 4 years old and Nvidia is a key player in the GPU market.
– Jim
May 16 '18 at 17:17
Similar but not the same. Searching tells me this is a wide spread problem that really needs to be addressed. I find it surprising that this error is happening since my Nvidia card is 4 years old and Nvidia is a key player in the GPU market.
– Jim
May 16 '18 at 17:17
add a comment |
1 Answer
1
active
oldest
votes
Given that downgrading is not an option and given that I would prefer not to have to reinstall Ubuntu and then reinstall and reconfigure all the apps I've already set up, as a work around I am going to use the following solution which works for me:
Press right shift key when booting up.
When the Grub menu appears, select "advanced options for Ubuntu" and press enter.
Select "Ubuntu with Linux 4.13.0-41-generic" and press enter.
Log in.
It seems that the problem is with the 4.15 kernel and since I can't undo the upgrade from 17.1 to 18.04, I can use this method to fall back to the 4.13 kernel.
Is it a kludge? Yes. But one that is certainly preferable to a complete re-install.
answered May 18 '18 at 1:14
JimJim
113
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%2f1036378%2fubuntu-18-04-boots-to-blank-purple-screen%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
Given that downgrading is not an option and given that I would prefer not to have to reinstall Ubuntu and then reinstall and reconfigure all the apps I've already set up, as a work around I am going to use the following solution which works for me:
Press right shift key when booting up.
When the Grub menu appears, select "advanced options for Ubuntu" and press enter.
Select "Ubuntu with Linux 4.13.0-41-generic" and press enter.
Log in.
It seems that the problem is with the 4.15 kernel and since I can't undo the upgrade from 17.1 to 18.04, I can use this method to fall back to the 4.13 kernel.
Is it a kludge? Yes. But one that is certainly preferable to a complete re-install.
answered May 18 '18 at 1:14
JimJim
113
add a comment |
Given that downgrading is not an option and given that I would prefer not to have to reinstall Ubuntu and then reinstall and reconfigure all the apps I've already set up, as a work around I am going to use the following solution which works for me:
Press right shift key when booting up.
When the Grub menu appears, select "advanced options for Ubuntu" and press enter.
Select "Ubuntu with Linux 4.13.0-41-generic" and press enter.
Log in.
It seems that the problem is with the 4.15 kernel and since I can't undo the upgrade from 17.1 to 18.04, I can use this method to fall back to the 4.13 kernel.
Is it a kludge? Yes. But one that is certainly preferable to a complete re-install.
answered May 18 '18 at 1:14
JimJim
113
add a comment |
Given that downgrading is not an option and given that I would prefer not to have to reinstall Ubuntu and then reinstall and reconfigure all the apps I've already set up, as a work around I am going to use the following solution which works for me:
Press right shift key when booting up.
When the Grub menu appears, select "advanced options for Ubuntu" and press enter.
Select "Ubuntu with Linux 4.13.0-41-generic" and press enter.
Log in.
It seems that the problem is with the 4.15 kernel and since I can't undo the upgrade from 17.1 to 18.04, I can use this method to fall back to the 4.13 kernel.
Is it a kludge? Yes. But one that is certainly preferable to a complete re-install.
answered May 18 '18 at 1:14
JimJim
113
Given that downgrading is not an option and given that I would prefer not to have to reinstall Ubuntu and then reinstall and reconfigure all the apps I've already set up, as a work around I am going to use the following solution which works for me:
Press right shift key when booting up.
When the Grub menu appears, select "advanced options for Ubuntu" and press enter.
Select "Ubuntu with Linux 4.13.0-41-generic" and press enter.
Log in.
It seems that the problem is with the 4.15 kernel and since I can't undo the upgrade from 17.1 to 18.04, I can use this method to fall back to the 4.13 kernel.
Is it a kludge? Yes. But one that is certainly preferable to a complete re-install.
answered May 18 '18 at 1:14
JimJim
113
answered May 18 '18 at 1:14
JimJim
113
answered May 18 '18 at 1:14
JimJim
113
answered May 18 '18 at 1:14
JimJim
113
113
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.
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%2f1036378%2fubuntu-18-04-boots-to-blank-purple-screen%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
Seem like this might be the same issue as inscribed here: askubuntu.com/questions/1036406/…
– dhuyvetter
May 15 '18 at 8:36
Similar but not the same. Searching tells me this is a wide spread problem that really needs to be addressed. I find it surprising that this error is happening since my Nvidia card is 4 years old and Nvidia is a key player in the GPU market.
– Jim
May 16 '18 at 17:17