Using Displayport over USB-C (Thunderbolt 3) to drive external 5120x2160 monitor; resolution not detected, cvt mode not working
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I bought a shiny new LG 34WK95U ultra-wide screen, which has a native resolution of 5120x2160 at 60Hz.
When connecting the monitor via a Thunderbolt 3 USB-C connection, it gets picked up, but it fails to probe for the correct resolution. Also, once connected, I now get two (!) new outputs. Here is my current xrandr:
% xrandr
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
# Snip; removed the laptop modes
DP-1 connected (normal left inverted right x axis y axis)
2560x2160 59.66
640x480 59.94
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 3440x1440+0+0 (normal left inverted right x axis y axis) 800mm x 330mm
3440x1440 59.97*+ 59.96 49.99
3840x2160 60.00 30.00
1920x1080 60.00 60.00 59.94
1600x900 60.00
1280x1024 60.02
1280x800 59.81
1152x864 59.97
1280x720 60.00 60.00 59.94
1024x768 60.00
800x600 60.32
720x480 60.00 59.94
640x480 60.00 59.94 59.94
5120x2160_60.00 59.99
5120x2160_30.00 29.98
HDMI-2 disconnected (normal left inverted right x axis y axis)
Those DP-1 and DP-2 popped up after I connected the USB-C to the external screen. I am not sure what the meaning of the second output is. Interestingly, when I did this the first time around, DP-1 had all the modes listed, and DP-2 only had those two right now under DP-1.
You can also see the additional modes I added, 5120x2160_60.00 and 5120x2160_30.00 by running % cvt 5120 2160 30 and 60 followed by xrandr --newmode and xrandr --addmode, respectively.
The result of calling xrandr with either of these two modes gives this:
% xrandr --output DP-2 --mode 5120x2160_30.00
xrandr: Configure crtc 0 failed
linux xrandr displayport
asked Dec 6 at 11:27
mSSM
1011
add a comment |
up vote
0
down vote
favorite
I bought a shiny new LG 34WK95U ultra-wide screen, which has a native resolution of 5120x2160 at 60Hz.
When connecting the monitor via a Thunderbolt 3 USB-C connection, it gets picked up, but it fails to probe for the correct resolution. Also, once connected, I now get two (!) new outputs. Here is my current xrandr:
% xrandr
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
# Snip; removed the laptop modes
DP-1 connected (normal left inverted right x axis y axis)
2560x2160 59.66
640x480 59.94
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 3440x1440+0+0 (normal left inverted right x axis y axis) 800mm x 330mm
3440x1440 59.97*+ 59.96 49.99
3840x2160 60.00 30.00
1920x1080 60.00 60.00 59.94
1600x900 60.00
1280x1024 60.02
1280x800 59.81
1152x864 59.97
1280x720 60.00 60.00 59.94
1024x768 60.00
800x600 60.32
720x480 60.00 59.94
640x480 60.00 59.94 59.94
5120x2160_60.00 59.99
5120x2160_30.00 29.98
HDMI-2 disconnected (normal left inverted right x axis y axis)
Those DP-1 and DP-2 popped up after I connected the USB-C to the external screen. I am not sure what the meaning of the second output is. Interestingly, when I did this the first time around, DP-1 had all the modes listed, and DP-2 only had those two right now under DP-1.
You can also see the additional modes I added, 5120x2160_60.00 and 5120x2160_30.00 by running % cvt 5120 2160 30 and 60 followed by xrandr --newmode and xrandr --addmode, respectively.
The result of calling xrandr with either of these two modes gives this:
% xrandr --output DP-2 --mode 5120x2160_30.00
xrandr: Configure crtc 0 failed
linux xrandr displayport
asked Dec 6 at 11:27
mSSM
1011
Guess: USB C alternate mode is not working properly (after all, support is quite new). What computer and what graphic card are you using? At least look into/var/log/Xorg.0.logto find out a bit more what the X server thinks it's doing. But very likely you'll have to file a bug with the USB C alternate mode developers (and if this is on a Mac, getting that to work will be difficult).
– dirkt
Dec 6 at 15:28
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I bought a shiny new LG 34WK95U ultra-wide screen, which has a native resolution of 5120x2160 at 60Hz.
When connecting the monitor via a Thunderbolt 3 USB-C connection, it gets picked up, but it fails to probe for the correct resolution. Also, once connected, I now get two (!) new outputs. Here is my current xrandr:
% xrandr
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
# Snip; removed the laptop modes
DP-1 connected (normal left inverted right x axis y axis)
2560x2160 59.66
640x480 59.94
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 3440x1440+0+0 (normal left inverted right x axis y axis) 800mm x 330mm
3440x1440 59.97*+ 59.96 49.99
3840x2160 60.00 30.00
1920x1080 60.00 60.00 59.94
1600x900 60.00
1280x1024 60.02
1280x800 59.81
1152x864 59.97
1280x720 60.00 60.00 59.94
1024x768 60.00
800x600 60.32
720x480 60.00 59.94
640x480 60.00 59.94 59.94
5120x2160_60.00 59.99
5120x2160_30.00 29.98
HDMI-2 disconnected (normal left inverted right x axis y axis)
Those DP-1 and DP-2 popped up after I connected the USB-C to the external screen. I am not sure what the meaning of the second output is. Interestingly, when I did this the first time around, DP-1 had all the modes listed, and DP-2 only had those two right now under DP-1.
You can also see the additional modes I added, 5120x2160_60.00 and 5120x2160_30.00 by running % cvt 5120 2160 30 and 60 followed by xrandr --newmode and xrandr --addmode, respectively.
The result of calling xrandr with either of these two modes gives this:
% xrandr --output DP-2 --mode 5120x2160_30.00
xrandr: Configure crtc 0 failed
linux xrandr displayport
asked Dec 6 at 11:27
mSSM
1011
I bought a shiny new LG 34WK95U ultra-wide screen, which has a native resolution of 5120x2160 at 60Hz.
When connecting the monitor via a Thunderbolt 3 USB-C connection, it gets picked up, but it fails to probe for the correct resolution. Also, once connected, I now get two (!) new outputs. Here is my current xrandr:
% xrandr
Screen 0: minimum 320 x 200, current 3440 x 1440, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
# Snip; removed the laptop modes
DP-1 connected (normal left inverted right x axis y axis)
2560x2160 59.66
640x480 59.94
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 3440x1440+0+0 (normal left inverted right x axis y axis) 800mm x 330mm
3440x1440 59.97*+ 59.96 49.99
3840x2160 60.00 30.00
1920x1080 60.00 60.00 59.94
1600x900 60.00
1280x1024 60.02
1280x800 59.81
1152x864 59.97
1280x720 60.00 60.00 59.94
1024x768 60.00
800x600 60.32
720x480 60.00 59.94
640x480 60.00 59.94 59.94
5120x2160_60.00 59.99
5120x2160_30.00 29.98
HDMI-2 disconnected (normal left inverted right x axis y axis)
Those DP-1 and DP-2 popped up after I connected the USB-C to the external screen. I am not sure what the meaning of the second output is. Interestingly, when I did this the first time around, DP-1 had all the modes listed, and DP-2 only had those two right now under DP-1.
You can also see the additional modes I added, 5120x2160_60.00 and 5120x2160_30.00 by running % cvt 5120 2160 30 and 60 followed by xrandr --newmode and xrandr --addmode, respectively.
The result of calling xrandr with either of these two modes gives this:
% xrandr --output DP-2 --mode 5120x2160_30.00
xrandr: Configure crtc 0 failed
linux xrandr displayport
linux xrandr displayport
asked Dec 6 at 11:27
mSSM
1011
asked Dec 6 at 11:27
mSSM
1011
asked Dec 6 at 11:27
mSSM
1011
asked Dec 6 at 11:27
mSSM
1011
asked Dec 6 at 11:27
mSSM
1011
1011
Guess: USB C alternate mode is not working properly (after all, support is quite new). What computer and what graphic card are you using? At least look into/var/log/Xorg.0.logto find out a bit more what the X server thinks it's doing. But very likely you'll have to file a bug with the USB C alternate mode developers (and if this is on a Mac, getting that to work will be difficult).
– dirkt
Dec 6 at 15:28
add a comment |
Guess: USB C alternate mode is not working properly (after all, support is quite new). What computer and what graphic card are you using? At least look into/var/log/Xorg.0.logto find out a bit more what the X server thinks it's doing. But very likely you'll have to file a bug with the USB C alternate mode developers (and if this is on a Mac, getting that to work will be difficult).
– dirkt
Dec 6 at 15:28
Guess: USB C alternate mode is not working properly (after all, support is quite new). What computer and what graphic card are you using? At least look into
/var/log/Xorg.0.log to find out a bit more what the X server thinks it's doing. But very likely you'll have to file a bug with the USB C alternate mode developers (and if this is on a Mac, getting that to work will be difficult).– dirkt
Dec 6 at 15:28
Guess: USB C alternate mode is not working properly (after all, support is quite new). What computer and what graphic card are you using? At least look into
/var/log/Xorg.0.log to find out a bit more what the X server thinks it's doing. But very likely you'll have to file a bug with the USB C alternate mode developers (and if this is on a Mac, getting that to work will be difficult).– dirkt
Dec 6 at 15:28
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486350%2fusing-displayport-over-usb-c-thunderbolt-3-to-drive-external-5120x2160-monitor%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486350%2fusing-displayport-over-usb-c-thunderbolt-3-to-drive-external-5120x2160-monitor%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Guess: USB C alternate mode is not working properly (after all, support is quite new). What computer and what graphic card are you using? At least look into
/var/log/Xorg.0.logto find out a bit more what the X server thinks it's doing. But very likely you'll have to file a bug with the USB C alternate mode developers (and if this is on a Mac, getting that to work will be difficult).– dirkt
Dec 6 at 15:28