Description of problem: On my new laptop, an ASUS Zenbook Pro UX550 with an NVIDIA Geforce GTX 1050 Ti Mobile card together with an integrated Intel UHD Graphics 630 the HDMI output doesn't work. I had problem since installation: the graphical installer didn't started. Solved by adding "nouveau.modeset=0" kernel parameters. After installation rebooted and same problem, resolved with same parameter. Then I attached an external monitor to the HDMI port, and it doesn't work. I know nouveau.modeset=0 disables nouveau, but without this parameter after the GDM Login the system freezes. Previous generation of ASUS Zenbook Pro (UX501) with a GTX 960M worked flawlessly. After searching for a while, found this bug: https://bugs.freedesktop.org/show_bug.cgi?id=100228 Don't know if it's related, but booting with kernel parameter "nouveau.noaccel=1" the second monitor to work (display in gnome control center shows both monitors), but the system is really slow and sluggish and unusable, and the external monitor doesn't work. Found also this infos: https://www.phoronix.com/scan.php?page=news_item&px=Nouveau-Blobs-Pascal-Laptops Apparently NVIDIA released firmware for Pascal GPU more than 3 months ago, and mine is (NV130 family is Pascal, and mine is NV137 (GP107)), but probably is necessary some work to make nouveau drivers usable. Is there any temporary workaround? What's the situation with the support or the Pascal architecture in nouveau? Thanks for the help. Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-1.0.15-6.fc29.x86_64 linux-firmware-20181008-88.gitc6b6265d.fc29.noarch How reproducible: Boot Fedora with nouveau.modeset=0: without this parameter after the GDM Login the system freezes. Steps to Reproduce: 1. Boot Fedora with nouveau.modeset=0 2. The internal monitor work well, but connecting an external monitor with the HDMI port doesn't work Actual results: External monitor says no signal, and display in gnome control center shows only integrated display Expected results: External monitor should work, and display in gnome control center should show both internal ed external monitor Additional info: Output of lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1)
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.