You are not logged in.
Pages: 1
Hello fellow Arch users.
I have an issue on my desktop PC, which is running Arch. When I suspend, then resume, the second monitor blacks out. Running this:
xset edpms force standbywill bring it to life again, however only briefly. Any support is appreciated.
.xinitrc:
xrandr --output VGA-0 --off ---output DVI-0 --mode 1680x1050 --pos 1920x0 --rotate normal --output HDMI-0 --mode 1920x1080 --pos 0x0 --rotate normal
setterm -blank 0 -powersave off -powerdown 0
xset s of
exec awesome dbus-launchEDIT: This also happens after a normal boot.
Last edited by anonkun (2014-05-19 11:00:24)
Offline
How about some logs after resume?
dmesg | tail -100
journalctl -b -n 60 --no-pager -x
tail -100 /var/log/Xorg.*.logAnd anything else that may be helpful, like some information on your system.
Offline
Hello, thank you for replying. Here are the outputs for the commands you listed.
dmesg | tail -100:
[[ 317.388499] PM: Syncing filesystems ... done.
[ 317.611252] PM: Preparing system for mem sleep
[ 317.966051] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 317.967247] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
[ 317.968047] PM: Entering mem sleep
[ 317.968078] Suspending console(s) (use no_console_suspend to debug)
[ 317.968172] sd 6:0:0:0: [sdf] Synchronizing SCSI cache
[ 317.968304] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 317.968459] sd 0:0:0:0: [sda] Stopping disk
[ 318.445063] PM: suspend of devices complete after 476.687 msecs
[ 318.445241] PM: late suspend of devices complete after 0.176 msecs
[ 318.445509] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
[ 318.471703] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 318.485139] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 318.511702] PM: noirq suspend of devices complete after 66.426 msecs
[ 318.512288] ACPI: Preparing to enter system sleep state S3
[ 318.513073] PM: Saving platform NVS memory
[ 318.513660] Disabling non-boot CPUs ...
[ 318.515086] kvm: disabling virtualization on CPU1
[ 318.515698] smpboot: CPU 1 is now offline
[ 318.517389] kvm: disabling virtualization on CPU2
[ 318.618337] smpboot: CPU 2 is now offline
[ 318.620036] kvm: disabling virtualization on CPU3
[ 318.721721] smpboot: CPU 3 is now offline
[ 318.723358] kvm: disabling virtualization on CPU4
[ 318.825102] smpboot: CPU 4 is now offline
[ 318.826688] kvm: disabling virtualization on CPU5
[ 318.928483] smpboot: CPU 5 is now offline
[ 318.930058] kvm: disabling virtualization on CPU6
[ 319.031864] smpboot: CPU 6 is now offline
[ 319.033443] kvm: disabling virtualization on CPU7
[ 319.135243] smpboot: CPU 7 is now offline
[ 319.136861] ACPI: Low-level resume complete
[ 319.136893] PM: Restoring platform NVS memory
[ 319.137303] Enabling non-boot CPUs ...
[ 319.137337] x86: Booting SMP configuration:
[ 319.137337] smpboot: Booting Node 0 Processor 1 APIC 0x2
[ 319.148399] kvm: enabling virtualization on CPU1
[ 319.150573] Intel pstate controlling: cpu 1
[ 319.150611] CPU1 is up
[ 319.150624] smpboot: Booting Node 0 Processor 2 APIC 0x4
[ 319.161784] kvm: enabling virtualization on CPU2
[ 319.163952] Intel pstate controlling: cpu 2
[ 319.163994] CPU2 is up
[ 319.164008] smpboot: Booting Node 0 Processor 3 APIC 0x6
[ 319.175168] kvm: enabling virtualization on CPU3
[ 319.177337] Intel pstate controlling: cpu 3
[ 319.177379] CPU3 is up
[ 319.177393] smpboot: Booting Node 0 Processor 4 APIC 0x1
[ 319.188556] kvm: enabling virtualization on CPU4
[ 319.190747] Intel pstate controlling: cpu 4
[ 319.190792] CPU4 is up
[ 319.190806] smpboot: Booting Node 0 Processor 5 APIC 0x3
[ 319.201963] kvm: enabling virtualization on CPU5
[ 319.204163] Intel pstate controlling: cpu 5
[ 319.204198] CPU5 is up
[ 319.204212] smpboot: Booting Node 0 Processor 6 APIC 0x5
[ 319.215369] kvm: enabling virtualization on CPU6
[ 319.217582] Intel pstate controlling: cpu 6
[ 319.217616] CPU6 is up
[ 319.217630] smpboot: Booting Node 0 Processor 7 APIC 0x7
[ 319.228788] kvm: enabling virtualization on CPU7
[ 319.231004] Intel pstate controlling: cpu 7
[ 319.231039] CPU7 is up
[ 319.237328] ACPI: Waking up from system sleep state S3
[ 319.263695] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
[ 319.290361] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 319.357205] PM: noirq resume of devices complete after 119.357 msecs
[ 319.357360] PM: early resume of devices complete after 0.125 msecs
[ 319.357431] mei_me 0000:00:16.0: irq 44 for MSI/MSI-X
[ 319.357504] pcieport 0000:00:1c.3: System wakeup disabled by ACPI
[ 319.357827] snd_hda_intel 0000:01:00.1: irq 45 for MSI/MSI-X
[ 319.359864] tg3 0000:03:00.0 enp3s0: Link is down
[ 319.361593] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[ 319.363880] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[ 319.367274] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
[ 319.367428] radeon 0000:01:00.0: WB enabled
[ 319.367431] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88021d0bec00
[ 319.367433] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88021d0bec0c
[ 319.368880] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900142b2118
[ 319.385392] [drm] ring test on 0 succeeded in 2 usecs
[ 319.385456] [drm] ring test on 3 succeeded in 1 usecs
[ 319.560596] usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
[ 319.572690] [drm] ring test on 5 succeeded in 2 usecs
[ 319.572696] [drm] UVD initialized successfully.
[ 319.572767] [drm] ib test on ring 0 succeeded in 0 usecs
[ 319.572841] [drm] ib test on ring 3 succeeded in 1 usecs
[ 319.690502] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 319.703837] ata4: SATA link down (SStatus 0 SControl 300)
[ 319.710509] ata3: SATA link down (SStatus 0 SControl 300)
[ 319.717172] ata5: SATA link down (SStatus 0 SControl 300)
[ 319.717353] ata2.00: configured for UDMA/100
[ 319.725217] [drm] ib test on ring 5 succeeded
[ 324.719516] ata1: link is slow to respond, please be patient (ready=0)
[ 325.733324] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 325.737567] ata1.00: configured for UDMA/133
[ 325.737681] sd 0:0:0:0: [sda] Starting disk
[ 325.752608] PM: resume of devices complete after 6392.296 msecs
[ 325.765637] PM: Finishing wakeup.
[ 325.765640] Restarting tasks ... done.journalctl -b -n 60 --no-pager -x:
May 22 18:56:07 arch systemd[1]: Starting Sleep.
-- Subject: Unit sleep.target has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has begun starting up.
May 22 18:56:07 arch systemd[1]: Reached target Sleep.
-- Subject: Unit sleep.target has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has finished starting up.
--
-- The start-up result is done.
May 22 18:56:07 arch systemd[1]: Starting Suspend...
-- Subject: Unit systemd-suspend.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit systemd-suspend.service has begun starting up.
May 22 18:56:07 arch systemd-sleep[1806]: Suspending system...
-- Subject: System sleep state suspend entered
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The system has now entered the suspend sleep state.
May 22 18:56:07 arch kernel: PM: Syncing filesystems ... done.
May 22 18:56:07 arch kernel: PM: Preparing system for mem sleep
May 22 18:56:19 arch kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
May 22 18:56:19 arch kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
May 22 18:56:19 arch kernel: PM: Entering mem sleep
May 22 18:56:19 arch kernel: Suspending console(s) (use no_console_suspend to debug)
May 22 18:56:19 arch kernel: sd 6:0:0:0: [sdf] Synchronizing SCSI cache
May 22 18:56:19 arch kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
May 22 18:56:19 arch kernel: sd 0:0:0:0: [sda] Stopping disk
May 22 18:56:19 arch kernel: PM: suspend of devices complete after 476.687 msecs
May 22 18:56:19 arch kernel: PM: late suspend of devices complete after 0.176 msecs
May 22 18:56:19 arch kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI
May 22 18:56:19 arch kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
May 22 18:56:19 arch kernel: ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
May 22 18:56:19 arch kernel: PM: noirq suspend of devices complete after 66.426 msecs
May 22 18:56:19 arch kernel: ACPI: Preparing to enter system sleep state S3
May 22 18:56:19 arch kernel: PM: Saving platform NVS memory
May 22 18:56:19 arch kernel: Disabling non-boot CPUs ...
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU1
May 22 18:56:19 arch kernel: smpboot: CPU 1 is now offline
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU2
May 22 18:56:19 arch kernel: smpboot: CPU 2 is now offline
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU3
May 22 18:56:19 arch kernel: smpboot: CPU 3 is now offline
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU4
May 22 18:56:19 arch kernel: smpboot: CPU 4 is now offline
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU5
May 22 18:56:19 arch kernel: smpboot: CPU 5 is now offline
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU6
May 22 18:56:19 arch kernel: smpboot: CPU 6 is now offline
May 22 18:56:19 arch kernel: kvm: disabling virtualization on CPU7
May 22 18:56:19 arch kernel: smpboot: CPU 7 is now offline
May 22 18:56:19 arch kernel: ACPI: Low-level resume complete
May 22 18:56:19 arch kernel: PM: Restoring platform NVS memory
May 22 18:56:19 arch kernel: Enabling non-boot CPUs ...
May 22 18:56:19 arch kernel: x86: Booting SMP configuration:
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU1
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 1
May 22 18:56:19 arch kernel: CPU1 is up
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU2
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 2
May 22 18:56:19 arch kernel: CPU2 is up
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU3
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 3
May 22 18:56:19 arch kernel: CPU3 is up
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU4
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 4
May 22 18:56:19 arch kernel: CPU4 is up
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU5
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 5
May 22 18:56:19 arch kernel: CPU5 is up
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU6
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 6
May 22 18:56:19 arch kernel: CPU6 is up
May 22 18:56:19 arch kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
May 22 18:56:19 arch kernel: kvm: enabling virtualization on CPU7
May 22 18:56:19 arch kernel: Intel pstate controlling: cpu 7
May 22 18:56:19 arch kernel: CPU7 is up
May 22 18:56:19 arch kernel: ACPI: Waking up from system sleep state S3
May 22 18:56:19 arch kernel: ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
May 22 18:56:19 arch kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
May 22 18:56:19 arch kernel: PM: noirq resume of devices complete after 119.357 msecs
May 22 18:56:19 arch kernel: PM: early resume of devices complete after 0.125 msecs
May 22 18:56:19 arch kernel: mei_me 0000:00:16.0: irq 44 for MSI/MSI-X
May 22 18:56:19 arch kernel: pcieport 0000:00:1c.3: System wakeup disabled by ACPI
May 22 18:56:19 arch kernel: snd_hda_intel 0000:01:00.1: irq 45 for MSI/MSI-X
May 22 18:56:19 arch kernel: tg3 0000:03:00.0 enp3s0: Link is down
May 22 18:56:19 arch kernel: [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
May 22 18:56:19 arch kernel: snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
May 22 18:56:19 arch kernel: [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
May 22 18:56:19 arch kernel: radeon 0000:01:00.0: WB enabled
May 22 18:56:19 arch kernel: radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88021d0bec00
May 22 18:56:19 arch kernel: radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88021d0bec0c
May 22 18:56:19 arch kernel: radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc900142b2118
May 22 18:56:19 arch kernel: [drm] ring test on 0 succeeded in 2 usecs
May 22 18:56:19 arch kernel: [drm] ring test on 3 succeeded in 1 usecs
May 22 18:56:19 arch kernel: usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
May 22 18:56:19 arch kernel: [drm] ring test on 5 succeeded in 2 usecs
May 22 18:56:19 arch kernel: [drm] UVD initialized successfully.
May 22 18:56:19 arch kernel: [drm] ib test on ring 0 succeeded in 0 usecs
May 22 18:56:19 arch kernel: [drm] ib test on ring 3 succeeded in 1 usecs
May 22 18:56:19 arch kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 22 18:56:19 arch kernel: ata4: SATA link down (SStatus 0 SControl 300)
May 22 18:56:19 arch kernel: ata3: SATA link down (SStatus 0 SControl 300)
May 22 18:56:19 arch kernel: ata5: SATA link down (SStatus 0 SControl 300)
May 22 18:56:19 arch kernel: ata2.00: configured for UDMA/100
May 22 18:56:19 arch kernel: [drm] ib test on ring 5 succeeded
May 22 18:56:19 arch kernel: ata1: link is slow to respond, please be patient (ready=0)
May 22 18:56:19 arch kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 22 18:56:19 arch kernel: ata1.00: configured for UDMA/133
May 22 18:56:19 arch kernel: sd 0:0:0:0: [sda] Starting disk
May 22 18:56:19 arch kernel: PM: resume of devices complete after 6392.296 msecs
May 22 18:56:19 arch kernel: PM: Finishing wakeup.
May 22 18:56:19 arch kernel: Restarting tasks ... done.
May 22 18:56:19 arch systemd[1]: Time has been changedscreenfetch -n (I ommitted some stuff):
OS: Arch Linux
Kernel: x86_64 Linux 3.14.4-1-ARCH
Uptime: 8h 38m
Packages: 691
Shell: bash 4.3.11
Resolution: 3600x1080
WM: Awesome
CPU: Intel Core i7-2600 CPU @ 3.8GHz
GPU: AMD/ATI Turks XT [Radeon HD 6670/7670]
RAM: 685MB / 7971MB/etc/X11/xorg.conf.d/10-monitor.conf:
Section "Monitor"
Identifier "HDMI-0"
Option "DPMS" "false"
EndSection
Section "Monitor"
Identifier "DVI-0"
Option "DPMS" "false"
EndSection
Section "ServerLayout"
Identifier "ServerLayout0"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSectionxset -q
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,built-ins
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
DPMS is Disabled~/.xinitrc:
xrandr --output VGA-0 --off --output DVI-0 --mode 1680x1050 --pos 1920x0 --rotate normal --output HDMI-0 --mode 1920x1080 --pos 0x0 --rotate normal
exec awesome dbus-launchLast edited by anonkun (2014-05-22 11:08:23)
Offline
My bad, I should have written the point of using tail, namely to cut out the previous part of the logs, since then they can be very large and therefore troublesome to read. Use whatever you want to give logs after resuming about the sleeping and resuming process. This goes also for Xorg.0.log and Xorg.1.log (tail apparently does not process given files separately, so it does not work in the form I suggested). Instead of posting them once more, please edit your previous post.
Edit: Or just post the whole thing.
Last edited by emeres (2014-05-20 10:22:58)
Offline
My bad, I should have written the point of using tail, namely to cut out the previous part of the logs, since then they can be very large and therefore troublesome to read. Use whatever you want to give logs after resuming about the sleeping and resuming process. This goes also for Xorg.0.log and Xorg.1.log (tail apparently does not process given files separately, so it does not work in the form I suggested). Instead of posting them once more, please edit your previous post.
Edit: Or just post the whole thing.
Is that okay or should I post Xorg.0.log and Xorg.1.log seperately?
Offline
Is that okay or should I post Xorg.0.log and Xorg.1.log seperately?
Is what okay? You did not post or edit anything. Preferably separately.
Does the same happen when you turn the display off [using xrandr for example], before putting your pc to sleep? Obviously you would have to turn it on afterwards, but does it stay on then? What does xset say about your second monitor before sleeping and after resume?
By the way you miss one "f" in your xinitrc by xset command.
Offline
anonkun wrote:Is that okay or should I post Xorg.0.log and Xorg.1.log seperately?
Is what okay? You did not post or edit anything. Preferably separately.
Does the same happen when you turn the display off [using xrandr for example], before putting your pc to sleep? Obviously you would have to turn it on afterwards, but does it stay on then? What does xset say about your second monitor before sleeping and after resume?By the way you miss one "f" in your xinitrc by xset command.
Hello again,
I fixed up the errors and tried to include more data. I removed the xorg logs because nothing in there was relevant to the sleep and wakeup. Also, in my WM config, I have not touched the xset or other xorg commands.
Last edited by anonkun (2014-05-22 11:08:57)
Offline
Is the second monitor powered on the whole time (during sleep and wake-up) or do you turn it on after waking up? Does it use HDMI-0 output? It could be a handshake issue. You could try temporary setting a different resolution, turning it off/on, changing dmps and then reverting it. You would have to post xset -q for both monitors, I assume this was for the primary one.
Since you are using two screens on one X server display from what I gathered, you should could be using DISPLAY environment variable when running xrandr or setting it through xrandr directly.
env DISPLAY=:0.1 xrandr --output HDMI-0 --off; env DISPLAY=:0.1 xrandr --output HDMI-0 --auto;
env DISPLAY=:0.1 xset -qEdit: I read too fast yet again. You have one screen, no server layout in the the server layout section in xorg.conf.d/10-monitors.conf, so xrandr is creating one.
Last edited by emeres (2014-05-22 21:05:26)
Offline
Is the second monitor powered on the whole time (during sleep and wake-up) or do you turn it on after waking up? Does it use HDMI-0 output? It could be a handshake issue. You could try temporary setting a different resolution, turning it off/on, changing dmps and then reverting it. You would have to post xset -q for both monitors, I assume this was for the primary one.
Since you are using two screens on one X server display from what I gathered, you should be using DISPLAY environment variable when running xrandr or setting it through xrandr directly.env DISPLAY=:0.1 xrandr --output HDMI-0 --off; env DISPLAY=:0.1 xrandr --output HDMI-0 --auto; env DISPLAY=:0.1 xset -q
Hello again, my main monitor is the HDMI one; and they both have power.
env DISPLAY=:0 xset qWorks, however
env DISPLAY=:0.1 xset qdoes not.
Also;
env DISPLAY=:0.0 xrandr --output DVI-0 --off; env DISPLAY=:0.0 xrandr --output DVI-0 --autocasues the monitor to light up for a few seconds then go black again. It mirrors my first monitor as well.
Last edited by anonkun (2014-05-22 17:55:27)
Offline
I corrected my previous post. Well I have a different setup, two screens on one DISPLAY (:0.0 and :0.1) and I could not force them to turn off, since the second one was blocking it, which caused some problems with suspending also. I had to turn dpms off and then on again, to be able to turn the monitors off (suspend them) with "xset dpms force off".
I do not want to force you to use the same thing, however you could try creating two different screens by changing xorg.conf[.d] to something like this:
Section "ServerLayout"
Identifier "ServerLayout0"
Screen 0 "Screen-0" 0 0
Screen 1 "Screen-1" 1920 0
#or Screen 1 "Screen-1" RightOf "Screen0"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSectionMaybe if you set them up as different screens the second one will get turned on back again after resuming from sleep. You would need to add two screens and two devices (at least in my case using fglrx driver) binding those screens to the two monitors respectively. If you want to try this, read more in the manual:
man xorg.confAlso check out the wiki.
Try turning the second monitor on after resuming or during like I previously suggested. Other than that, I am out of ideas for now.
Offline
Snip
Last edited by anonkun (2014-05-24 05:08:54)
Offline
I have the same problem, but in my case it's a VGA and a DVI monitor, the DVI monitor stops working after suspend. It worked correctly previously, I'll try restoring to identify what changed triggered it.
Offline
Same here, happened after a pacman update. I'm using a Nvidia Geforce 540M with Nouveau driver, so it can't be the graphics card (OP has a ATI GPU).
xrandr:
Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm
1366x768 60.10*+
1024x768 59.92
800x600 59.86
640x480 59.38
720x400 59.55
640x400 59.95
640x350 59.77
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected 1920x1080+1366+0 (normal left inverted right x axis y axis) 531mm x 298mm
1920x1080 60.00*+
1280x1024 60.02
1440x900 59.90
1280x800 59.91
1152x864 75.00
1024x768 70.07 60.00
800x600 60.32 56.25
640x480 66.67 60.00
720x400 70.08
DP-1 disconnected (normal left inverted right x axis y axis)My guess is it's kernel related
Offline
Bump for update. I have also the same problem. It used to work fine but it is broken after update. Any luck resolving it?
Offline
It's definetly a kernel problem: when I downgrade to 3.14 the issue is gone.
So, the bug appeared between kernel version 3.14.4 and 3.16.2. And it's still in 3.16.4.
Last edited by wgnm (2014-10-15 21:26:13)
Offline
Same issue occurs 3 years on.
GPU : GTX 670
DE : GNOME 3.28 (but also happens with GNOME 3.26)
Xorg : 1.19.6
NVIDIA driver : 390.42
Kernel : 4.15.12
Display 1 connected via DP with res 2560x1440
Display 2 connected via HDMI with res 2560x1440
After locking screen and both monitors going into powersave mode, when resuming, only primary display is able to resume properly. Secondary display stays off.
Only recoverable by switching tty (Alt + F7 and back to Alt + F2).
Reported to NVIDIA but i figured i'd let you guys know. Since it's also happening on Intel drivers, i'm going to assume that it's a bug in Xorg.
Last edited by Cxpher (2018-03-26 08:58:21)
Offline
Pages: 1