Bug 540783 - Monitor size is wrong in dpyinfo
Summary: Monitor size is wrong in dpyinfo
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 15
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-24 05:15 UTC by Pete Zaitcev
Modified: 2018-04-11 16:13 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-07 19:32:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (71.98 KB, text/plain)
2011-03-15 18:26 UTC, Matthias Berndt
no flags Details
/var/log/messages (69.10 KB, text/plain)
2011-03-15 18:27 UTC, Matthias Berndt
no flags Details
Xorg log (44.79 KB, text/plain)
2011-03-15 18:27 UTC, Matthias Berndt
no flags Details
edid data from my monitor, perhaps it matters... (128 bytes, text/plain)
2011-03-15 18:30 UTC, Matthias Berndt
no flags Details
Xorg.0.log (67.25 KB, text/plain)
2011-03-17 17:24 UTC, Pete Zaitcev
no flags Details
dmesg (123.35 KB, text/plain)
2011-03-17 17:24 UTC, Pete Zaitcev
no flags Details
messages (36.47 KB, text/plain)
2011-03-17 17:25 UTC, Pete Zaitcev
no flags Details


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 25615 0 None None None Never

Description Pete Zaitcev 2009-11-24 05:15:07 UTC
Description of problem:

When I run dpyinfo, the result is:
screen #0:
  dimensions:    1440x900 pixels (381x238 millimeters)
  resolution:    96x96 dots per inch

However, actual measurements are 303x189 mm.

Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg-1.7.1-7.fc12.x86_64

Additional info:

The difference is noticeable, about a quarter off. So, everything is
really small and hard to read. The weird thing is, if I run
gnome-display-properties, it detects correct size (14").

IIRC there was an option DisplaySize in Monitor section in xorg.conf,
but this is a fully auto-configured system. There's no xorg.conf.

Comment 1 Bug Zapper 2010-11-04 05:32:42 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Matthias Berndt 2011-03-12 14:14:12 UTC
This bug is still present in Fedora 14. 

# xdpyinfo | grep dimensions
  dimensions:    1280x1024 pixels (338x270 millimeters)
# monitor-edid | grep size
Screen size: 37.0 cm x 30.0 cm (18.75 inches, aspect ratio 5/4 = 1.25)

I'm using the radeon driver with the integrated graphics chip on a Gigabyte GA-MA785GM-US2H mainboard (it uses an RS880 chip).

Comment 3 Matěj Cepl 2011-03-13 00:56:37 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 4 Matthias Berndt 2011-03-15 18:26:36 UTC
Created attachment 485571 [details]
dmesg

Comment 5 Matthias Berndt 2011-03-15 18:27:01 UTC
Created attachment 485572 [details]
/var/log/messages

Comment 6 Matthias Berndt 2011-03-15 18:27:23 UTC
Created attachment 485573 [details]
Xorg log

Comment 7 Matthias Berndt 2011-03-15 18:30:01 UTC
Created attachment 485574 [details]
edid data from my monitor, perhaps it matters...

Comment 8 Matthias Berndt 2011-03-16 13:26:36 UTC
I'd say that this is probably a bug in the radeon xorg driver. In the X.org log it says in one place:
[    22.832] (II) RADEON(0): EDID for output VGA-0
...
[    22.833] (II) RADEON(0): Max Image Size [cm]: horiz.: 37  vert.: 30

and later on it says 
[    22.868] (II) RADEON(0): Setting screen physical size to 338 x 270

So for whatever reason, it just ignores the EDID data it parsed earlier on.

Comment 10 Pete Zaitcev 2011-03-16 17:09:57 UTC
Of course I do care, just stuck on vacation while Mattias is hijacking
my bug instead of filing a separate one. I don't have a Radeon, BTW.

Comment 11 Matěj Cepl 2011-03-16 23:51:46 UTC
(In reply to comment #10)
> Of course I do care, just stuck on vacation while Mattias is hijacking
> my bug instead of filing a separate one. I don't have a Radeon, BTW.

Could we get updated logs (see comment 3) then, please?

Matthias, could I ask you to file a separate bug for your problem please?

Thank you

Comment 12 Matthias Berndt 2011-03-17 13:24:27 UTC
Pete, this isn't "your" bug, and I didn't "hijack" it. I merely did what every bug reporter is supposed to do: check for duplicates before filing a redundant new bug.

And I personally still don't see the point in filing a new bug since after all, I have the same problem as Pete. The fact that he doesn't have a Radeon doesn't necessarily mean that the cause is not the same.

Comment 13 Pete Zaitcev 2011-03-17 17:20:08 UTC
I agree that the cause may end the same for our hardware. The speculation in
comment #8 was not based on code.

Comment 14 Pete Zaitcev 2011-03-17 17:24:05 UTC
Created attachment 486071 [details]
Xorg.0.log

Comment 15 Pete Zaitcev 2011-03-17 17:24:33 UTC
Created attachment 486072 [details]
dmesg

Comment 16 Pete Zaitcev 2011-03-17 17:25:09 UTC
Created attachment 486073 [details]
messages

Comment 17 Pete Zaitcev 2011-03-17 17:31:55 UTC
Here's an equivalent of comment #8:

[    39.149] (II) intel(0): EDID for output LVDS1
.....
[    39.149] (II) intel(0): Max Image Size [cm]: horiz.: 30  vert.: 19
.....
[    35.692] (**) intel(0): Display dimensions: (300, 190) mm
[    35.692] (**) intel(0): DPI set to (121, 120)
.....
[    35.918] (II) GLX: Initialized DRI2 GL provider for screen 0
[    35.919] (II) intel(0): Setting screen physical size to 381 x 238

Comment 18 Matthias Berndt 2011-03-28 15:02:11 UTC
So what's going to happen how? Will this be reported upstream? Or will we have to wait another year and a half for anything to happen?

Comment 19 Felipe Contreras 2011-05-25 11:20:23 UTC
Same on nouveaou.

[ 13260.376] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34  vert.: 19
[ 13260.832] (II) NOUVEAU(0): Setting screen physical size to 508 x 285

Comment 20 Felipe Contreras 2011-05-25 11:30:42 UTC
(In reply to comment #18)
> So what's going to happen how? Will this be reported upstream? Or will we have
> to wait another year and a half for anything to happen?

It's already there:
https://bugs.freedesktop.org/show_bug.cgi?id=25615

Comment 22 Pete Zaitcev 2011-08-01 22:17:10 UTC
Still broken (obviously - the upstream does not appear to be very interested)
xorg-x11-server-Xorg-1.10.3-1.fc15.x86_64
xorg-x11-drv-intel-2.15.0-5.fc15.x86_64

Comment 23 Fedora End Of Life 2012-08-07 19:32:19 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 24 Pete Zaitcev 2013-08-01 16:01:45 UTC
This may be interesting, a note by Adam:
 https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/xsettings/gsd-xsettings-manager.c#n67

Of course nothing he's saying is helping one bit to the people who
own a properly working hardware that reports sizes correctly, and
those sizes are then discarded.


Note You need to log in before you can comment on or make changes to this bug.