Bug 2131203
| Summary: | Re-enable wayland session for ASPEED devices in GDM | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | RHEL Program Management Team <pgm-rhel-tools> |
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Kopec <pekopec> |
| Severity: | unspecified | Docs Contact: | Marek Suchánek <msuchane> |
| Priority: | unspecified | ||
| Version: | 9.1 | CC: | hdegoede, jfalempe, jkoten, ndegraef, ohudlick, pasik, pekopec, pvlasin, rstrode, sbarcomb, tpelka, tpopela |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 9.2 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gdm-40.1-19.el9 | Doc Type: | Enhancement |
| Doc Text: |
.Wayland is now enabled on Aspeed GPUs
Previously, the Aspeed GPU driver did not perform well enough to run a Wayland session. To work around that problem, the Wayland session was disabled for Aspeed GPUs.
With this release, the driver performance has been significantly improved and the Wayland session is now responsive. As a result, the Wayland session is now enabled on Aspeed GPUs by default.
|
Story Points: | --- |
| Clone Of: | 2097308 | Environment: | |
| Last Closed: | 2023-05-09 07:41:47 UTC | Type: | --- |
| 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: | 2097308, 2128599 | ||
| Bug Blocks: | |||
|
Comment 1
Tomas Popela
2022-10-20 15:39:03 UTC
With gdm-40.1-19.el9 wayland with apseed gpu is available. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (gdm bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:2278 |