Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A amd
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,333
    • Issues 1,333
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • drm
  • amd
  • Issues
  • #1151
Closed
Open
Created May 23, 2020 by Philipp@Troggi

No proper resolution for Philips 272G5DYEB on Ubuntu 20.04

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 systems: desktop and laptop with GPUs from different companies: 1050 ti (mobile) and 5700 xt
  • Use different drivers: propritary and open source
  • Change resolution via xrandr addmode/newmode with modelines from cvt 1920 1080 and modeline I got from Windows (where 1920x1080 works) (leads to monitor saying "no signal on screen")
  • Using "GRUB_GFXMODE" config in grub (no change)
  • Searching through logs, only useleful thing I found was in the Xorg log (for AMD):
 [ 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)
  • for Nvidia:
 [ 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)
  • In Windows the resolution works, but Windows is showing resolutions up to 4K which is unusual (I think). Looks to me that Windows is guessing the modelines better
  • Both GPUs work fine with a different monitor
  • Use latest DRM-tip kernel
  • Use different DP cables

Some logs can be found here.

Edited May 23, 2020 by Philipp
Assignee
Assign to
Time tracking