Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1955390

Summary: Fedora 34 Workstation hangs on Lenovo splash screen on ThinkPad T490
Product: [Fedora] Fedora Reporter: Seth Goldin <sethgoldin>
Component: fedora-releaseAssignee: Mohan Boddu <mboddu>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 34CC: bugzilla, dennis, fedoraproject, jkeating, kellin, kevin, mboddu, pbrobinson, sgallagh, thrcka, zbyszek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-30 05:09:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Seth Goldin 2021-04-30 02:46:03 UTC 
Description of problem:
Unable to successfully boot Fedora 34 Workstation after installing the DVD ISO to a Lenovo ThinkPad T490. After installing to boot drive from live USB, from Fedora-Workstation-Live-x86_64-34-1.2.iso image, the ThinkPad just hangs at the Lenovo splash screen.

Version-Release number of selected component (if applicable):


How reproducible:
Always.


Steps to Reproduce:
1. Set BIOS/UEFI to factory defaults [F9]
2. Boot to live USB
3. Install to disk
4. Installation completes
5. Reboot machine

Actual results:
Machine hangs on Lenovo splash screen


Expected results:
Get past the Lenovo splash screen to LUKS prompt [if LUKS is installed] or to grub menu and login page.


Additional info:
This happens every time. Tried lots of different permutations:
1. Factory defaults on UEFI settings
2. With or without Secure Boot enabled
3. Secure Boot enabled: Factory Secure Boot keys [presumably for Windows 10?]
4. Secure Boot enabled: "Setup" keys for Secure Boot
5. TPM 2.0 enabled or disabled
6. Automatic partitioning from installer
7. Manual partitioning with "standard partition"
8. Manual partioning with BTRFS
9. Manual partitioning with LVM
10. All partitioning with or without encryption enabled

For what it's worth, this happened on an upgrade initially, but then I kept clean installing over and over again.
Comment 1 Chris Murphy 2021-04-30 05:09:49 UTC 

*** This bug has been marked as a duplicate of bug 1955416 ***