Can't setup monitor after reconnecting ThinkPad T570 to USB-C dock The Next CEO of Stack OverflowHow to configure Xorg for a dynamic dual monitor setupUsing xrandr freezes computer completelyCannot use highest resolution, xrandr does not list mode (Intel GPU, DP to DVI adapter)Can't get my secondary monitor to power on in X11xrandr not activating laptop displayxrandr only lists mode after a while of waitingxrandr: cannot find mode on startupDisplay on laptop doesn't work if I connect it to a monitor firstCannot use more than 2 monitors at a timexrandr: Display Desktop on TV
How do I go from 300 unfinished/half written blog posts, to published posts?
What's the best way to handle refactoring a big file?
What can we do to stop prior company from asking us questions?
Why is the US ranked as #45 in Press Freedom ratings, despite its extremely permissive free speech laws?
Skipping indices in a product
If a black hole is created from light, can this black hole then move at speed of light?
How did the Bene Gesserit know how to make a Kwisatz Haderach?
Interfacing a button to MCU (and PC) with 50m long cable
How do we know the LHC results are robust?
Why does standard notation not preserve intervals (visually)
Contours of a clandestine nature
Giving the same color to different shapefiles in QGIS
What do "high sea" and "carry" mean in this sentence?
How should I support this large drywall patch?
Why does the UK parliament need a vote on the political declaration?
FBX seems to be empty when imported into Blender
Novel about a guy who is possessed by the divine essence and the world ends?
What does convergence in distribution "in the Gromov–Hausdorff" sense mean?
Different harmonic changes implied by a simple descending scale
Anatomically Correct Strange Women In Ponds Distributing Swords
Is there an analogue of projective spaces for proper schemes?
How did people program for Consoles with multiple CPUs?
"and that skill is always a class skill for you" - does "always" have any meaning in Pathfinder?
If/When UK leaves the EU, can a future goverment conduct a referendum to join the EU?
Can't setup monitor after reconnecting ThinkPad T570 to USB-C dock
The Next CEO of Stack OverflowHow to configure Xorg for a dynamic dual monitor setupUsing xrandr freezes computer completelyCannot use highest resolution, xrandr does not list mode (Intel GPU, DP to DVI adapter)Can't get my secondary monitor to power on in X11xrandr not activating laptop displayxrandr only lists mode after a while of waitingxrandr: cannot find mode on startupDisplay on laptop doesn't work if I connect it to a monitor firstCannot use more than 2 monitors at a timexrandr: Display Desktop on TV
I've got two monitors connected via DisplayPort to the dock. xrandr displays the external monitors as DP1-1 and DP1-2 and the laptop as eDP1.
I set up my monitors with the following in ~/.xprofile:
xrandr --output eDP1 --same-as DP1-1
xrandr --output DP1-2 --right-of DP1-1
This works fine. When disconnecting the laptop from the dock the laptop screen does the right thing, reverting to a single monitor. When reconnecting the laptop DP1-1 shows up, but DP1-2 remains blank. . ~/.xprofile changes nothing, and no error message is printed. I tried reconfiguring using the --crtc option, but all I ended up with were complaints that crtc-1 (or something similar) was not configured correctly. After trying a couple things I got "xrandr: cannot find output 0x46", which I can't find any precedence for.
After reconnecting the monitors have the same names ("DP1-1" and "DP1-2") and both of them are shown as "connected" by xrandr.
arch-linux xrandr laptop dock
add a comment |
I've got two monitors connected via DisplayPort to the dock. xrandr displays the external monitors as DP1-1 and DP1-2 and the laptop as eDP1.
I set up my monitors with the following in ~/.xprofile:
xrandr --output eDP1 --same-as DP1-1
xrandr --output DP1-2 --right-of DP1-1
This works fine. When disconnecting the laptop from the dock the laptop screen does the right thing, reverting to a single monitor. When reconnecting the laptop DP1-1 shows up, but DP1-2 remains blank. . ~/.xprofile changes nothing, and no error message is printed. I tried reconfiguring using the --crtc option, but all I ended up with were complaints that crtc-1 (or something similar) was not configured correctly. After trying a couple things I got "xrandr: cannot find output 0x46", which I can't find any precedence for.
After reconnecting the monitors have the same names ("DP1-1" and "DP1-2") and both of them are shown as "connected" by xrandr.
arch-linux xrandr laptop dock
I may not have direct answers but few pointers which I want you to try. 1. (Mons package)[github.com/Ventto/mons] 2. adding hotplug configuration for monitor. and running xrandr when detected.
– Devidas
Jun 11 '18 at 7:26
you can try github.com/codingtony/udev-monitor-hotplug. I feel this is better way because this way we can always execute when some device plugged in or out. whereas when we do it using ~/.xprofile it will execute only once on start of x-server. I am not claiming it cannot be done that way. just this is more convinient way to write logic(this is just my personal preferance).
– Devidas
Jun 11 '18 at 7:31
Are the monitors named the same after reconnecting them?
– mattia.b89
Jun 12 '18 at 19:52
Ok... you are an experienced user, so I think the more likely it is a: new-hardware+double GPU+USB-C+multi-monitor-setup = kernel/driver bug or missing feature -> try to open a bug report
– mattia.b89
Jun 16 '18 at 8:57
@mattia.b89 After filing probably hundreds of bug reports in open source projects I haven't the faintest idea what or even where to report this issue. Is it a bug in X, the Intel driver,xrandr, or some other component? And in my experience the amount of work involved in writing such a bug report which will be fixed is about the same as learning to program it myself.
– l0b0
Jun 16 '18 at 10:12
add a comment |
I've got two monitors connected via DisplayPort to the dock. xrandr displays the external monitors as DP1-1 and DP1-2 and the laptop as eDP1.
I set up my monitors with the following in ~/.xprofile:
xrandr --output eDP1 --same-as DP1-1
xrandr --output DP1-2 --right-of DP1-1
This works fine. When disconnecting the laptop from the dock the laptop screen does the right thing, reverting to a single monitor. When reconnecting the laptop DP1-1 shows up, but DP1-2 remains blank. . ~/.xprofile changes nothing, and no error message is printed. I tried reconfiguring using the --crtc option, but all I ended up with were complaints that crtc-1 (or something similar) was not configured correctly. After trying a couple things I got "xrandr: cannot find output 0x46", which I can't find any precedence for.
After reconnecting the monitors have the same names ("DP1-1" and "DP1-2") and both of them are shown as "connected" by xrandr.
arch-linux xrandr laptop dock
I've got two monitors connected via DisplayPort to the dock. xrandr displays the external monitors as DP1-1 and DP1-2 and the laptop as eDP1.
I set up my monitors with the following in ~/.xprofile:
xrandr --output eDP1 --same-as DP1-1
xrandr --output DP1-2 --right-of DP1-1
This works fine. When disconnecting the laptop from the dock the laptop screen does the right thing, reverting to a single monitor. When reconnecting the laptop DP1-1 shows up, but DP1-2 remains blank. . ~/.xprofile changes nothing, and no error message is printed. I tried reconfiguring using the --crtc option, but all I ended up with were complaints that crtc-1 (or something similar) was not configured correctly. After trying a couple things I got "xrandr: cannot find output 0x46", which I can't find any precedence for.
After reconnecting the monitors have the same names ("DP1-1" and "DP1-2") and both of them are shown as "connected" by xrandr.
arch-linux xrandr laptop dock
arch-linux xrandr laptop dock
edited Jun 12 '18 at 20:41
l0b0
asked May 9 '18 at 21:54
l0b0l0b0
28.7k19121249
28.7k19121249
I may not have direct answers but few pointers which I want you to try. 1. (Mons package)[github.com/Ventto/mons] 2. adding hotplug configuration for monitor. and running xrandr when detected.
– Devidas
Jun 11 '18 at 7:26
you can try github.com/codingtony/udev-monitor-hotplug. I feel this is better way because this way we can always execute when some device plugged in or out. whereas when we do it using ~/.xprofile it will execute only once on start of x-server. I am not claiming it cannot be done that way. just this is more convinient way to write logic(this is just my personal preferance).
– Devidas
Jun 11 '18 at 7:31
Are the monitors named the same after reconnecting them?
– mattia.b89
Jun 12 '18 at 19:52
Ok... you are an experienced user, so I think the more likely it is a: new-hardware+double GPU+USB-C+multi-monitor-setup = kernel/driver bug or missing feature -> try to open a bug report
– mattia.b89
Jun 16 '18 at 8:57
@mattia.b89 After filing probably hundreds of bug reports in open source projects I haven't the faintest idea what or even where to report this issue. Is it a bug in X, the Intel driver,xrandr, or some other component? And in my experience the amount of work involved in writing such a bug report which will be fixed is about the same as learning to program it myself.
– l0b0
Jun 16 '18 at 10:12
add a comment |
I may not have direct answers but few pointers which I want you to try. 1. (Mons package)[github.com/Ventto/mons] 2. adding hotplug configuration for monitor. and running xrandr when detected.
– Devidas
Jun 11 '18 at 7:26
you can try github.com/codingtony/udev-monitor-hotplug. I feel this is better way because this way we can always execute when some device plugged in or out. whereas when we do it using ~/.xprofile it will execute only once on start of x-server. I am not claiming it cannot be done that way. just this is more convinient way to write logic(this is just my personal preferance).
– Devidas
Jun 11 '18 at 7:31
Are the monitors named the same after reconnecting them?
– mattia.b89
Jun 12 '18 at 19:52
Ok... you are an experienced user, so I think the more likely it is a: new-hardware+double GPU+USB-C+multi-monitor-setup = kernel/driver bug or missing feature -> try to open a bug report
– mattia.b89
Jun 16 '18 at 8:57
@mattia.b89 After filing probably hundreds of bug reports in open source projects I haven't the faintest idea what or even where to report this issue. Is it a bug in X, the Intel driver,xrandr, or some other component? And in my experience the amount of work involved in writing such a bug report which will be fixed is about the same as learning to program it myself.
– l0b0
Jun 16 '18 at 10:12
I may not have direct answers but few pointers which I want you to try. 1. (Mons package)[github.com/Ventto/mons] 2. adding hotplug configuration for monitor. and running xrandr when detected.
– Devidas
Jun 11 '18 at 7:26
I may not have direct answers but few pointers which I want you to try. 1. (Mons package)[github.com/Ventto/mons] 2. adding hotplug configuration for monitor. and running xrandr when detected.
– Devidas
Jun 11 '18 at 7:26
you can try github.com/codingtony/udev-monitor-hotplug. I feel this is better way because this way we can always execute when some device plugged in or out. whereas when we do it using ~/.xprofile it will execute only once on start of x-server. I am not claiming it cannot be done that way. just this is more convinient way to write logic(this is just my personal preferance).
– Devidas
Jun 11 '18 at 7:31
you can try github.com/codingtony/udev-monitor-hotplug. I feel this is better way because this way we can always execute when some device plugged in or out. whereas when we do it using ~/.xprofile it will execute only once on start of x-server. I am not claiming it cannot be done that way. just this is more convinient way to write logic(this is just my personal preferance).
– Devidas
Jun 11 '18 at 7:31
Are the monitors named the same after reconnecting them?
– mattia.b89
Jun 12 '18 at 19:52
Are the monitors named the same after reconnecting them?
– mattia.b89
Jun 12 '18 at 19:52
Ok... you are an experienced user, so I think the more likely it is a: new-hardware+double GPU+USB-C+multi-monitor-setup = kernel/driver bug or missing feature -> try to open a bug report
– mattia.b89
Jun 16 '18 at 8:57
Ok... you are an experienced user, so I think the more likely it is a: new-hardware+double GPU+USB-C+multi-monitor-setup = kernel/driver bug or missing feature -> try to open a bug report
– mattia.b89
Jun 16 '18 at 8:57
@mattia.b89 After filing probably hundreds of bug reports in open source projects I haven't the faintest idea what or even where to report this issue. Is it a bug in X, the Intel driver,
xrandr, or some other component? And in my experience the amount of work involved in writing such a bug report which will be fixed is about the same as learning to program it myself.– l0b0
Jun 16 '18 at 10:12
@mattia.b89 After filing probably hundreds of bug reports in open source projects I haven't the faintest idea what or even where to report this issue. Is it a bug in X, the Intel driver,
xrandr, or some other component? And in my experience the amount of work involved in writing such a bug report which will be fixed is about the same as learning to program it myself.– l0b0
Jun 16 '18 at 10:12
add a comment |
1 Answer
1
active
oldest
votes
In my experience, it sometimes works to issue xrandr --auto after connecting to the dock again. This brings up the external monitor 3 out of 10 times at least.
Also logging out and then in brings the monitor back to life.
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
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',
autoActivateHeartbeat: false,
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%2f442874%2fcant-setup-monitor-after-reconnecting-thinkpad-t570-to-usb-c-dock%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In my experience, it sometimes works to issue xrandr --auto after connecting to the dock again. This brings up the external monitor 3 out of 10 times at least.
Also logging out and then in brings the monitor back to life.
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
In my experience, it sometimes works to issue xrandr --auto after connecting to the dock again. This brings up the external monitor 3 out of 10 times at least.
Also logging out and then in brings the monitor back to life.
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
In my experience, it sometimes works to issue xrandr --auto after connecting to the dock again. This brings up the external monitor 3 out of 10 times at least.
Also logging out and then in brings the monitor back to life.
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
In my experience, it sometimes works to issue xrandr --auto after connecting to the dock again. This brings up the external monitor 3 out of 10 times at least.
Also logging out and then in brings the monitor back to life.
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 2 days ago
sebasth
8,64432450
8,64432450
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
Marcin BąkMarcin Bąk
1
1
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Marcin Bąk is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
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.
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%2f442874%2fcant-setup-monitor-after-reconnecting-thinkpad-t570-to-usb-c-dock%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
I may not have direct answers but few pointers which I want you to try. 1. (Mons package)[github.com/Ventto/mons] 2. adding hotplug configuration for monitor. and running xrandr when detected.
– Devidas
Jun 11 '18 at 7:26
you can try github.com/codingtony/udev-monitor-hotplug. I feel this is better way because this way we can always execute when some device plugged in or out. whereas when we do it using ~/.xprofile it will execute only once on start of x-server. I am not claiming it cannot be done that way. just this is more convinient way to write logic(this is just my personal preferance).
– Devidas
Jun 11 '18 at 7:31
Are the monitors named the same after reconnecting them?
– mattia.b89
Jun 12 '18 at 19:52
Ok... you are an experienced user, so I think the more likely it is a: new-hardware+double GPU+USB-C+multi-monitor-setup = kernel/driver bug or missing feature -> try to open a bug report
– mattia.b89
Jun 16 '18 at 8:57
@mattia.b89 After filing probably hundreds of bug reports in open source projects I haven't the faintest idea what or even where to report this issue. Is it a bug in X, the Intel driver,
xrandr, or some other component? And in my experience the amount of work involved in writing such a bug report which will be fixed is about the same as learning to program it myself.– l0b0
Jun 16 '18 at 10:12