Bug 1605409
Summary: | Boot screen doesn't redraw after showing initial password prompt until is complete [amdgpu, works fine with radeon driver] | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ell1e <el> |
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: | 29 | CC: | elad, fedora2021q2, hdegoede, rstrode |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-12 08:41:51 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
ell1e
2018-07-20 15:16:15 UTC
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1490490 Unfortunately, the Bugzilla Plymouth maintainer has completely ignored that bug for a year now. As a bonus, with kernel 4.18.x, Plymouth is now completely broken on AMDGPU - blank screen, doesn't silently accept a password, can't Esc to use text mode. Workaround is to remove rhgb from the boot line. I'd consider Plymouth unmaintained at this point. This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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. Co-maintainer of plymouth here. (In reply to fednuc from comment #1) > Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1490490 > > Unfortunately, the Bugzilla Plymouth maintainer has completely ignored that > bug for a year now. That is simply not true, the original bug where this is tracked is bug 1490490 and I've responded several times in that bug. As mentioned there, this really is an amdgpu kernel driver bug, not a plymouth issue. As also mentioned there someone really should file a bug for this upstream, which no one has done so far. I've added instructions to bug 1490490 for filing this bug and one person has filed a bug, but he actually is using Intel graphics, so that is a completely different issue. No-one I repeat *no-one* has filed a bug with the upstream amdgpu developers for this yert. So if you want to help getting this fixed, please file such a bug. I will repeat instructions for filing the bug in bug 1490490, once I've marked all the other bugs about this as duplicates (so that everyone will be in the Cc of bug 1490490 and see the instructions there. Please put any further comments about this in bug 1490490. > I'd consider Plymouth unmaintained at this point. Again that is simply not true. *** This bug has been marked as a duplicate of bug 1490490 *** > That is simply not true, the original bug where this is tracked is bug 1490490 and I've responded several times in that bug. Er, that bug was opened in September 2017, my comment you quoted was from September 2018; your first comment on that bug was in December 2018 ;) > As mentioned there, this really is an amdgpu kernel driver bug, not a plymouth issue. As also mentioned there someone really should file a bug for this upstream, which no one has done so far. > > I've added instructions to bug 1490490 for filing this bug and one person has filed a bug, but he actually is using Intel graphics, so that is a completely different issue. > > No-one I repeat *no-one* has filed a bug with the upstream amdgpu developers for this yert. So if you want to help getting this fixed, please file such a bug. Um, you said to Sebastian in https://bugzilla.redhat.com/show_bug.cgi?id=1490490#c24 to file a bug about the different PSR issue, which he did. AFAICS the first reference to upstreaming the amdgpu issue was 2 days ago. |