|Summary:||300x230mm reported incorrectly by xdpyinfo for IVM 46ac monitor|
|Product:||xorg||Reporter:||Bryce Harrington <bryce>|
|Component:||Server/General||Assignee:||Xorg Project Team <xorg-team>|
|Status:||RESOLVED MOVED||QA Contact:||Xorg Project Team <xorg-team>|
|Priority:||medium||CC:||alex, bugzi11.fdo.tormod, hramrach, jan.baier, pali.rohar|
|i915 platform:||i915 features:|
Description Bryce Harrington 2008-04-23 14:43:09 UTC
I'm forwarding this bug report from a Ubuntu user: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/201491 With a Iiyama monitor, xdpyinfo reports 300x230mm yet the actual physical size differs. Xorg.0.log lists the correct dimensions (no mention of 300x230mm in the log), and ddcprobe and xrandr also both report the correct dimensions. Looking through the xdpyinfo code and referring to xlib's implementation of DisplayHeightMM() and DisplayWidthMM(), I didn't spot code that manipulates those values or sets them to default values, so my guess is the EDID from the monitor simply needs quirked? Does it need quirk_detailed_use_maximum_size() like the LPL monitors? Iiyama ProLite E431S, ATI Radeon 9800 Pro, DVI, -ati Manufacturer: IVM Model: 46ac Serial#: 16832 == Original Report == Binary package hint: xorg It seems tools like xdpyinfo are reporting screen sizes as 300x230 mm in a lot of cases when they are not. On my own Iiyama ProLite E431S with an ATI Radeon 9800 Pro connected over DVI using the "ati" driver, I get this from xdpyinfo: screen #0: dimensions: 1280x1024 pixels (300x230 millimeters) resolution: 108x113 dots per inch ddcprobe correctly detects the screen physical dimensions: screensize: 34 27 In another report, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/201032 the reporter shows that xdpyinfo quotes: screen #0: dimensions: 1280x800 pixels (300x230 millimeters) resolution: 108x88 dots per inch and ddcprobe reports: screensize: 33 21 Notice that the screens are actually different dimensions, both in physical terms and pixel terms, yet xdpyinfo thinks they are 300x230 mm. Also, the other reporter is using the intel driver. This did indeed used to work correctly in the early Hardy alphas, and previous releases of Ubuntu. ====== [Note that the bug the user references is about a LGPhilipsLCD LP154W01-TLD (LPL prod id 48128) monitor, which might be similar to the LGPhilipsLCD LP154W01-A5 from bug #10304, which is quirked with quirk_detailed_use_maximum_size().]
Comment 1 Bryce Harrington 2008-04-23 15:01:42 UTC
http://launchpadlibrarian.net/13009368/Xorg.0.log ddcprobe thinks: 34 x 27 (cm) (approx. 95.6 x 96.3 dpi) - Correct! So radeon thinks 340 x 270 (mm) - yep... correct xrandr thinks 340mm x 270mm - correct xdpyinfo thinks 300 x 230 ((approx. 108.4 x 113.1 dpi) WRONG!
Comment 2 Alexander Jones 2008-04-23 15:21:39 UTC
In case it wasn't obvious, this only became an issue fairly recently. In Ubuntu 7.10 which shipped Xorg 7.3 (I think), this seemed to work OK.
Comment 3 Bryce Harrington 2009-01-21 23:50:13 UTC
Comment 4 Michal Suchanek 2012-04-25 02:12:26 UTC
Xorg reports wrong screen size by design. See bug 23705
Comment 5 Tom Mittelstädt 2016-09-13 18:31:59 UTC
This bug is still present. xdpyinfo reports always 96x96 dpi resulting in wrong screen dimensions and incorrect scaling. $ xdpyinfo | grep -B2 resolution screen #0: dimensions: 3840x2160 pixels (1016x571 millimeters) resolution: 96x96 dots per inch however, xrandr is right; $ xrandr | grep DP1 DP1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
Comment 6 Jan Baier 2016-12-15 09:41:36 UTC
I have something maybe related to this problem. Incorrect resolution detected: screen #0: dimensions: 5120x1024 pixels (1354x270 millimeters) resolution: -2147483648x-2147483648 dots per inch More on https://bugs.launchpad.net/xorg-server/+bug/1650192
Comment 7 Pali Rohár 2018-03-12 19:26:51 UTC
xdpyinfo on XRandR 1.2+ screen really reports wrong DPI information. Last version of patch for xdpyinfo which fixes this problem is there: https://lists.x.org/archives/xorg-devel/2017-May/053743.html Also this patch (v2) fixes reporing of negative values in resolution information.
Comment 8 GitLab Migration User 2018-12-13 22:19:29 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/xorg/xserver/issues/366.