Bug 1658561
Summary: | HDMI not working on laptop ASUS Zenbook Pro UX550 with NVIDIA Geforce GTX | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Simone Marchioni <s.marchioni> |
Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | airlied, ajax, bskeggs, jglisse, s.marchioni |
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: | 2019-05-28 23:27:32 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
Simone Marchioni
2018-12-12 12:20:45 UTC
Various new laptops have issues with runtime power management, which could be what you're seeing here. What happens if you boot with "nouveau.runpm=0"? Tried to boot replacing "nouveau.modeset=0" with "nouveau.runpm=0", and here are the results: - boot MUCH MORE SLOWER than before - at the GDM login screen, after insertion of user's credentials, the system seems locked (GMD gray backgroud + mouse pointer locked), and after about a minute the desktop shows - GNOME starts to pop up a sequence of "Ooops", showing that "something went wrong" - the HDMI output still doesn't work Hope this helps 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. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |