Bug 72418 - intel-virtual-output: exits w/o error, doesn't seem to do anything
Summary: intel-virtual-output: exits w/o error, doesn't seem to do anything
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-06 21:06 UTC by Tom
Modified: 2013-12-07 01:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Tom 2013-12-06 21:06:34 UTC
Forgive me if this isn't really a bug; I've been trying very hard to understand how `intel-virtual-output` should work/be used and I've yet to successfully make it do anything.

Here's my process:

1. Start X
2. Ensure `xrandr --listproviders` contains both my video cards
3. Connect external monitor to dock (hardwired to the discrete GPU)
4. Call `intel-virtual-output`

At this point, the command simply exits without any output. I have tried specifying the "source display" argument as :0 (or whatever my X display happens to be); the command doesn't exit, but doesn't appear to do anything else either. If I enable the VIRTUAL1 display, I just get an extended desktop I can't access and the external monitor remains dark.

I am probably just using the tool incorrectly but since Google provided no usage instructions and the manpage is rather spartan, I figured I'd give this a shot.
Comment 1 Chris Wilson 2013-12-06 21:58:22 UTC
If you are using outputproviders (aka PRIME) then you do not need intel-virtual-output and can do everything with the appropriate "xrandr --setprovideroutputsource" command. intel-virtual-output is for the hybrid case with old propietary drivers that lack PRIME integration. In such cases, intel-virtual-output will launch and go in the background, and listen to randr commands to set up the VIRTUAL outputs which will then be aliased to outputs on the discrete GPU.
Comment 2 Tom 2013-12-07 01:14:19 UTC
Oh, well that explains a lot then! Now, to figure out why X segfaults when I use that ;)

Thanks!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.