Can't boot after upgrading from 16.04 to 18.04
I tried to upgrade from Ubuntu 16.04 to Ubuntu 18.04 this morning. Everything went alright, except when the system finished upgrading and tried to reboot it could not enter the desktop environment and got stuck at a purple screen with 'ubuntu' and five dots below it. It lasted for about 5 hours when I realized that something probably had gone wrong.
boot upgrade
edited Jan 5 at 10:15
karel
58.3k12128146
asked Jan 5 at 9:56
bob wongbob wong
82
add a comment |
I tried to upgrade from Ubuntu 16.04 to Ubuntu 18.04 this morning. Everything went alright, except when the system finished upgrading and tried to reboot it could not enter the desktop environment and got stuck at a purple screen with 'ubuntu' and five dots below it. It lasted for about 5 hours when I realized that something probably had gone wrong.
boot upgrade
edited Jan 5 at 10:15
karel
58.3k12128146
asked Jan 5 at 9:56
bob wongbob wong
82
add a comment |
I tried to upgrade from Ubuntu 16.04 to Ubuntu 18.04 this morning. Everything went alright, except when the system finished upgrading and tried to reboot it could not enter the desktop environment and got stuck at a purple screen with 'ubuntu' and five dots below it. It lasted for about 5 hours when I realized that something probably had gone wrong.
boot upgrade
edited Jan 5 at 10:15
karel
58.3k12128146
asked Jan 5 at 9:56
bob wongbob wong
82
I tried to upgrade from Ubuntu 16.04 to Ubuntu 18.04 this morning. Everything went alright, except when the system finished upgrading and tried to reboot it could not enter the desktop environment and got stuck at a purple screen with 'ubuntu' and five dots below it. It lasted for about 5 hours when I realized that something probably had gone wrong.
boot upgrade
boot upgrade
edited Jan 5 at 10:15
karel
58.3k12128146
asked Jan 5 at 9:56
bob wongbob wong
82
edited Jan 5 at 10:15
karel
58.3k12128146
asked Jan 5 at 9:56
bob wongbob wong
82
edited Jan 5 at 10:15
karel
58.3k12128146
edited Jan 5 at 10:15
karel
58.3k12128146
edited Jan 5 at 10:15
karel
58.3k12128146
58.3k12128146
asked Jan 5 at 9:56
bob wongbob wong
82
asked Jan 5 at 9:56
bob wongbob wong
82
asked Jan 5 at 9:56
bob wongbob wong
82
82
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Ubuntu 18.04 was not booting to the desktop environment because there was a problem with the Nvidia graphics driver. The computer has two GPUs, an integrated Intel GPU and a discrete Nvidia GTX 1050 graphics card. After changing the custom GPU to Intel in the BIOS/UEFI setup utility, it just worked.
Install proprietary Nvidia GTX 1050 graphics driver
Uninstall the existing proprietary Nvidia graphics driver and reboot before trying to automatically install the proprietary Nvidia graphics driver in Ubuntu 18.04. Don't uninstall the open source Nouveau graphics driver. The proprietary Nvidia graphics driver for the Nvidia GTX 1050 GPU can be installed in Ubuntu 18.04 from the terminal or console with the following commands:
sudo ubuntu-drivers autoinstall
sudo reboot
When installing a proprietary graphics driver, it is not necessary to uninstall the built-in Nouveau open source graphics driver. The two graphics drivers can be installed alongside each other allowing the open source graphics driver to be used as a fallback alternative in case there is a problem using the proprietary graphics driver.
The ubuntu-drivers autoinstall command installs drivers that are appropriate for automatic installation including their dependencies, and the Nvidia driver will also be updated automatically when an update is available.
answered Jan 5 at 9:58
karelkarel
58.3k12128146
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to#and you can run commands that require root permissions without prefacing them with sudo. For example, instead ofsudo apt install lightdmtypeapt install lightdm
– karel
Jan 5 at 11:18
|
show 5 more comments
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
add a comment |
The old machine I was using did this same thing, I realised it was because it's only 32 bit capable and 18.x is 64 bit
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
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%2f1107132%2fcant-boot-after-upgrading-from-16-04-to-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ubuntu 18.04 was not booting to the desktop environment because there was a problem with the Nvidia graphics driver. The computer has two GPUs, an integrated Intel GPU and a discrete Nvidia GTX 1050 graphics card. After changing the custom GPU to Intel in the BIOS/UEFI setup utility, it just worked.
Install proprietary Nvidia GTX 1050 graphics driver
Uninstall the existing proprietary Nvidia graphics driver and reboot before trying to automatically install the proprietary Nvidia graphics driver in Ubuntu 18.04. Don't uninstall the open source Nouveau graphics driver. The proprietary Nvidia graphics driver for the Nvidia GTX 1050 GPU can be installed in Ubuntu 18.04 from the terminal or console with the following commands:
sudo ubuntu-drivers autoinstall
sudo reboot
When installing a proprietary graphics driver, it is not necessary to uninstall the built-in Nouveau open source graphics driver. The two graphics drivers can be installed alongside each other allowing the open source graphics driver to be used as a fallback alternative in case there is a problem using the proprietary graphics driver.
The ubuntu-drivers autoinstall command installs drivers that are appropriate for automatic installation including their dependencies, and the Nvidia driver will also be updated automatically when an update is available.
answered Jan 5 at 9:58
karelkarel
58.3k12128146
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to#and you can run commands that require root permissions without prefacing them with sudo. For example, instead ofsudo apt install lightdmtypeapt install lightdm
– karel
Jan 5 at 11:18
|
show 5 more comments
Ubuntu 18.04 was not booting to the desktop environment because there was a problem with the Nvidia graphics driver. The computer has two GPUs, an integrated Intel GPU and a discrete Nvidia GTX 1050 graphics card. After changing the custom GPU to Intel in the BIOS/UEFI setup utility, it just worked.
Install proprietary Nvidia GTX 1050 graphics driver
Uninstall the existing proprietary Nvidia graphics driver and reboot before trying to automatically install the proprietary Nvidia graphics driver in Ubuntu 18.04. Don't uninstall the open source Nouveau graphics driver. The proprietary Nvidia graphics driver for the Nvidia GTX 1050 GPU can be installed in Ubuntu 18.04 from the terminal or console with the following commands:
sudo ubuntu-drivers autoinstall
sudo reboot
When installing a proprietary graphics driver, it is not necessary to uninstall the built-in Nouveau open source graphics driver. The two graphics drivers can be installed alongside each other allowing the open source graphics driver to be used as a fallback alternative in case there is a problem using the proprietary graphics driver.
The ubuntu-drivers autoinstall command installs drivers that are appropriate for automatic installation including their dependencies, and the Nvidia driver will also be updated automatically when an update is available.
answered Jan 5 at 9:58
karelkarel
58.3k12128146
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to#and you can run commands that require root permissions without prefacing them with sudo. For example, instead ofsudo apt install lightdmtypeapt install lightdm
– karel
Jan 5 at 11:18
|
show 5 more comments
Ubuntu 18.04 was not booting to the desktop environment because there was a problem with the Nvidia graphics driver. The computer has two GPUs, an integrated Intel GPU and a discrete Nvidia GTX 1050 graphics card. After changing the custom GPU to Intel in the BIOS/UEFI setup utility, it just worked.
Install proprietary Nvidia GTX 1050 graphics driver
Uninstall the existing proprietary Nvidia graphics driver and reboot before trying to automatically install the proprietary Nvidia graphics driver in Ubuntu 18.04. Don't uninstall the open source Nouveau graphics driver. The proprietary Nvidia graphics driver for the Nvidia GTX 1050 GPU can be installed in Ubuntu 18.04 from the terminal or console with the following commands:
sudo ubuntu-drivers autoinstall
sudo reboot
When installing a proprietary graphics driver, it is not necessary to uninstall the built-in Nouveau open source graphics driver. The two graphics drivers can be installed alongside each other allowing the open source graphics driver to be used as a fallback alternative in case there is a problem using the proprietary graphics driver.
The ubuntu-drivers autoinstall command installs drivers that are appropriate for automatic installation including their dependencies, and the Nvidia driver will also be updated automatically when an update is available.
answered Jan 5 at 9:58
karelkarel
58.3k12128146
Ubuntu 18.04 was not booting to the desktop environment because there was a problem with the Nvidia graphics driver. The computer has two GPUs, an integrated Intel GPU and a discrete Nvidia GTX 1050 graphics card. After changing the custom GPU to Intel in the BIOS/UEFI setup utility, it just worked.
Install proprietary Nvidia GTX 1050 graphics driver
Uninstall the existing proprietary Nvidia graphics driver and reboot before trying to automatically install the proprietary Nvidia graphics driver in Ubuntu 18.04. Don't uninstall the open source Nouveau graphics driver. The proprietary Nvidia graphics driver for the Nvidia GTX 1050 GPU can be installed in Ubuntu 18.04 from the terminal or console with the following commands:
sudo ubuntu-drivers autoinstall
sudo reboot
When installing a proprietary graphics driver, it is not necessary to uninstall the built-in Nouveau open source graphics driver. The two graphics drivers can be installed alongside each other allowing the open source graphics driver to be used as a fallback alternative in case there is a problem using the proprietary graphics driver.
The ubuntu-drivers autoinstall command installs drivers that are appropriate for automatic installation including their dependencies, and the Nvidia driver will also be updated automatically when an update is available.
answered Jan 5 at 9:58
karelkarel
58.3k12128146
edited Jan 8 at 4:05
answered Jan 5 at 9:58
karelkarel
58.3k12128146
answered Jan 5 at 9:58
karelkarel
58.3k12128146
answered Jan 5 at 9:58
karelkarel
58.3k12128146
58.3k12128146
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to#and you can run commands that require root permissions without prefacing them with sudo. For example, instead ofsudo apt install lightdmtypeapt install lightdm
– karel
Jan 5 at 11:18
|
show 5 more comments
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to#and you can run commands that require root permissions without prefacing them with sudo. For example, instead ofsudo apt install lightdmtypeapt install lightdm
– karel
Jan 5 at 11:18
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Did you mean I need to recover the old kernel using GRUB. I'll have a try.
– bob wong
Jan 5 at 10:23
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Recovering an old kernel with grub will only make matters worse because the kernel is OK, otherwise it wouldn't have shown the purple screen with the 5 dots. After you get into recovery mode the best option to try first is the failsafeX option which may be able to get into a low resolution GUI desktop environment. Then you can fix the rest of it from the terminal.
– karel
Jan 5 at 10:28
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Got it. Thanks a lot.
– bob wong
Jan 5 at 10:30
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Well, it did not give an error message. But it just did not work. I tried the recovery mode with clean, dpkg and grub. After it, I tried both resume from recovery mode and failsafeX. It just gave me some messages about some information of my shadowsocks(not an error) and stuck there.
– bob wong
Jan 5 at 11:10
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to
# and you can run commands that require root permissions without prefacing them with sudo. For example, instead of sudo apt install lightdm type apt install lightdm– karel
Jan 5 at 11:18
Instead of entering the virtual console it would be easier for you to select the root option from recovery mode. After selecting root the command prompt changes to
# and you can run commands that require root permissions without prefacing them with sudo. For example, instead of sudo apt install lightdm type apt install lightdm– karel
Jan 5 at 11:18
|
show 5 more comments
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
add a comment |
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
add a comment |
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
answered Jan 6 at 1:35
heynnemaheynnema
18.3k22054
18.3k22054
add a comment |
add a comment |
The old machine I was using did this same thing, I realised it was because it's only 32 bit capable and 18.x is 64 bit
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
add a comment |
The old machine I was using did this same thing, I realised it was because it's only 32 bit capable and 18.x is 64 bit
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
add a comment |
The old machine I was using did this same thing, I realised it was because it's only 32 bit capable and 18.x is 64 bit
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
The old machine I was using did this same thing, I realised it was because it's only 32 bit capable and 18.x is 64 bit
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
answered Jan 6 at 1:52
CJ BoutinCJ Boutin
12
12
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%2f1107132%2fcant-boot-after-upgrading-from-16-04-to-18-04%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
