Bug 102300

Summary: Missing 1920x1080_59.94Hz mode (Second monitor shows black screen but has signal)
Product: DRI Reporter: fayn
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg and xorg logs none

Description fayn 2017-08-18 18:42:05 UTC
I can't set my second monitor to 1920x1080 mode in linux. This problem started 2-3 weeks ago. Disabling and enabling monitor with xrandr or XFCE settings used to restore signal (until next restart, sleep doesn't cause bug) but that doesn't help anymore and adding custom mode doesn't help either. I can set xrandr supported lower resolutions and they work.

This happens in Archlinux with linux 4.12 / Mesa 17.1 / amdgpu 1.3.0 but also happens with linux 4.13rc5 / mesa-git / amdgpu-git. 

Everything works in grub and windows 7, but right after linux starts to boot it switches resolution (fb -> amdgpudrmfb i guess?) and ASUS monitor goes black. So the problem only happens in linux. it's UEFI boot for both OS.

Ryzen 1700
ASUS Prime B350+
Radeon R9 285

Dell U2414H DVI-D-0 (HDMI -> DVI-D cable)
ASUS VE247  DVI-I-1 (DVI-I cable)

If logs are needed just tell what to show.
Comment 1 Alex Deucher 2017-08-18 19:00:20 UTC
Please attach your xorg log and dmesg output.  If this is a regression can you bisect?
Comment 2 fayn 2017-08-18 19:26:32 UTC
Created attachment 133616 [details]
dmesg and xorg logs

Logs are from Gallium 0.4 on AMD TONGA (DRM 3.15.0 / 4.12.8-1-ARCH, LLVM 4.0.1) and other ones from git versions.
Comment 3 fayn 2017-08-19 10:51:50 UTC
I find out Asus (2nd monitor) works with 1920x1080 @ 59.94Hz mode, which was probed for my Dell monitor. I'm 99% sure Asus used to be 59.94Hz when monitor last worked, however i can't see it in list of supported modes, only 60Hz which doesn't work. 

AMDGPU(0): Modeline "1920x1080"x59.9  148.35  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
Comment 4 Michel Dänzer 2017-08-23 01:24:39 UTC
Please attach the Xorg configuration snippets you created in /etc/X11/xorg.conf.d and/or /usr/share/X11/xorg.conf.d , in particular anything related to a mode named "1920x1080_60.00".
Comment 5 fayn 2017-08-23 13:30:12 UTC
(In reply to Michel Dänzer from comment #4)
> Please attach the Xorg configuration snippets you created in
> /etc/X11/xorg.conf.d and/or /usr/share/X11/xorg.conf.d , in particular
> anything related to a mode named "1920x1080_60.00".

I forgot to mention, that is irrelevant. The problem happened before i had anything configured in xorg.conf.d (also fixed it since obviously that mode doesn't exist).
Comment 6 fayn 2017-08-23 13:32:51 UTC
Section "Device"
	Identifier "Radeon R9 285"
	Driver "amdgpu"
	Option "AccelMethod" "glamor"
	Option "DRI" "3"
	Option "TearFree" "on"
	Option "ColorTiling" "on"
	Option "ColorTiling2D" "on"
EndSection

This was all in 20-amdgpu.conf originally, doesn't matter if I add monitors+screen or not. I have to run these commands after every restart, or no signal:

xrandr --newmode "mymode" 148.35  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync
xrandr --addmode DVI-I-1 mymode
xrandr --output DVI-I-1 --right-of DVI-D-0 --mode mymode
Comment 7 Michel Dänzer 2017-08-24 03:29:53 UTC
According to the log file, the ASUS monitor only lists the 60 Hz 1920x1080 mode in its EDID. So it seems clear that's what the monitor wants to be fed, but for some reason we don't seem to be generating it properly.

Any chance you can try if a kernel built from the amd-staging-4.12 or amd-staging-drm-next branch of https://cgit.freedesktop.org/~agd5f/linux/ with CONFIG_DRM_AMD_DC=y works better?
Comment 8 fayn 2017-08-24 08:34:07 UTC
(In reply to Michel Dänzer from comment #7)
> According to the log file, the ASUS monitor only lists the 60 Hz 1920x1080
> mode in its EDID. So it seems clear that's what the monitor wants to be fed,
> but for some reason we don't seem to be generating it properly.
> 
> Any chance you can try if a kernel built from the amd-staging-4.12 or
> amd-staging-drm-next branch of https://cgit.freedesktop.org/~agd5f/linux/
> with CONFIG_DRM_AMD_DC=y works better?

Thank you, It works :) 

I thought amdgpu-staging kernel was only needed for their PRO driver, so i never had the idea to try it.
Comment 9 fayn 2017-08-29 09:40:12 UTC
I updated bunch of packages today (linux-amd-staging,mesa etc) and now DVI-I-1 is not recognized but it is shown as DVI-D-1. This also brought new problem: monitors 'blink' randomly, about every ten seconds and it is VERY annoying. 

I also left the computer for few hours monitor powered off, and then when I came back and it should've shown lockscreen monitor repeatedly showed "signal not found" and then got it, and lost it immediately again. I couldn't get picture to either monitor but Ctrl-Alt-Del restart did work.
Comment 10 fayn 2017-08-29 09:43:13 UTC
By the way refresh rate 60.00 is used since DVI-I-1 -> DVI-D-1 change.
Comment 11 Michel Dänzer 2017-08-30 08:06:10 UTC
(In reply to fayn from comment #9)
> I updated bunch of packages today (linux-amd-staging,mesa etc) and now
> DVI-I-1 is not recognized but it is shown as DVI-D-1. This also brought new
> problem: monitors 'blink' randomly, about every ten seconds and it is VERY
> annoying. 

Sounds like most likely there's been a regression on the amd-staging kernel branch you're using. Please file a separate report about that.
Comment 12 fayn 2017-09-25 20:04:23 UTC
Arch stock kernel 4.12.13-1 still boots one monitor black, but can be restored with xrandr.

Wayland sessions work, and they never lose signal in any situation. Xorg sessions do randomly cause black screen (https://bugs.freedesktop.org/show_bug.cgi?id=102956).
Comment 13 fayn 2017-11-04 07:58:15 UTC
Latest mesa driver still shows black screen. I also tested with fresh Ubuntu 16.04  installation, and same thing happens there (black screen problems started well over a year ago, just it got worse this summer).

AMDGPU-PRO 17.40 (and probably earlier ones) works and I don't have any problems with it. Switching to fullscreen and back is absolutely no problem with it, and it always shows picture at boot time in both monitors.
Comment 14 Martin Peres 2019-11-19 08:21:27 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/223.

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.