Ask Your Question

fedora 29 get stucked booting after starting Gnome display manager

asked 2019-02-13 03:32:35 -0500

devrieshh gravatar image

updated 2019-02-13 03:47:03 -0500

After upgrading kernel to 4.20 fedora gets stucked booting up after starting Gnome display manager,so i have to startup with 4.19 kernel,does somebody has any idea why

edit retag flag offensive close merge delete


video driver was not updated, when the new kernel went on. Did you use dkms, kmod, or akmod for your video driver installation?

SteveEbey73701 gravatar imageSteveEbey73701 ( 2019-02-13 13:35:53 -0500 )edit

As a follow up question, if 4.19 was not installed and accessible, how do you get the OS to boot? I have been stuck with 4.20 and have no other versions of Fedora 29 installed It seems like all of my Fedora 28 images not won't work either after update.

TheoTrav gravatar imageTheoTrav ( 2019-02-26 11:07:46 -0500 )edit

press esc during the process to check the boot instructions and report them back.

weezylane gravatar imageweezylane ( 2019-03-03 10:40:07 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-03-01 10:38:38 -0500

sender gravatar image

updated 2019-03-03 17:22:49 -0500

-Same problem here, but with Fedora running in a VM! (vmware workstation)

It started with the update from kernel* 4.18 or 4.19 to 4.20.11-200 (and is still present in 4.20.12-200). The VM is booting fine with previous kernel in boot menu, 4.18 or 4.19.

For experimenting I did a dnf upgrade --exclude=kernel,kernel\* to isolate the problem -- it booted up normally.

However, kernel 4.20 boots up wenn the vmware window is set to 'Free stretch'. With this setting it boots in a lower resolution and grub menu is visible. After login 'Free stretch' can be unset and the desktop adjusts to monitor's resolution, 1920x1200 or 4K on laptop display.

some info from journalctl:

Logs begin at Wed 2019-02-27 14:40:27 CET, end at Fri 2019-03-01 15:04:50 CET.     
Mär 01 11:55:26 fedora3ng kernel: piix4_smbus 0000:00:07.3: SMBus Host Controller not enabled!
Mär 01 11:55:32 fedora3ng spice-vdagent[1908]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Mär 01 11:55:33 fedora3ng kernel: [drm:vmw_stdu_crtc_page_flip [vmwgfx]] *ERROR* Page flip error -16.
Mär 01 11:55:44 fedora3ng spice-vdagent[2328]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Mär 01 11:55:45 fedora3ng kernel: [drm:vmw_stdu_crtc_page_flip [vmwgfx]] *ERROR* Page flip error -16.
Mär 01 11:55:46 fedora3ng gnome-session-binary[2091]: GLib-CRITICAL: g_child_watch_add_full: assertion 'pid > 0' failed
Mär 01 11:55:52 fedora3ng gnome-session-binary[1715]: Unrecoverable failure in required component org.gnome.Shell.desktop

So this is not an answer, but some more info -- same problem in a VM; it's not a hypervisor issue or specific to hardware.

How to proceed from this point?

Update 2019-03-03, my boot and shutdown problem is probably solved

devrieshh, if you boot up your machine again, you should see grub boot menu, because previous boot was not succesfull. When you get to the grub boot menu you can follow the instructions Disabling Graphical Boot Temporarily in the same document. Then, the system should be booting into gnome desktop, where you can disable graphical boot permanently as well. Maybe you would like to edit the grub configuration file via grub-customizer as well.

Moreover, if you would like to see grub boot menu on every boot follow nicklevinson's answer.

edit flag offensive delete link more

Question Tools



Asked: 2019-02-13 03:32:35 -0500

Seen: 879 times

Last updated: Mar 03 '19