[i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead

[Mike Harris]

The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem.

Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs

Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid.

After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next.

Here is information I collected:

output from xrandr after fresh boot:

~$ xrandr
Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080 60.01*+ 60.01 59.97 59.96 59.93
   1680x1050 59.95 59.88
   1600x1024 60.17
   1400x1050 59.98
   1600x900 59.99 59.94 59.95 59.82
   1280x1024 60.02
   1440x900 59.89
   1400x900 59.96 59.88
   1280x960 60.00
   1440x810 60.00 59.97
   1368x768 59.88 59.85
   1360x768 59.80 59.96
   1280x800 59.99 59.97 59.81 59.91
   1152x864 60.00
   1280x720 60.00 59.99 59.86 59.74
   1024x768 60.04 60.00
   960x720 60.00
   928x696 60.05
   896x672 60.01
   1024x576 59.95 59.96 59.90 59.82
   960x600 59.93 60.00
   960x540 59.96 59.99 59.63 59.82
   800x600 60.00 60.32 56.25
   840x525 60.01 59.88
   864x486 59.92 59.57
   800x512 60.17
   700x525 59.98
   800x450 59.95 59.82
   640x512 60.02
   720x450 59.89
   700x450 59.96 59.88
   640x480 60.00 59.94
   720x405 59.51 58.99
   684x384 59.88 59.85
   680x384 59.80 59.96
   640x400 59.88 59.98
   576x432 60.06
   640x360 59.86 59.83 59.84 59.32
   512x384 60.00
   512x288 60.00 59.92
   480x270 59.63 59.82
   400x300 60.32 56.34
   432x243 59.92 59.57
   320x240 60.05
   360x202 59.51 59.13
   320x180 59.84 59.32
HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm
   1920x1080 60.00* 50.00 59.94
   1280x720 60.00 50.00 59.94
   1024x768 60.00
   800x600 60.32
   720x576 50.00
   720x480 60.00 59.94
   640x480 60.00 59.94
DP-1-1 disconnected (normal left inverted right x axis y axis)

output from get-edid | parse-edid:
~$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 9
No EDID on bus 10
3 potential busses found: 0 4 8
Will scan through until the first EDID is found.
Pass a bus number as an option to this program to go only for that one.
Bus 0 doesn't really have an EDID...
256-byte EDID successfully retrieved from i2c bus 4
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
 Identifier "ROG PG278QR"
 ModelName "ROG PG278QR"
 VendorName "AUS"
 # Monitor Manufactured week 47 of 2016
 # EDID version 1.3
 # Digital Display
 DisplaySize 600 340
 Gamma 2.20
 Option "DPMS" "false"
 Horizsync 30-140
 VertRefresh 24-60
 # Maximum pixel clock is 300MHz

 #Extension block found. Parsing...
 Modeline "Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
 Modeline "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync
 Modeline "Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
 Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
 Modeline "Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
 Modeline "Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
 Modeline "Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
 Modeline "Mode 7" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
 Option "PreferredMode" "Mode 1"
EndSection

"Mode 0" above is the mode that I want to use, which doesn't appear in the Settings app list of available resolutions.

I used "Mode 0" to via xrandr --newmode:
~$ xrandr --newmode "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync

Then, xrandr --addmode:
~$ xrandr --addmode HDMI-1-1 "Mode 0"

Then in Settings app, I can select the 2560x1440 resolution for the ASUS PG278QR display.
---
ProblemType: Bug
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus.0000.02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020
 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: Fresh install
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 620 (Whiskey Lake) [1462:126c]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Mobile] [1462:126c]
InstallationDate: Installed on 2019-04-11 (565 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Micro-Star International Co., Ltd. PS63 Modern 8RC
NonfreeKernelModules: nvidia_modeset nvidia
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Tags: focal ubuntu
Uname: Linux 5.4.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout plugdev sudo tty uucp
_MarkForUpload: True
dmi.bios.date: 12/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16S1IMS.106
dmi.board.asset.tag: Default string
dmi.board.name: MS-16S1
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S1IMS.106:bd12/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnPS63Modern8RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
dmi.product.family: PS
dmi.product.name: PS63 Modern 8RC
dmi.product.sku: 16S1.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1901470/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1901470

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Mike Harris (t-mike-6)]

apport information

[Daniel van Vugt (vanvugt)]

Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor:

Standard Timings: none
Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm
               2560 2608 2640 2720 ( 48 32 80)
               1440 1443 1448 1481 ( 3 5 33)
               +hsync -vsync
               VertFreq: 59.951 Hz, HorFreq: 88.787 kHz
Display Product Serial Number: GBLMQS047683
Display Range Limits
  Monitor ranges (Bare Limits): 24-60 Hz V, 30-140 kHz H, max dotclock 300 MHz
Display Product Name: ROG PG278QR

[Daniel van Vugt (vanvugt)]

I would like to check to see if the problem is occurring in the kernel and not just in Xorg. Please run:

  grep . /sys/class/drm/*/modes > modes.txt

and then attach the resulting text file here.

[Mike Harris (t-mike-6)]

output from: grep . /sys/class/drm/*/modes > modes.txt

[Daniel van Vugt (vanvugt)]

Thanks. Looks like this is also a kernel bug...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mike Harris (t-mike-6)]

Follow post of a work around that automatically enables the resolution I want.

I added a file named: 45custom_xrandr_settings
in folder: /etc/X11/Xsession.d

containing:
xrandr --newmode "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync
xrandr --addmode HDMI-1-1 "Mode 0"

This will cause X11 to use the 2560x1440 resolution after reboot.

[Kai-Heng Feng (kaihengfeng)]

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

And file a bug agains Intel graphics if the issue persists:
https://gitlab.freedesktop.org/drm/intel/wikis/How-to-file-i915-bugs

[Daniel van Vugt (vanvugt)]

Comment #29 shows this problem is originating in the i915 kernel driver. So there's no need to include 'xorg-server' here, Xorg is only following the (incomplete) list of modes exposed by the kernel.

[Daniel van Vugt (vanvugt)]

It looks like this issue keeps happening with HDMI for i915 users. Maybe Intel is being conservative (or just accurate) with bandwidth limitations... Anyone affected, please follow the instructions in comment #34.

[Daniel van Vugt (vanvugt)]

Also note that 3K/4K-wide at 60Hz requires an HDMI 2.0 port and cable, or for you to limit your refresh rate to 30Hz (not recommended for desktop usage) for HDMI v1.4:

https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video

[Daniel van Vugt (vanvugt)]

Ideally use DisplayPort if you can, because it has supported higher resolutions and higher bandwidth than HDMI for a long time already.

[Daniel van Vugt (vanvugt)]

Anyone affected by this bug, please tell us if it exists in a live session of Ubuntu 21.04:

  https://ubuntu.com/download/desktop

and if it does then please also follow the instructions in comment #34.

[Sebastian (seb1024)]

If started a live session with Ubuntu 21.04 and the problem exists also (as described in "my" bug 1929456).
I run
 grep . /sys/class/drm/*/modes > modes.txt
and will attach the output file (renamed).

The workaround (as described in "my" bug 1929456) helped there also.

I wasn't able to follow the instructions in comment #34, because I didn't understand what to do there. Maybe a link to an explanation how to do this could help, so I could do (or at least try) it.

[Daniel van Vugt (vanvugt)]

For comment #34, click on the link and then click the 'amd64' directory. Then download all the files that don't have "lowlatency" in their name. You don't need "lowlatency". Now you can install your kernel files in a single command:

  sudo dpkg -i *.deb

and reboot.

[Daniel van Vugt (vanvugt)]

I'm guessing a common cause of this bug is low quality HDMI cables. If you're stuck at 1080p then that suggests the cable is only HDMI 1.2. To achieve 1440p at 60Hz you will need an HDMI 1.4 cable. And to achieve 2160p (4K) at 60Hz you will need an HDMI 2.0 cable AND a modern GPU to plug it into. 3K and 5K requirements are somewhere in the middle depending on the vertical resolution of the monitor.

https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video

If you're shopping for a new monitor then it's best to find one with DisplayPort (or USB-C) which doesn't have quite as severe limitations as HDMI does.

[jerry collins (jerrycollins)]

Hi Daniel,

Thanks for the help and the quick response.

I don't see any marking on the HDMI cable I'm using so I'm guessing it
isn't one a high quality one.

So, I played around with the refresh rates and got it to work at a lower
refresh rate:

xrandr --addmode HDMI-2 2560x1440_24.00
xrandr --output HDMI-2 --mode 2560x1440_24.00
xrandr --newmode "2560x1440_24.00" 113.75 2560 2648 2904 3248 1440 1443
1448 1463 -hsync +vsync

This ties in with the poor quality cable idea.

Thanks again for the assistance,
Jerry.

On Wed, Dec 15, 2021 at 3:00 AM Daniel van Vugt <email address hidden>
wrote:

> I'm guessing a common cause of this bug is low quality HDMI cables. If
> you're stuck at 1080p then that suggests the cable is only HDMI 1.2. To
> achieve 1440p at 60Hz you will need an HDMI 1.4 cable. And to achieve
> 2160p (4K) at 60Hz you will need an HDMI 2.0 cable AND a modern GPU to
> plug it into. 3K and 5K requirements are somewhere in the middle
> depending on the vertical resolution of the monitor.
>
>
> https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video
>
> If you're shopping for a new monitor then it's best to find one with
> DisplayPort (or USB-C) which doesn't have quite as severe limitations as
> HDMI does.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1954840).
> https://bugs.launchpad.net/bugs/1901470
>
> Title:
> [i915] HDMI monitor's native resolution (EDID detailed mode) not
> available, defaults to 1080p instead
>
> Status in linux package in Ubuntu:
> Confirmed
> Status in linux-hwe-5.11 package in Ubuntu:
> Confirmed
>
> Bug description:
> The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4,
> the max resolution presented in the Settings app is 1920x1080, and
> this resolution is the one that it uses. Switching between the Nvidia
> driver or the Intel driver (laptop has low-power intel gpu too)
> doesn't correct the problem.
>
> Digging in deeper, based on
>
> https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs
>
> Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to
> use get-edid | parse-edid.
>
> After applying the mode that I wanted manually via xrandr --newmode
> and xrandr --addmode, I was able to select the max resolution of the
> monitor and works correctly, until reboot. I will add it to my
> xorg.conf next.
>
> Here is information I collected:
>
> output from xrandr after fresh boot:
>
> ~$ xrandr
> Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
> eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x
> axis y axis) 344mm x 193mm
> 1920x1080 60.01*+ 60.01 59.97 59.96 59.93
> 1680x1050 59.95 59.88
> 1600x1024 60.17
> 1400x1050 59.98
> 1600x900 59.99 59.94 59.95 59.82
> 1280x1024 60.02
> 1440x900 59.89
> 1400x900 59.96 59.88
> 1280x960 60.00
> 1440x810 60.00 59.97
> 1368x768 59.88 59.85
> 1360x768 59.80 59.96
>...

[Dave Chiluk (chiluk)]

I'm having a similar issue in Jammy again with an HDMI connected 2k monitor. The issue here being that the monitor works on boot up, but experiences this problem after a few hot plugs. Has someone found a follow-on ticket similar to this?

[Daniel van Vugt (vanvugt)]

Dave,

The first thing to check is whether new cables fix the problem.

The second thing to check is whether the latest development kernel already has a fix that works for you:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/

Third is to report your own bug upstream:
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs

It's best that everyone reports their own issue upstream because the root causes of these bugs are so hidden that the solutions are likely to be different for different people.

[Andy Hardwick (mintalone)]

I am not convinced this is a bug. I've had the same issue with an LG ultrawide (2560x1080) ever since kernel +4.5.7. Linux Mint 18 (4.4 kernel) the monitor worked at its native resolution out of the box. LM19 (think it was a 4.15 kernel) max is 1920x1080 unless you manually set the resolution with xrandr. Did some testing and the last kernel to 'work' was 4.5.7.

I think the problem lies in the EDID implementation by LG. read-edid | parse-edid will list all the modes. 2560x1080 is mode 0, 1920x1020 is mode 11. The "PreferredMode" output by read-edid is mode 11. That I think is the problem. I have no idea how the "PreferredMode" is determined from the EDID.