[amdgpu] Proper monitor resolution/refresh rate not available

Bug #1879402 reported by Philipp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
xserver-xorg-video-amdgpu (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm currently (in Ubuntu 20.04) stuck with this low resolution: 640x480 59.94*, what I want to have is the monitor specs: 1080p and 144 Hz. This problem appeared after plugging in my old monitor after 2 years again, it's a philips 272G5DYEB. Things that I unsuccesfully tried to get a proper resolution:
-Use different GPUs from different vendors: 1050 ti and 5700 xt. Use different drivers: propritary and open source
-Change resolution via xrandr addmode/newmode (leads to "no signal" from monitor)
-Using "GRUB_GFXMODE" config in grub (no change)
-Searching through logs, only useleful thing I found was in the Xorg log:
[ 12.117] (II) AMDGPU(0): EDID for output DisplayPort-0
[ 12.117] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[ 12.117] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
-In Windows the resolution works fine
-Both GPUs work fine with a different monitor
I'm not sure how to proceed here nor do I know where the problem lies. I assume this to be a bug in Ubuntu because a bunch of different GPUs/drivers lead to this problem making it unlikely to be a driver problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.4.0-050400-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 18 22:16:58 2020
DistUpgraded: 2020-05-09 15:39:17,760 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:0b36]
InstallationDate: Installed on 2019-11-26 (173 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-050400-generic root=UUID=f3ec722e-f50e-43cf-8e55-3cbdb22a0592 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-09 (9 days ago)
dmi.bios.date: 11/29/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.LQ
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 PC MATE (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.LQ:bd11/29/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350PCMATE(MS-7A34):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101+git2005070630.c997ba~oibaf~f
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2~git2005181337.b5accb~oibaf~f
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Nov 26 22:01:15 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.5+git20191008-0ubuntu1

Revision history for this message
Philipp (phglipp) wrote :
description: updated
affects: ubuntu → xorg (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

It looks like the amdgpu driver can't properly talk to or identify that monitor. Try a different DisplayPort cable.

tags: added: amdgpu
summary: - Proper monitor resolution/refresh rate not available
+ [amdgpu] Proper monitor resolution/refresh rate not available
affects: xorg (Ubuntu) → xserver-xorg-video-amdgpu (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: New → Incomplete
Revision history for this message
Philipp (phglipp) wrote :

I tried 3 different Displayport cables without success. In Ubuntu get-edid tells me that there is no EDID information provided. As the monitor is working properly in Windows I think that Windows is just doing a better job at coming up with a 1080p modeline on its own. So in my mind the thing to do now is trying out different modelines until one with the proper resolution is actually working but I have no idea how to come up with more modelines other than using cvt 1920 1080.

Revision history for this message
Philipp (phglipp) wrote :

I just went into Windows using a cmd-tool called DumbEDID which gave me information I upload here (note that there are two monitors present and the MSI is working fine in Ubuntu, I'm referring to the philips at the bottom of the log). There is some information that is actually transported like the native resolution, physical size, monitor model and some frequencies. I'm wondering if I can use this information now to create a modeline in Ubuntu.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please attach output of `find /sys | grep edid$ | xargs file -i`, thanks!

Revision history for this message
Philipp (phglipp) wrote :

Doesn't seem to be that there is much EDID communication going on.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Ok, please test latest drm-tip kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

And file an upstream bug if it doesn't work:
https://gitlab.freedesktop.org/drm/amd/issues

Revision history for this message
Philipp (phglipp) wrote :

The drm-tip kernel didn't help the case. Did I understand this correctly that you have identified the driver to be the problem? If so I have to delegate this two 3 different drivers with which I have this problem: the already linked amd driver, but also the proprietary and open source nvidia drivers that I both tested with unsuccessfully. Can you point me to the right places here?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Yes, the EDID needs to be read from DRM drivers, then userspace will use the EDID exported from DRM.

Revision history for this message
Philipp (phglipp) wrote :

I just checked back with my Nvidia machine and instead of "amdgpu" it saying that "modeset" is doing the EDID'ing (both with open source and proprietary driver) and no 1080p 144 Hz:
[ 18.782] (II) modeset(G0): EDID for output DP-1-1
[ 18.782] (II) modeset(G0): Printing probed modes for output DP-1-1
[ 18.782] (II) modeset(G0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 18.782] (II) modeset(G0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 18.782] (II) modeset(G0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 18.782] (II) modeset(G0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 18.782] (II) modeset(G0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
Where do I have to file the bug report in this case? I saw that there is a thing called modesetting that is part of the kernel. Do I have to file a report for the kernel?

Philipp (phglipp)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.]

Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Changed in linux (Ubuntu):
status: Expired → New
Changed in xserver-xorg-video-amdgpu (Ubuntu):
status: Expired → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

I found that `find /sys | grep edid$ | xargs file -i` will always report the file is empty.

Please use `find /sys | grep edid$ | xargs cat` to find out which one is non-empty and attach the EDID here.

To post a comment you must log in.