Comment 5 for bug 835945

Yes, exactly, it's not a bug on the driver; I think fglrx does it well just ignoring the wrong EDID data and forcing the refresh rate he thinks can work.
I marked the old report as a duplicate of this: I did have only this computer and no secondary pc nor monitor to test this bug, so I had to wait for months before filing a complete report... sorry for that, at least now we have a complete view of the problem :) thanks Tormod :)