Score:0

The monitor doesn't want to wake up after sleep

us flag

I have a couple of issues with the waking up monitor from sleep and after a restart.

When I wake up the computer from sleep, the monitor does not want to turn on at all. Everything else works fine (i can hear music in the background for example). 2nd issue is when I do restart, sometimes I just get a message on my monitor "No signal".

Configuration:

Resolution: 1920x1080 (two monitor setup, but just one is turn on most of the time)
DE: GNOME 40.5 
CPU: AMD Ryzen 7 2700 
GPU: AMD ATI Radeon  5700
Memory: 16GB

lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 21.10
Release:    21.10
Codename:   impish

cat /sys/power/mem_sleep

s2idle [deep]

uname -r

5.13.0-21-generic

sudo dmesg | grep -i amdgpu

[    1.065293] [drm] amdgpu kernel modesetting enabled.
[    1.065344] amdgpu: Ignoring ACPI CRAT on non-APU system
[    1.065347] amdgpu: Virtual CRAT table created for CPU
[    1.065355] amdgpu: Topology: Add CPU node
[    1.065425] fb0: switching to amdgpudrmfb from EFI VGA
[    1.065467] amdgpu 0000:28:00.0: vgaarb: deactivate vga console
[    1.065564] amdgpu 0000:28:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[    1.066683] amdgpu 0000:28:00.0: No more image in the PCI ROM
[    1.066711] amdgpu 0000:28:00.0: amdgpu: Fetched VBIOS from ROM BAR
[    1.066713] amdgpu: ATOM BIOS: 113-3E4112U-O47
[    1.066760] amdgpu 0000:28:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used)
[    1.066764] amdgpu 0000:28:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF
[    1.066766] amdgpu 0000:28:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF
[    1.066819] [drm] amdgpu: 8176M of VRAM memory ready
[    1.066822] [drm] amdgpu: 8176M of GTT memory ready.
[    1.280923] amdgpu 0000:28:00.0: amdgpu: RAS: optional ras ta ucode is not available
[    1.285167] amdgpu 0000:28:00.0: amdgpu: RAP: optional rap ta ucode is not available
[    1.285168] amdgpu 0000:28:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[    1.285236] amdgpu 0000:28:00.0: amdgpu: use vbios provided pptable
[    1.285237] amdgpu 0000:28:00.0: amdgpu: smc_dpm_info table revision(format.content): 4.5
[    1.331340] amdgpu 0000:28:00.0: amdgpu: SMU is initialized successfully!
[    1.833253] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[    1.833386] amdgpu: Virtual CRAT table created for GPU
[    1.833465] amdgpu: Topology: Add dGPU node [0x731f:0x1002]
[    1.833467] kfd kfd: amdgpu: added device 1002:731f
[    1.833469] amdgpu 0000:28:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 10, active_cu_number 36
[    1.839374] fbcon: amdgpudrmfb (fb0) is primary device
[    1.839378] amdgpu 0000:28:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[    1.862927] amdgpu 0000:28:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[    1.862929] amdgpu 0000:28:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[    1.862930] amdgpu 0000:28:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[    1.862931] amdgpu 0000:28:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[    1.862932] amdgpu 0000:28:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[    1.862933] amdgpu 0000:28:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[    1.862934] amdgpu 0000:28:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[    1.862935] amdgpu 0000:28:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[    1.862936] amdgpu 0000:28:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[    1.862937] amdgpu 0000:28:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[    1.862938] amdgpu 0000:28:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[    1.862939] amdgpu 0000:28:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[    1.862940] amdgpu 0000:28:00.0: amdgpu: ring vcn_dec uses VM inv eng 0 on hub 1
[    1.862941] amdgpu 0000:28:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 1 on hub 1
[    1.862942] amdgpu 0000:28:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 4 on hub 1
[    1.862943] amdgpu 0000:28:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1
[    1.864065] amdgpu 0000:28:00.0: amdgpu: Using BACO for runtime pm
[    1.864394] [drm] Initialized amdgpu 3.41.0 20150101 for 0000:28:00.0 on minor 0
[   10.336677] snd_hda_intel 0000:28:00.1: bound 0000:28:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

Note:

I try the same sleep thing on this distros:

PopOS (20.10, 21.04, 21.10 (beta, kernel 5.13, 5.15)), Ubuntu 20.04, Manjaro 21.1.6 (kernel 5.13, 5.14, 5.15), Linux Mint 20.2.

Update: Now I'm trying to test OS behavior while both monitors are on. The situation is the same during the sleep period (they don't want to turn on), but when I hard restart my PC, after that I get a lot of weird issues. Sometimes the primary monitor does not want to turn on at all or it just gives a half-image.

ChanganAuto avatar
us flag
Even brand system do need UEFI update. Do that before anything else. If the problem persists then we troubleshoot from there.
NoobyAFK avatar
us flag
I just did that, still the same.
user10489 avatar
in flag
Try running `xrandr` which will probe and sometimes reset the video mode. You can also try `xset dpms force off; xset dpms force on` to power cycle the video output. Those will help if the video card is confused about mode settings or sleep state. But it sounds like you might have a more serious problem.
bd flag
I have exactly the same issue in Ubuntu 21.10 on Lenovo Legion 7i Gen6. Only way to fix it is to disconnect hdmi cable, wait a minute and connect it back. kernel: 5.13.0-22-generic
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.