Comment 37 for bug 3731

I believe that the same class of problems are causing many monitor resolution/refresh rate problems as listed in bugs 50048, 27667 (these are the bugs I made comments on) and probably many more. The problems with the edid data.

The new Xorg server should be able to query monitor by itself for DDC edid info about it's capatibilities, without ddcprobe. This functionality works for me if I leave out monitor specific information from my Xorg.conf like this:
Section "Monitor"
    Identifier "Generic Monitor"
    Option "DPMS"
EndSection

In the edid there should be data for the recommended resolution and refresh rate. The problem is however that some monitors have this data wrong (so you don't get the right resolution or refresh rate), or the checksum of the complete data wrong (so you don't get the edid data used by X at all). Either way, could you send the output of the get-edid > yourmonitormakeandmodel.edid as attachment to this bug, and possibly the xorg mailing list, so we can see what's wrong with the data and add a quirk for it in the Xorg code? get-edid is in the read-edid package, and it's output can be piped to parse-edid to create the Xorg.conf monitor section). I'm not sure why the checksum for edid data for my monitor is incorrect, it's probably a quirk of my monitor, but for other cases where edid data is different on multiple runs of get-edid or Xorg, it might be best to permanently store this data to be used if nothing valid is detected on subsequent runs.

 If this gets done in time, it's quite possible that gutsy will finally have good out of the box monitor autodetection support.