[Bug 82619] [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 27 03:44:45 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=82619

--- Comment #68 from Martin Andersen <martin.x.andersen at gmail.com> ---
Some additional information, which may or may not be relevant to this bug.

There are still issues with Xorg being able to set the correct modes for
dual-head, specifically the refresh rate.

With 13.04, setting 24Hz & 23.976Hz on HDMI2 was not an issue (worked well,
24Hz set on true 24Hz content, and 23.976Hz set on U.S-hobbled
24Hz=((24*1000)/1001 content). With the newer drivers from 14.04 (using the
latest 01.org provided ones), xrandr tries to set this (seemingly
successfully), but the output is always running on 60Hz regardless.

It is the same behaviour for 50Hz as well (which is stuck at 60). The main LCD
monitor is running on 60Hz, but even turning the monitor off (or using XBMCs
'blank other displays' setting has zero effect.)

However, this occurs independently of running XBMC or not. 
(The problem can also be verified from the desktop.)

Driver version rehash:

- i965-va-driver:amd64       1.3.2-1
- libva1:amd64               1.3.1-3
- libdrm2:amd64              2.4.54
- xserver-xorg-video-intel   2.99.911

Modes seen by xrandr:

Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 32767 x 32767
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected primary 1920x1200+0+0 (normal left inverted right x axis y
axis) 518mm x 324mm
   1920x1200      59.6*+   60.0     59.6* 
   1024x768       60.0 +   75.1     75.0     70.1     60.0  
   1920x1080      60.0     60.2  
   1600x1200      60.0     60.1  
   1280x1024      76.0     76.0     75.0     60.0     60.0     60.0  
   1152x921       66.0     66.0  
   1152x864       75.0  
   832x624        74.6     74.5  
   800x600        72.2     75.0     60.3     56.2  
   640x480        75.0     72.8     75.0     72.8     66.7     60.0     60.0  
   720x400        70.1  
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+1920+0 (normal left inverted right x axis y axis)
1600mm x 900mm
   1920x1080      60.0*+   50.0     59.9     24.0     24.0  
   1920x1080 at 60   60.0  
   1920x1080 at 50   50.0  
   1920x1080 at 59.94p   59.9  
   1920x1080i at 60   60.1  
   1920x1080i at 50   50.0  
   1920x1080 at 24   24.0     24.0  
   1920x1080i     60.1     50.0     60.0  
   1280x720 at 60    60.0  
   1280x720 at 50    50.0  
   1280x720       60.0     50.0     59.9  
   1440x576 at 50    50.0  
   1440x576       50.0  
   1440x576i at 50   50.1  
   1440x480       60.0     59.9  
   1440x480 at 59.9   59.9  
   1440x480i at 59.9   60.1  
   720x576 at 50     50.0  
   720x576        50.0  
   720x576i       50.1  
   720x480        60.0     59.9  
   720x480 at 59.9   59.9  
   720x480i       60.1     60.1  
   640x480 at 60     60.0     60.0  
   640x480        60.0     59.9  
   640x480 at 59.9   60.0  
DP2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Running 'xrandr --output HDMI2 --mode 1920x1080 at 24' from within the desktop
tries to set 24Hz, but still outputs 60Hz regardless.

Surely I can't be the only one experiencing this issue? (are there really that
few people running XBMC on Intel w/ dual-head?)

btw.-this is my fourth upgrade (and subsequent immediate downgrade) on this
system from 13.04 to 13.10 & 14.04–assumed to be the final one–as XBMC was
worked around to correctly start on the second display with the latest patches.
But obviously the picture is juddery as hell trying to output 23.976Hz on a
60Hz display (especially when the video renderer _thinks_ it is on the correct
refresh rate).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141027/331a9520/attachment.html>


More information about the intel-gfx-bugs mailing list