Ubuntu 18.04 is stuck at loading screen after new installation
I installed Ubuntu 18.04 from a bootable USB last night, but when I tried to login to the operating system I got stuck at a ubuntu loading screen with five dots on it.
I have seen an older question where it might seem to be a graphics problem, and the solution mentioned was to press Ctrl +Alt+f1,f2,f3 etc. to go the shell, but when I do that the shell is not showing up.
What else can I try?
boot
|
show 1 more comment
I installed Ubuntu 18.04 from a bootable USB last night, but when I tried to login to the operating system I got stuck at a ubuntu loading screen with five dots on it.
I have seen an older question where it might seem to be a graphics problem, and the solution mentioned was to press Ctrl +Alt+f1,f2,f3 etc. to go the shell, but when I do that the shell is not showing up.
What else can I try?
boot
If you pressescape
, can you see anything? If you hard reset (using the power button), and then boot in non-quiet mode by editing the selected item (presse
), removingquiet splash
and pressing ctrl-x, is anything interesting displayed on screen?
– Iain Lane
May 8 '18 at 12:21
I did it like you said but still it is stuck on loading.
– Wasil Khan
May 8 '18 at 14:14
I didn't expect it to fix the problem. It should make some text be displayed and that text might contain a clue.
– Iain Lane
May 8 '18 at 16:01
It didn't give any error but after deleting quiet splash from the grub menu it runs quiet well in the recovery mode. What do you suspect? What should I do now?
– Wasil Khan
May 8 '18 at 16:14
You mean it made the computer boot? Perhaps if you runjournalctl
you can see evidence of a problem?
– Iain Lane
May 10 '18 at 15:39
|
show 1 more comment
I installed Ubuntu 18.04 from a bootable USB last night, but when I tried to login to the operating system I got stuck at a ubuntu loading screen with five dots on it.
I have seen an older question where it might seem to be a graphics problem, and the solution mentioned was to press Ctrl +Alt+f1,f2,f3 etc. to go the shell, but when I do that the shell is not showing up.
What else can I try?
boot
I installed Ubuntu 18.04 from a bootable USB last night, but when I tried to login to the operating system I got stuck at a ubuntu loading screen with five dots on it.
I have seen an older question where it might seem to be a graphics problem, and the solution mentioned was to press Ctrl +Alt+f1,f2,f3 etc. to go the shell, but when I do that the shell is not showing up.
What else can I try?
boot
boot
edited Dec 7 '18 at 8:35
karel
59.7k13129151
59.7k13129151
asked May 8 '18 at 7:47
Wasil KhanWasil Khan
1113
1113
If you pressescape
, can you see anything? If you hard reset (using the power button), and then boot in non-quiet mode by editing the selected item (presse
), removingquiet splash
and pressing ctrl-x, is anything interesting displayed on screen?
– Iain Lane
May 8 '18 at 12:21
I did it like you said but still it is stuck on loading.
– Wasil Khan
May 8 '18 at 14:14
I didn't expect it to fix the problem. It should make some text be displayed and that text might contain a clue.
– Iain Lane
May 8 '18 at 16:01
It didn't give any error but after deleting quiet splash from the grub menu it runs quiet well in the recovery mode. What do you suspect? What should I do now?
– Wasil Khan
May 8 '18 at 16:14
You mean it made the computer boot? Perhaps if you runjournalctl
you can see evidence of a problem?
– Iain Lane
May 10 '18 at 15:39
|
show 1 more comment
If you pressescape
, can you see anything? If you hard reset (using the power button), and then boot in non-quiet mode by editing the selected item (presse
), removingquiet splash
and pressing ctrl-x, is anything interesting displayed on screen?
– Iain Lane
May 8 '18 at 12:21
I did it like you said but still it is stuck on loading.
– Wasil Khan
May 8 '18 at 14:14
I didn't expect it to fix the problem. It should make some text be displayed and that text might contain a clue.
– Iain Lane
May 8 '18 at 16:01
It didn't give any error but after deleting quiet splash from the grub menu it runs quiet well in the recovery mode. What do you suspect? What should I do now?
– Wasil Khan
May 8 '18 at 16:14
You mean it made the computer boot? Perhaps if you runjournalctl
you can see evidence of a problem?
– Iain Lane
May 10 '18 at 15:39
If you press
escape
, can you see anything? If you hard reset (using the power button), and then boot in non-quiet mode by editing the selected item (press e
), removing quiet splash
and pressing ctrl-x, is anything interesting displayed on screen?– Iain Lane
May 8 '18 at 12:21
If you press
escape
, can you see anything? If you hard reset (using the power button), and then boot in non-quiet mode by editing the selected item (press e
), removing quiet splash
and pressing ctrl-x, is anything interesting displayed on screen?– Iain Lane
May 8 '18 at 12:21
I did it like you said but still it is stuck on loading.
– Wasil Khan
May 8 '18 at 14:14
I did it like you said but still it is stuck on loading.
– Wasil Khan
May 8 '18 at 14:14
I didn't expect it to fix the problem. It should make some text be displayed and that text might contain a clue.
– Iain Lane
May 8 '18 at 16:01
I didn't expect it to fix the problem. It should make some text be displayed and that text might contain a clue.
– Iain Lane
May 8 '18 at 16:01
It didn't give any error but after deleting quiet splash from the grub menu it runs quiet well in the recovery mode. What do you suspect? What should I do now?
– Wasil Khan
May 8 '18 at 16:14
It didn't give any error but after deleting quiet splash from the grub menu it runs quiet well in the recovery mode. What do you suspect? What should I do now?
– Wasil Khan
May 8 '18 at 16:14
You mean it made the computer boot? Perhaps if you run
journalctl
you can see evidence of a problem?– Iain Lane
May 10 '18 at 15:39
You mean it made the computer boot? Perhaps if you run
journalctl
you can see evidence of a problem?– Iain Lane
May 10 '18 at 15:39
|
show 1 more comment
2 Answers
2
active
oldest
votes
Ubuntu 18.04 uses Wayland display server which does not work on a few systems.
Try the below steps to make the system boot normally:
- Go to recovery mode from the GRUB menu and then boot into the system. Recovery mode uses low graphics and hence will not get stuck at the splash (logo) screen.
- Once you are logged in, open a terminal (Use Ctrl+Alt+t shortcut)
Try changing the display server to Xorg in the gdm3 custom conf file using the below command and reboot the system.
sudo gedit /etc/gdm3/custom.conf
Change
#WaylandEnable=false
toWaylandEnable=false
(Basically uncommenting it).Reboot the system.
This will disable the Wayland display server and make the system to use the Xorg
display server. Your system should hopefully progress to the login screen now with a normal boot.
Let me know if this works.
Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
add a comment |
The similar stuck issue occurs when I try to restart or shutdown the system after a new installation of ubuntu 18.04.2 on my laptop.
I solved the problem by switch from Nouveau driver to Nvidia driver, using Software & Updates App, as following screenshot. The problem disappers after using Nvidia driver, so I assume there are some potential bugs in Nouveau driver.
Just for references, here is my video card info:
$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001D12sv00001D72sd00001604bc03sc02i00
vendor : NVIDIA Corporation
driver : nvidia-driver-390 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtin
$ sudo lshw -c video
# OR
$ sudo lshw -c display
*-display
description: VGA compatible controller
product: HD Graphics 620
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:4000(size=64) memory:c0000-dffff
*-display
description: 3D controller
product: GP108M [GeForce MX150]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=nvidia latency=0
resources: irq:133 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:3000(size=128)
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%2f1033463%2fubuntu-18-04-is-stuck-at-loading-screen-after-new-installation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ubuntu 18.04 uses Wayland display server which does not work on a few systems.
Try the below steps to make the system boot normally:
- Go to recovery mode from the GRUB menu and then boot into the system. Recovery mode uses low graphics and hence will not get stuck at the splash (logo) screen.
- Once you are logged in, open a terminal (Use Ctrl+Alt+t shortcut)
Try changing the display server to Xorg in the gdm3 custom conf file using the below command and reboot the system.
sudo gedit /etc/gdm3/custom.conf
Change
#WaylandEnable=false
toWaylandEnable=false
(Basically uncommenting it).Reboot the system.
This will disable the Wayland display server and make the system to use the Xorg
display server. Your system should hopefully progress to the login screen now with a normal boot.
Let me know if this works.
Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
add a comment |
Ubuntu 18.04 uses Wayland display server which does not work on a few systems.
Try the below steps to make the system boot normally:
- Go to recovery mode from the GRUB menu and then boot into the system. Recovery mode uses low graphics and hence will not get stuck at the splash (logo) screen.
- Once you are logged in, open a terminal (Use Ctrl+Alt+t shortcut)
Try changing the display server to Xorg in the gdm3 custom conf file using the below command and reboot the system.
sudo gedit /etc/gdm3/custom.conf
Change
#WaylandEnable=false
toWaylandEnable=false
(Basically uncommenting it).Reboot the system.
This will disable the Wayland display server and make the system to use the Xorg
display server. Your system should hopefully progress to the login screen now with a normal boot.
Let me know if this works.
Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
add a comment |
Ubuntu 18.04 uses Wayland display server which does not work on a few systems.
Try the below steps to make the system boot normally:
- Go to recovery mode from the GRUB menu and then boot into the system. Recovery mode uses low graphics and hence will not get stuck at the splash (logo) screen.
- Once you are logged in, open a terminal (Use Ctrl+Alt+t shortcut)
Try changing the display server to Xorg in the gdm3 custom conf file using the below command and reboot the system.
sudo gedit /etc/gdm3/custom.conf
Change
#WaylandEnable=false
toWaylandEnable=false
(Basically uncommenting it).Reboot the system.
This will disable the Wayland display server and make the system to use the Xorg
display server. Your system should hopefully progress to the login screen now with a normal boot.
Let me know if this works.
Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
Ubuntu 18.04 uses Wayland display server which does not work on a few systems.
Try the below steps to make the system boot normally:
- Go to recovery mode from the GRUB menu and then boot into the system. Recovery mode uses low graphics and hence will not get stuck at the splash (logo) screen.
- Once you are logged in, open a terminal (Use Ctrl+Alt+t shortcut)
Try changing the display server to Xorg in the gdm3 custom conf file using the below command and reboot the system.
sudo gedit /etc/gdm3/custom.conf
Change
#WaylandEnable=false
toWaylandEnable=false
(Basically uncommenting it).Reboot the system.
This will disable the Wayland display server and make the system to use the Xorg
display server. Your system should hopefully progress to the login screen now with a normal boot.
Let me know if this works.
Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux
edited Dec 14 '18 at 14:03
mature
2,1172729
2,1172729
answered Dec 7 '18 at 8:04
SanjaySanjay
113
113
add a comment |
add a comment |
The similar stuck issue occurs when I try to restart or shutdown the system after a new installation of ubuntu 18.04.2 on my laptop.
I solved the problem by switch from Nouveau driver to Nvidia driver, using Software & Updates App, as following screenshot. The problem disappers after using Nvidia driver, so I assume there are some potential bugs in Nouveau driver.
Just for references, here is my video card info:
$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001D12sv00001D72sd00001604bc03sc02i00
vendor : NVIDIA Corporation
driver : nvidia-driver-390 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtin
$ sudo lshw -c video
# OR
$ sudo lshw -c display
*-display
description: VGA compatible controller
product: HD Graphics 620
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:4000(size=64) memory:c0000-dffff
*-display
description: 3D controller
product: GP108M [GeForce MX150]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=nvidia latency=0
resources: irq:133 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:3000(size=128)
add a comment |
The similar stuck issue occurs when I try to restart or shutdown the system after a new installation of ubuntu 18.04.2 on my laptop.
I solved the problem by switch from Nouveau driver to Nvidia driver, using Software & Updates App, as following screenshot. The problem disappers after using Nvidia driver, so I assume there are some potential bugs in Nouveau driver.
Just for references, here is my video card info:
$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001D12sv00001D72sd00001604bc03sc02i00
vendor : NVIDIA Corporation
driver : nvidia-driver-390 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtin
$ sudo lshw -c video
# OR
$ sudo lshw -c display
*-display
description: VGA compatible controller
product: HD Graphics 620
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:4000(size=64) memory:c0000-dffff
*-display
description: 3D controller
product: GP108M [GeForce MX150]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=nvidia latency=0
resources: irq:133 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:3000(size=128)
add a comment |
The similar stuck issue occurs when I try to restart or shutdown the system after a new installation of ubuntu 18.04.2 on my laptop.
I solved the problem by switch from Nouveau driver to Nvidia driver, using Software & Updates App, as following screenshot. The problem disappers after using Nvidia driver, so I assume there are some potential bugs in Nouveau driver.
Just for references, here is my video card info:
$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001D12sv00001D72sd00001604bc03sc02i00
vendor : NVIDIA Corporation
driver : nvidia-driver-390 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtin
$ sudo lshw -c video
# OR
$ sudo lshw -c display
*-display
description: VGA compatible controller
product: HD Graphics 620
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:4000(size=64) memory:c0000-dffff
*-display
description: 3D controller
product: GP108M [GeForce MX150]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=nvidia latency=0
resources: irq:133 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:3000(size=128)
The similar stuck issue occurs when I try to restart or shutdown the system after a new installation of ubuntu 18.04.2 on my laptop.
I solved the problem by switch from Nouveau driver to Nvidia driver, using Software & Updates App, as following screenshot. The problem disappers after using Nvidia driver, so I assume there are some potential bugs in Nouveau driver.
Just for references, here is my video card info:
$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001D12sv00001D72sd00001604bc03sc02i00
vendor : NVIDIA Corporation
driver : nvidia-driver-390 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtin
$ sudo lshw -c video
# OR
$ sudo lshw -c display
*-display
description: VGA compatible controller
product: HD Graphics 620
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:128 memory:b2000000-b2ffffff memory:c0000000-cfffffff ioport:4000(size=64) memory:c0000-dffff
*-display
description: 3D controller
product: GP108M [GeForce MX150]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=nvidia latency=0
resources: irq:133 memory:b3000000-b3ffffff memory:a0000000-afffffff memory:b0000000-b1ffffff ioport:3000(size=128)
answered 6 mins ago
YaOzIYaOzI
1313
1313
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%2f1033463%2fubuntu-18-04-is-stuck-at-loading-screen-after-new-installation%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
If you press
escape
, can you see anything? If you hard reset (using the power button), and then boot in non-quiet mode by editing the selected item (presse
), removingquiet splash
and pressing ctrl-x, is anything interesting displayed on screen?– Iain Lane
May 8 '18 at 12:21
I did it like you said but still it is stuck on loading.
– Wasil Khan
May 8 '18 at 14:14
I didn't expect it to fix the problem. It should make some text be displayed and that text might contain a clue.
– Iain Lane
May 8 '18 at 16:01
It didn't give any error but after deleting quiet splash from the grub menu it runs quiet well in the recovery mode. What do you suspect? What should I do now?
– Wasil Khan
May 8 '18 at 16:14
You mean it made the computer boot? Perhaps if you run
journalctl
you can see evidence of a problem?– Iain Lane
May 10 '18 at 15:39