4

My problem is quite strange I couldn't find a source of the issue so I will just try to explain problem manifestation and hopefully someone will have an idea how to solve it (or just how can I start tracking the issue).

I have Thinkpad t460p and docking station ThinkPad Ultra Dock. I am running Ubuntu 16.04, kernel 4.4.0 with i3wm. When I plug laptop to docking station everything works fine I can set monitors as I like (using xrandr) and also suspend and wake laptop from sleep (while docked). Problem: if I undock laptop, it is then impossible to wake it up from sleep. Pressing power button turns the laptop on, but screen is always blank and it doesn't react to any inputs. Only way around it (as far as I can see) is to force reboot the laptop. Interesting thing is that undocking laptop while it is not suspended works until it gets suspended and after it encounters same issue. If the laptop was undocked while suspended it will also encounter same issue.

My question is, how can I address this problem, where can I find more information about what could be wrong, logs or any other hints what could be a problem.

One more observation: If i don't setup external monitor with xrandr unplugging laptop while awake works, as I can later wake it up from sleep, but in case of undocking it while encounter same issue.

Thanks

  • Try this. If not installed, install pm-utils. Then run sudo pm-suspend to put the laptop to sleep while docked. Do like you usually do and undock it, then try to open it. Report back if that works for you. – Dorian Mar 17 '17 at 18:10
  • Nope, same issue again. Just black screen after waking up and no reaction to any input. – Milan Mar 17 '17 at 18:40
  • Sounds like you will have to start looking into log files. If you have another system to SSH into it, perhaps you can view the dmesg output from it. Not sure if it will work, but you could also try dmesg -w > ~/file.txt and then repeat the issue. After rebooting, read the file.txt to see what errors pop up. – Dorian Mar 17 '17 at 18:46
  • 1
    Seems there are multiple bug reports on this already with displayport/hdmi/multiple monitors. It was supposed to be fixed in kernel 4.4.0-24.43. Can you confirm what exact kernel you're running with uname -a? – Dorian Mar 17 '17 at 19:48
  • 1
    Did this issue get resolved in chat? Same here. – BartBog Nov 16 '17 at 8:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.