RandR 1.5 Monitors: "No monitor named '...'"

[Aaron Plattner]

On 09/15/2016 12:56 PM, Nathan Schulte wrote:
> Thanks for the reply, Aaron.  I assume then I've stumbled upon an issue
> w/ this version of xrandr / X's RandR 1.5 impl?
>
> On 09/14/2016 11:16 AM, Aaron Plattner wrote:
>> There is supposed to be a "ConnectorNumber" property that you can use to
>> correlate these RandR outputs with physical connectors.
>>
>> https://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt?id=cf3272717e08325f69bdbb759ab35cb4d1839fb7#n1931
>>
>>
>> E.g., on my system, these two are halves of the same mini-DisplayPort
>> connector:
>>
>> DP-4 disconnected (normal left inverted right x axis y axis)
>>     CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
>>     BorderDimensions: 4
>>         supported: 4
>>     Border: 0 0 0 0
>>         range: (0, 65535)
>>     SignalFormat: DisplayPort
>>         supported: DisplayPort
>>     ConnectorType: DisplayPort
>>     ConnectorNumber: 1
>>     _ConnectorLocation: 1
>
> Aaron, what did you use to produce that output?  I see something similar
> w/ the output of xrandr (note the "Clones" and "CRTC" and "CRTCs"
> properties).  If I understand correctly, all of these outputs are from
> the Intel Haswell HD 4600, and none from the AMD Radeon.

It was "xrandr --prop" with the NVIDIA driver since that's what I work 
on. --verbose should also print the properties so if you're not seeing 
them, then it sounds like the Intel driver isn't providing them.

>> $ xrandr --version
>> xrandr program version       1.5.0
>> Server reports RandR version 1.5
>
>> $ xrandr --verbose
>> Screen 0: minimum 8 x 8, current 3600 x 3840, maximum 32767 x 32767
>> eDP1 connected (normal left inverted right x axis y axis)
>>     Identifier: 0x79
>>     Timestamp:  56437148
>>     Subpixel:   unknown
>>     Clones:
>>     CRTCs:      0 1 2
>> --- snip ---
>> DP1 disconnected (normal left inverted right x axis y axis)
>>     Identifier: 0x7a
>>     Timestamp:  56437148
>>     Subpixel:   unknown
>>     Clones:     HDMI1
>>     CRTCs:      0 1 2
>> --- snip ---
>> DP2 connected primary 1200x3840+0+0 (0x13b) left (normal left inverted
>> right x axis y axis) 580mm x 360mm
>>     Identifier: 0x7b
>>     Timestamp:  56437148
>>     Subpixel:   unknown
>>     Gamma:      1.0:1.0:1.0
>>     Brightness: 1.0
>>     Clones:     HDMI3
>>     CRTC:       0
>>     CRTCs:      0 1 2
>> --- snip ---
>> HDMI1 connected 1200x1920+2400+0 (0x13a) left (normal left inverted
>> right x axis y axis) 580mm x 360mm
>>     Identifier: 0x7c
>>     Timestamp:  56437148
>>     Subpixel:   unknown
>>     Gamma:      1.0:1.0:1.0
>>     Brightness: 1.0
>>     Clones:     DP1
>>     CRTC:       1
>>     CRTCs:      0 1 2
>> --- snip ---
>> HDMI2 connected 1200x1920+1200+0 (0x13a) left (normal left inverted
>> right x axis y axis) 580mm x 360mm
>>     Identifier: 0x7d
>>     Timestamp:  56437148
>>     Subpixel:   unknown
>>     Gamma:      1.0:1.0:1.0
>>     Brightness: 1.0
>>     Clones:
>>     CRTC:       2
>>     CRTCs:      0 1 2
>> --- snip ---
>> HDMI3 disconnected (normal left inverted right x axis y axis)
>>     Identifier: 0x7e
>>     Timestamp:  56437148
>>     Subpixel:   unknown
>>     Clones:     DP2
>>     CRTCs:      0 1 2
>> --- snip ---
>> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
>>     Identifier: 0x7f
>>     Timestamp:  56437148
>>     Subpixel:   no subpixels
>>     Clones:
>>     CRTCs:      3
>> --- snip ---
>
> I'm still not sure how or why I would use this VIRTUAL1 output; I can't
> help but wonder if it has to do w/ DRI Prime (hybrid graphics), but I
> guess it's not and is [necessary, and subsequently] used internally in
> the driver stack somehow else.
>
> --
> Nate
>