XServer don't detect Display Resolution (not a driver problem)

[Johannes Fortner]

Binary package hint: xserver-xorg

Xorg don't detect right Display Resolution from iiyama Vision Master 501 Analog Monitor. Xorg detect a screen Resolution from 1024x768 by 60hz, but the monitor can do over 1280x1024 by 85hz.
Its not a problem of the graphic-card driver, i have tested it with some graphic-cards (nvidia, ati, intel onboard), always the same problem.
Xorg don't read the edid-data correct, disabling use edid in xorg-config solves the problem. But normally xorg must detect it automatically right, window§ detect it automatically.

I have the same problem on all other distros, too (tested: fedora, (open)suse, knopix).

[John Vivirito (gnomefreak)]

Have a look at this to see if it helps you http://help.ubuntu.com/community/FixVideoResolutionHowto

also can you attach var/log/Xorg.0.log and /etc/X11/xorg.conf files using attach file in the upper left of this screen thank you.

[Johannes Fortner (johannes-fortner)]

> Have a look at this to see if it helps you
> http://help.ubuntu.com/community/FixVideoResolutionHowto
Yes, by editing my xorg.conf-file I able to get the right screenresolution. But I think some users don't can do it.

> also can you attach var/log/Xorg.0.log and /etc/X11/xorg.conf files using attach > file in the upper left of this screen thank you.
Yes, but this not the automatic generated xorg.conf. I have it changed to fix the screenresolution problem. I hope it will help you to detect the matter off the broken automatic screen resolution detecting. If you need the original files, write me and I send you the files generated from the edgy livecd.

[doobydave (dooby-dave)]

I have iiyama vision master pro 510.

Dapper used to auto-detect it (but only with K7 kernel optimisation). Edgy, however, does not.

[Bryce Harrington (bryce)]

This is another example of bug 49827, which is quite common, so I'm marking this a dupe of that.

For Gutsy we're hoping to make more use of xorg monitor/device autodetection, which should make these misdetections less common.

We're also going to be including a GUI tool called displayconfig-gtk (you can apt-get an early version of this tool in Feisty, if you wish to preview). This way if it does misdetect, it will provide a user-friendly way to fix things.