http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #12 from Egbert Eich <eich@suse.com> --- (In reply to Takashi Iwai from comment #10)
Then it's the result of the recent "fix". The driver became more strict and prunes the invalid modes for DVI. Some monitors allow higher clocks than specification (like yours), but these are filtered out now.
The reasoning behind this is a bit more complicated even: DVI does support these modes, this is why the monitor lists them in the EDID on a DVI connector. On DVI these modes are however only specified for dual link which Intel doesn't support. For single link DVI has a clock limit of 165MHz. HDMI is compatible with single link DVI, however has a higher clock limit. The intel driver uses this higher clock limit (on most chips) if it detects an HDMI sink. Then it depends if the monitor supports these modes over its HDMI port.
As a workaround, you can still add the mode manually via xrandr, and use it explicitly. For example,
This workaround will work for X, not console - the kernel allows all modes (even invalid ones) to be specified from user space. This way one can sneak in a mode which should not work according to the specs but still works on a certain piece of hardware. But since the driver no longer takes modes from the EDID the mode needs to be added explicitely, -- You are receiving this mail because: You are on the CC list for the bug.