Created attachment 1678980 [details] journalctl with nomodeset parameter Description of problem: GNOME Shell fails to boot up past gdm with nomodeset kernel parameter on BIOS systems. Live works just fine with nomodeset. Enabling automatic login (and thus bypassing gdm screen as it's happening on live installation media) workarounds the issue. Version-Release number of selected component (if applicable): gnome-shell-3.36.1-3.fc32.x86_64 mutter-3.36.1-4.fc32.x86_64 (https://kojipkgs.fedoraproject.org/compose/32/Fedora-32-20200414.1/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-32-1.3.iso) How reproducible: Always (tested just on one system) Steps to Reproduce: 1. Boot Fedora 32 with Basic Video Driver in BIOS mode 2. Proceed with Fedora installation 3. Boot installed system 4. Shell gets stuck on grey screen after finishing initial setup Actual results: GNOME Shell works fine without nomodeset, doesn't work with nomodeset. There are no issues on UEFI/nomodeset. Expected results: GNOME Shell should work on BIOS nomodeset. Additional info: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
Proposed as a Blocker for 32-final by Fedora user frantisekz using the blocker tracking app because: The generic video driver option ('basic graphics mode' - as described in the Basic criteria) on all release-blocking installer and live images must function as intended (launching the installer or desktop and attempting to use a generic driver), and there must be no bugs that clearly prevent the installer or desktop from being reached in this configuration on all systems or on wide classes of hardware.
Created attachment 1678993 [details] video of the issue
I have tested the KDE Live RC 1.3 on my T460s. The installation on basic graphic driver was flawless, when I booted for the first time the system reset itself automatically after showing a black screen for a while and then it booted normally using the basic graphics driver. I am pasting logs from the machine.
Created attachment 1678998 [details] "journalctl -b" from T460's succesfull boot process.
I tested a BIOS install on Thinkpad T500 with Intel graphics, both GNOME and KDE boot fine with nomodeset.
Tried also the Workstation Live and got similar behaviour as before. In the end, I have a working Workstation running with nomodeset. T460s.
FYI: This seems to affect just one Intel GPU generations, leaving the bug open and removing Blocker Proposal. Thanks everybody for testing on different HW!
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.