On 9 April 2014 11:41, Dave Airlie <airlied@xxxxxxxxx> wrote: > On Tue, Apr 8, 2014 at 5:32 PM, Daniel J Blueman <daniel@xxxxxxxxx> wrote: >> On 8 April 2014 15:14, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote: >>> On Tue, 08 Apr 2014, Daniel J Blueman <daniel@xxxxxxxxx> wrote: >>>> Ville et al, >>>> >>>> It looks like commit e3ea8fa6beaf55fee64bf816f3b8a80ad733b2c2 (or >>>> another commit in 3.13.7) broke modes which require DVI-D dual-link, >>>> eg 2560x1440 with my panel. >>>> >>>> I don't see these modelines in 3.13.7 or later (eg 3.14): >>>> >>>> [ 5.582] (II) intel(0): Modeline "2560x1440"x60.0 312.25 2560 >>>> 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync (89.5 kHz eP) >>>> [ 5.582] (II) intel(0): Modeline "2560x1440"x60.0 312.25 2560 >>>> 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync (89.5 kHz eP) >>>> [ 5.582] (II) intel(0): Modeline "1920x1200"x59.9 193.25 1920 >>>> 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync (74.6 kHz e) >>>> >>>> My monitor is a Dell U2713HM; mobo uses an H87 chipset with i5-4670. >>> >>> By allowing those modes we regressed setups which were not capable of >>> displaying them. So you've got an HDMI->DVI converter? >>> >>> https://bugzilla.kernel.org/show_bug.cgi?id=72961 >> >> I am using a dual-link DVI-D to DVI-D cable to this monitor, since I >> previously couldn't get 2560x1440 via HDMI. > > Intel hw has dual-link DVI-D? I'm not sure I've ever seen that, is > this SDVO device or plain DVI-D? It's the DVI-D connector on: https://www.asus.com/Motherboards/H87IPLUS/ However, it is logically detected as HDMI-0: $ xrandr Screen 0: minimum 320 x 320, current 2560 x 1440, maximum 32767 x 32767 VGA-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 600mm x 340mm 2560x1440 60.0*+ 1920x1200 59.9 1920x1080 60.0 1600x1200 59.9 1680x1050 59.9 1280x1024 74.9 59.9 1280x800 59.8 1152x864 74.8 1024x768 74.9 59.9 800x600 74.9 60.3 640x480 74.8 59.4 720x400 69.8 HDMI-1 disconnected (normal left inverted right x axis y axis) Using the mobo HDMI socket and a HDMI to dual-link DVI-D cable (logically detected as HDMI-1), the same patch causes the same issue. Thanks, Daniel -- Daniel J Blueman _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx