2014-07-31, 13:14
[If there are any others on here successfully using a dual-display on Intel hw with a recent distro, i.e, a desktop on one output + XBMC on the other–please give a shout out, as I've been trying to get this working for the better part of a week on numerous different installations and intellinux/01.org driver version combinations]
First off: I am not 100% certain that this is actually related to a fault in XBMC. So far, it appears to be related to the recent ABI changes in Xorg or a change in Intel's drivers. Especially since this works _perfectly_ on 13.04, using exactly the same (and current) XBMC versions I've tested (both mainline and FernetMenta's branches.)
In any case, I am trying to get to the bottom of exactly which component is causing this. So far, I've ruled out libva/libva-intel-driver, and also, most likely, libdrm.
Testing older versions of the driver components have proven to be a real *PITA*, as they are closely linked wrt. functionality. I had initially suspected the 'xserver-xorg-video-intel' (intel_drv.so) or xorg itself as being the culprit, but I haven't been able to verify this, as running an older Xorg with current drivers is impossible due to the recent ABI changes. For the record, the last known good version of xserver-xorg-video-intel (xf86-video-intel on Arch) is 2.21.9.
I am really struggling to figure out what is causing this, and specifically, where (and to whom) any bug report can be filed.
DE-specific issues have been ruled out completely. The error exists on all environments I've tried:
- IceWM
- Cinnamon (which works perfectly on 13.04)
- Fluxbox
- XFCE4
- Unity
- Mate
- Gnome
- etc.
When changing video output ports, it lists the second output, changes to it (presumably successfully as far as XBMC is concerned), and displays the output on the same port as what was initially used. When selecting 'blank other displays', it blanks the primary display(!), but still does not change the display to the port selected.
I've tested this on Ivy Bridge, Haswell and on Sandy Bridge systems using various combinations of HDMI, VGA, DVI & DisplayPort outputs. They all behave the same.
First off: I am not 100% certain that this is actually related to a fault in XBMC. So far, it appears to be related to the recent ABI changes in Xorg or a change in Intel's drivers. Especially since this works _perfectly_ on 13.04, using exactly the same (and current) XBMC versions I've tested (both mainline and FernetMenta's branches.)
In any case, I am trying to get to the bottom of exactly which component is causing this. So far, I've ruled out libva/libva-intel-driver, and also, most likely, libdrm.
Testing older versions of the driver components have proven to be a real *PITA*, as they are closely linked wrt. functionality. I had initially suspected the 'xserver-xorg-video-intel' (intel_drv.so) or xorg itself as being the culprit, but I haven't been able to verify this, as running an older Xorg with current drivers is impossible due to the recent ABI changes. For the record, the last known good version of xserver-xorg-video-intel (xf86-video-intel on Arch) is 2.21.9.
I am really struggling to figure out what is causing this, and specifically, where (and to whom) any bug report can be filed.
DE-specific issues have been ruled out completely. The error exists on all environments I've tried:
- IceWM
- Cinnamon (which works perfectly on 13.04)
- Fluxbox
- XFCE4
- Unity
- Mate
- Gnome
- etc.
When changing video output ports, it lists the second output, changes to it (presumably successfully as far as XBMC is concerned), and displays the output on the same port as what was initially used. When selecting 'blank other displays', it blanks the primary display(!), but still does not change the display to the port selected.
I've tested this on Ivy Bridge, Haswell and on Sandy Bridge systems using various combinations of HDMI, VGA, DVI & DisplayPort outputs. They all behave the same.