Bug 2430612
| Summary: | Plymouth visual stall during boot and LUKS passphrase entry on AMD Strix Point | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gergely Dömsödi <doome> | ||||
| Component: | plymouth | Assignee: | Ray Strode [halfline] <rstrode> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 43 | CC: | gnome-sig, hans, rstrode | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2026-01-18 12:59:06 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: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 2430613 *** |
Created attachment 2122525 [details] plymouth debug log during boot Description of problem: Plymouth visual stall during boot and LUKS passphrase entry. Version-Release number of selected component (if applicable): My system is a Ryzen AI 9 HX 370 CPU providing integrated graphics, and an Nvidia RTX 5070 Ti, an asus zephyrus g14 laptop. How reproducible: Always on my setup. Steps to Reproduce: 1. Boot the computer 2. 3. Actual results: The luks passpharse entry screen is shown, but no keypresses are echoed, but if I enter the password blindly, the boot continues. The screen refreshes only at the GDM login screen. Expected results: The keypresses are echoed back to the screen. Additional info: First I suspected some timing issue between the dGPU and the iGPU, and tried to disable the dGPU entirely using udev blacklisting, but the bug stayed.