Description of problem: With three monitors (two connected to nvidia card (nouveau), third to onboard i915 (Intel) wayland only recognised one set of providers. If I set the primary display in the BIOS to use the onboard 915 then wayland recognizes and uses the Intel provider, does not find the nouveau providers. If I set the BIOS to set the primary display to AUTO wayland uses the nouveau provider. X recognizes both and uses all three displays: xrandr --listproviders Providers: number : 3 Provider 0: id: 0xa4 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 6 associated providers: 2 name:Intel Provider 1: id: 0x64 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 2 outputs: 3 associated providers: 2 name:nouveau Provider 2: id: 0x64 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 2 outputs: 3 associated providers: 2 name:nouveau Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
From dmesg: dmesg |grep -i drm [ 1.270587] [drm] Initialized drm 1.1.0 20060810 [ 2.254007] nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB [ 2.254008] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB [ 2.254010] nouveau 0000:01:00.0: DRM: TMDS table version 2.0 [ 2.254011] nouveau 0000:01:00.0: DRM: DCB version 4.0 [ 2.254012] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000302 00020030 [ 2.254013] nouveau 0000:01:00.0: DRM: DCB outp 01: 02000300 00000000 [ 2.254014] nouveau 0000:01:00.0: DRM: DCB outp 02: 08011392 00020020 [ 2.254015] nouveau 0000:01:00.0: DRM: DCB outp 03: 04022310 00000000 [ 2.254016] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030 [ 2.254017] nouveau 0000:01:00.0: DRM: DCB conn 01: 00002161 [ 2.254017] nouveau 0000:01:00.0: DRM: DCB conn 02: 00000200 [ 2.267096] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.267097] [drm] Driver supports precise vblank timestamp query. [ 2.322280] nouveau 0000:01:00.0: DRM: MM: using COPY0 for buffer copies [ 2.449458] nouveau 0000:01:00.0: DRM: allocated 1680x1050 fb: 0x60000, bo ffff880457de0800 [ 2.458634] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0 [ 2.459370] [drm] Memory usable by graphics device = 2048M [ 2.459375] fb: switching to inteldrmfb from EFI VGA [ 2.459473] [drm] Replacing VGA console driver [ 2.466161] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.466163] [drm] Driver supports precise vblank timestamp query. [ 2.477531] [drm] Initialized i915 1.6.0 20151218 for 0000:00:02.0 on minor 1 [ 2.675807] fbcon: inteldrmfb (fb0) is primary device [ 3.084055] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device Logged into Gnome-Wayland (using i915) $ xrandr --listproviders Providers: number : 0 $ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 XWAYLAND0 connected 1920x1080+0+0 480mm x 270mm 1920x1080 59.96*+
I have the same issue with my Lenovo p50. I run Fedora 25-Beta (F25). On this machine, the internal LCD is linked to the Intel graphics card, and the external display directly on the Nvidia chip. (Atleast that's what I believe.) These scenarios are tested: 1. Bios: Hybrid graphics, Xorg Internal display works fine. External display works fine. 2. Bios: Hybrid graphics, wayland Internal display works fine. External display does not show. 3. Bios: Discrete graphics only, Wayland Both displays, but nouveau does not work with a lots of Xorg applications. (Xorg fallback.) Power consumption is much higher. Let me know if I can should do some extra testing og provide some logs! Regards, Kjetil
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.