Bug 2119757
| Summary: | F37 images don't boot in BIOS mode on Thinkpad T480s | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
| Component: | lorax | Assignee: | Brian Lane <bcl> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | anaconda-maint-list, bcl, gmarr, reallylongword, robatino |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | RejectedBlocker | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-23 15:27:01 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2092065 | ||
I know I only found a single PC where the new boot workflow fails, but still, proposing as a blocker, to do more investigation and be aware of this. Brian, anything I can do to help you debug this? One thing I have done when debugging things like this is make a video of the boot and step through the 'flash' to see if there really is a message there. I don't think this should be a blocker though -- the system is really a UEFI system and that boot path works. Good idea. I've created a video and went frame by frame, there is no message printed. Discussed during the 2022-08-22 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Final)" was made as it's clear images boot in both BIOS and UEFI mode on most systems, and this system is not blocked because you can simply boot in UEFI mode. With only this one UEFI-capable system definitely affected, this clearly is not severe enough to violate the criteria. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-08-22/f37-blocker-review.2022-08-22-16.01.txt |
Description of problem: F37 images don't boot on my Thinkpad T480s in BIOS ("Legacy") mode. If I select the USB thumb drive from a one-time boot menu, the screen flashes and immediately returns to the same menu. I.e. I never see the boot menu presented by Fedora. With F36 images, it boots as expected. I assume this is caused by: https://fedoraproject.org/wiki/Changes/BIOSBootISOWithGrub2 On Thinkpad T480s: * Selecting "Legacy only" boot in firmware setup means that F37 images can't be booted (F36 images can). * Selecting "UEFI only" boot in firmware setup means that F37 images can be booted just fine. * Selecting "Both (Legacy+UEFI), Legacy first" boot in firmware setup means that F37 images can be booted just fine, but they boot in UEFI mode, despite BIOS mode being configured as the default. I also tested other computers I have at home, and all of them booted F37 without issues in BIOS mode - Thinkpad T500, Fujitsu Lifebook E780, Gigabyte GA-Z87-D3HP (Intel Z87) desktop motherboard. Version-Release number of selected component (if applicable): Fedora-Workstation-Live-x86_64-37-20220818.n.0.iso Fedora-Everything-netinst-x86_64-37-20220818.n.0.iso How reproducible: always, on T480s Steps to Reproduce: 1. select "Legacy only" boot in firmware setup 2. open one-time boot menu 3. select the USB thumb drive 4. the screen flashes and displays the one-time boot menu again