37

My current setup is my Dell XPS 9560 (1080p) with 2x 1440p 75hz monitors. Everything works fine on first boot: I turn on the laptop, type in my password, shut the lid and just use the two external monitors.

However, if I put the computer to sleep and then try and wake it up again, only one of the two external monitors comes on. Sometimes both of them do but that only seems to happen around 1/10 times.

The monitor appears to wake up (it turns on) but it flicks between the sources and reports "no signal".

I have the laptop running on the integrated Intel graphics but the same thing appears to happen on the Nvidia graphics as well.

The easiest way to get the monitor back on is just to restart the entire machine and 99% of the time it comes back on. Either that or if I fiddle around with settings long enough and re-plug the HDMI cable a few times it sometimes comes back on.

I am running Ubuntu 18.04 LTS on the machine and this is the only problem I have had so far!

EDIT: The current workaround I am using to get the monitor to come back on is to change the refresh rate from 74.99hz to 59.95hz and then back again. This pretty consistently works but obviously isn't an ideal solution.

2
  • it also seems to depend on what key you press and the login window side. for example if you press space the "other" monitor will work but not the login.
    – Asher
    May 11, 2022 at 21:27
  • Was hoping for a fix, but the workaround I've been using is, on the screen that DOES start, right click and go to display settings. Change the monitor arrangement, by dragging that screen up a hair, commit, then the other monitor comes on, and revert. Apr 2, 2023 at 16:02

6 Answers 6

22

You don't need to reboot your computer to fix it. A better way to deal with it is using xrandr, which is the tool to manage the output of your displays.

First, run simply xrandr to get a list of all displays currently connected and their respective names (their connection). In possession of that information, you can run a simple command to 'reactivate' the secondary display and place it in the correct location. It would be something like:

xrandr --output SECONDARYDISPLAY --auto --right-of PRIMARYDISPLAY

You want to replace both the displays with the actual name you got from your xrandr. It is usually things like HDMI-A-0, DisplayPort-0, DVI-D-0, etc... If you connect the display to the left side of your main display, you also want to change the --right-of. Xrandr has many other options you might want to use, like setting offset, refresh rate, etc. For more, take a look at the man page.

In your case, since you are using two external displays, you might also want to set the primary display with xrandr, in case running simply the first command doesn't work. You can then combine both with something like:

xrandr --output PRIMARYDISPLAY --auto --primary && xrandr --output SECONDARYDISPLAY --auto --right-of PRIMARYDISPLAY

If you are satisfied with the results of the commands, you might want to add them to a shortcut, if you feel that is faster than running them from the command line. You might also want to add them to a script that is run on resume and placing it over at /usr/lib/pm-utils/sleep.d/.

Keep in mind that this issue might go away of it's own in the future. There are plenty of reports of similar issues, but the underlying cases can be very different. If you believe your case is very persistent, you could try opening a bug report. I personally used to have this problem a couple months ago, but it 'fixed itself', and I haven't had it ever since. I found that using: ctrl+alt+t (open terminal) typing 'xr' followed by 'UP' and 'ENTER' (this way my terminal would connect to the last used command that started with xr) was a good solution for me, specially because I also turn my secondary display off with xrandr from time to time.

1
  • 2
    This solution is not working for me (20.04 LTS, Kernel 5.8.0 36 (HDE)). For what it's worth - the monitor didn't wake up, but the display seems to be recognized correctly as I can move the mouse into the black area.
    – Jan Groth
    Jan 9, 2021 at 20:08
7

The given answer posted by Podesta did not work for me on first try.

I remembered a weird monitor quirk, tried it and it worked.

If the xrand command did not help, try unplugging the monitor for a while.

In my case the "sleep" led stays on a couple of seconds after loosing power. Just re-plug your monitor when it has fully lost power.

After that I ran the xrand command and my monitor came back to life :)

5
  • Wasted hours trying to solve this. This is the only solution that worked for me. :-) +1
    – dww
    Mar 9, 2021 at 15:17
  • 1
    unplugging and replugging both of my monitors every time I want to log into my Linux box is extremely not good. It's the only way I can log in anymore. Jun 9, 2021 at 5:37
  • 2
    What works for me on my work computer is CTRL+ALT+F3 to get to a text terminal, wait a few seconds, and go back to the graphical terminal by doing CTRL+ALT+F2. Alternatively locking the screen and unlocking it using SUPER+L, but that's annoying since I have to type a password then. Oct 18, 2021 at 13:41
  • @AtillaFiliz Good find, that's a way less annoying fix than unplugging the monitor. Wanna post it as an answer?
    – otterstorm
    Dec 10, 2021 at 15:11
  • @otterstorm another workaround is the command xset dpms force off which forces turning off all the monitors. then pressing any key turns them back on. Jan 12, 2022 at 7:47
6

I have another Dell which has a similar issue on Ubuntu 20.04. The most convenient workarounds I found were either:

  • running xset dpms force off
  • Switching to TTY3 and back to TTY2.

EDIT: I installed kubuntu-desktop and started running Plasma. In addition, instead of the regular HDMI port, I began using a USB-C to HDMI adapter. I don't have the issue anymore.

3
  • 1
    Switching to TTY3 and back to TTY2 worked for me Mar 11, 2022 at 6:01
  • Running xset dpms force off woked for me!
    – gmelodie
    May 9, 2022 at 21:14
  • does it persist after reboot?
    – birgersp
    Mar 13, 2023 at 11:41
0

I had the same issue.

When the second monitor was connected with a HDMI-DVI cable, I was able to work around the problem by doing these things:

  • Suspend, wait for a few seconds and wake up.
  • Shutdown and start.

It didn't work to log out and back in, restart from the menu option, or unplug the second monitor and wait until it consumes the power completely.

Finally I switched to using a VGA-VGA cable and everything works properly.

0

I am having the same issue with this Laptop on Fedora 36. It helped me to disable the power management daemon that comes with the NVIDIA driver:

systemctl disable nvidia-powerd

I noticed that this service produced errors in the kernel log and did not run properly anyway. You can check the status of the service with this command:

systemctl status nvidia-powerd

After disabling the service the monitor wakeup issues were gone. I am not sure if that is a fix for Ubuntu as I am running Fedora with Wayland. It might be worth a try.

0

My os is Ubuntu 22.04 with nvidia installed 535 My second screen is ViewSonic, when I turnoff screen and turn on again, the signal has been recovered. Maybe error from screen instead of Laptop (dell precision 5510)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .