Bug 91446 - Unable to disable and enable outputs on the same command line with xrandr
Summary: Unable to disable and enable outputs on the same command line with xrandr
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-24 07:10 UTC by Vincent Bernat
Modified: 2017-04-11 12:27 UTC (History)
1 user (show)

See Also:
i915 platform: IVB
i915 features:


Attachments
xrandr --verbose output (17.34 KB, text/plain)
2015-07-24 07:10 UTC, Vincent Bernat
no flags Details

Description Vincent Bernat 2015-07-24 07:10:34 UTC
Created attachment 117333 [details]
xrandr --verbose output

Hey!

When I dock my laptop, I would like to switch to the external screens with the following command:

xrandr --output eDP1 --off --output DP2-1 --auto --primary \
       --output DP2-2 --auto --right-of DP2-1 --dpi 96

Unfortunately, I get:

xrandr: Configure crtc 1 failed

There is no problem if I use two steps:

xrandr --output eDP1 --off --output DP2-1 --auto --primary
xrandr --output DP2-2 --auto --right-of DP2-1 --dpi 96

But it sometimes confuse my window manager (two reconfigure events in a very short time).

Another oddity is that I have enough CRTC to get the three screens running. When not turning off eDP1, everything works as expected.

X.org 7.7 from Debian Sid.
Intel driver 2.99.917.

The laptop is a Lenovo Carbon X1 and the external screens are plugged through a dock using MST.
Comment 1 Chris Wilson 2015-07-24 08:58:49 UTC
Should be fixed in xrandr by

commit 3d03be780fca4949b11ead46c5ea5d3266c03c32
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jun 18 08:27:49 2015 +0100

    Mark all CRTC as currently unused for second picking CRTC pass

commit 53ef3fc13b3e282902892e3140765460c6f93276
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Thu Jun 18 08:27:48 2015 +0100

    Mark disabling an output as a change in its CRTC
Comment 2 Vincent Bernat 2015-07-24 11:25:21 UTC
Just tried 1.4.3 and adding the two mentioned patches and no luck, same message.
Comment 3 Vincent Bernat 2015-07-28 15:45:35 UTC
Since libxrandr 1.5.0 has landed in Debian/sid, I have also tried the xrandr HEAD without any change.

ii  libxrandr2:amd64  2:1.5.0-1     amd64         X11 RandR extension library

What kind of debug log can I provide?
Comment 4 Chris Wilson 2015-07-29 20:57:50 UTC
There is not much in the way of debugging inside xrandr, if you fancy adding printf()s everywhere to figure out why it does what it does that would be useful. Or you can wait a bit until I have a go myself at adding debug...
Comment 5 Vincent Bernat 2015-08-10 09:07:09 UTC
Just for information, doing that also leads to the same error:

            xrandr \
                --output DP2-1 --auto --primary \
                --output DP2-2 --auto --right-of DP2-1 \
                --output eDP1 --auto --right-of DP2-2 --scale-from 1600x900 \
                --dpi 96

Putting eDP1 first also leads to the same error.
Comment 6 Vincent Bernat 2016-03-04 19:36:12 UTC
I still have the same problems with the following versions:
 - 2:2.99.917+git20160218-1
 - xrandr 1.5.0
 - kernel 4.4
 - X Server 1.18.1

However, when using the mode setting driver instead (0.9.0), I don't have the problem (however, it doesn't support scaling which I need from time to time).
Comment 7 yann 2017-03-16 13:22:10 UTC
(In reply to Vincent Bernat from comment #6)
> I still have the same problems with the following versions:
>  - 2:2.99.917+git20160218-1
>  - xrandr 1.5.0
>  - kernel 4.4
>  - X Server 1.18.1
> 
> However, when using the mode setting driver instead (0.9.0), I don't have
> the problem (however, it doesn't support scaling which I need from time to
> time).


We seem to have neglected the bug a bit, apologies.

Vincent Bernat, since There were improvements pushed in kernel & xrand that will benefit to your system, so please re-test with latest kernel &xrand and mark as REOPENED if you can reproduce (and attach fresh xrand log & kernel log) and RESOLVED/* if you cannot reproduce.
Comment 8 yann 2017-04-11 12:27:45 UTC
(In reply to yann from comment #7)
> (In reply to Vincent Bernat from comment #6)
> > I still have the same problems with the following versions:
> >  - 2:2.99.917+git20160218-1
> >  - xrandr 1.5.0
> >  - kernel 4.4
> >  - X Server 1.18.1
> > 
> > However, when using the mode setting driver instead (0.9.0), I don't have
> > the problem (however, it doesn't support scaling which I need from time to
> > time).
> 
> 
> We seem to have neglected the bug a bit, apologies.
> 
> Vincent Bernat, since There were improvements pushed in kernel & xrand that
> will benefit to your system, so please re-test with latest kernel &xrand and
> mark as REOPENED if you can reproduce (and attach fresh xrand log & kernel
> log) and RESOLVED/* if you cannot reproduce.

Timeout - assuming resolved+fixed.

If problem still persist with the latest kernels (preferable drm-tip from git://anongit.freedesktop.org/git/drm-tip), reopen this bug with latest logs as attachments.


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.