Bug 107635 - Internal display always be blank in mirror, extended and built-in only display mode
Summary: Internal display always be blank in mirror, extended and built-in only displa...
Status: RESOLVED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-21 03:51 UTC by jian-hong
Modified: 2018-08-28 03:24 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
log of display mode changement (1.07 MB, text/plain)
2018-08-21 03:51 UTC, jian-hong
no flags Details

Description jian-hong 2018-08-21 03:51:59 UTC
Created attachment 141208 [details]
log of display mode changement

We have an ASUS X570ZD laptop equipped with AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx and NVIDIA GeForce GTX 1050 Mobile.

We tested it with Linux kernel 4.18.3.  It is nouveau with parameters runpm=0 and noaccel=1 as the driver for NVIDIA GeForce GTX 1050 Mobile card.

After plugin the HDMI cable, the system is in extended mode and displays correctly.

But the internal display becomes blank after changes to mirror mode, extended mode and built-in only mode.  The external display always works correctly.

There are the errors: 
"[drm:hwss_edp_wait_for_hpd_ready [amdgpu]] *ERROR* hwss_edp_wait_for_hpd_ready: wait timed out!"
"[drm:drm_dp_dpcd_access [drm_kms_helper]] Too many retries, giving up. First error: -71"
in dmesg.
Comment 1 Harry Wentland 2018-08-24 13:18:16 UTC
Have you tried with nouveau disabled?

https://askubuntu.com/questions/841876/how-to-disable-nouveau-kernel-driver/951892#951892
Comment 2 Daniel Drake 2018-08-28 03:24:05 UTC
This issue was detected on 4.18.3 when using a somewhat reduced developer config. When using our usual full distro kernel config (from Ubuntu), the issue convincingly goes away.

Both Jian-Hong and I looked at the differences in the config and couldn't spot anything obvious that would explain different behaviour.

There's probably a bug here somewhere, but as it's working on our shipped config I'll close this issue, as we need to focus our time on other issues on this platform.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.