Display becomes inactive on primary display after wake from suspend

[unkemptArc99]

I have a Lenovo Legion 5 15ACH6 laptop with Linux Mint 20.3 Una dual boot with Windows. Here are my system specs -

Code: Select all

❯ inxi -Fxxxz
System:
  Kernel: 5.13.0-25-generic x86_64 bits: 64 compiler: N/A 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: LENOVO product: 82JW v: Legion 5 15ACH6 
  serial: <filter> Chassis: type: 10 v: Legion 5 15ACH6 serial: <filter> 
  Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN serial: <filter> 
  UEFI: LENOVO v: HHCN11WW date: 05/13/2021 
Battery:
  ID-1: BAT0 charge: 62.0 Wh condition: 62.0/60.0 Wh (103%) volts: 17.2/15.4 
  model: Celxpert L20C4PC0 type: Li-poly serial: <filter> status: Charging 
  cycles: 7 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 5800H with Radeon Graphics bits: 64 
  type: MT MCP arch: Zen 3 L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 102206 
  Speed: 1297 MHz min/max: 1200/3200 MHz boost: enabled Core speeds (MHz): 
  1: 1391 2: 1297 3: 1297 4: 1297 5: 1285 6: 1296 7: 1271 8: 1156 9: 1240 
  10: 1135 11: 1135 12: 1134 13: 1259 14: 1428 15: 2527 16: 1173 
Graphics:
  Device-1: NVIDIA vendor: Lenovo driver: nvidia v: 495.46 bus ID: 01:00.0 
  chip ID: 10de:25e0 
  Display: x11 server: X.Org 1.20.13 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa 
  resolution: 1920x1080~60Hz, 1920x1080~165Hz 
  OpenGL: renderer: NVIDIA GeForce RTX 3050 Ti Laptop GPU/PCIe/SSE2 
  v: 4.6.0 NVIDIA 495.46 direct render: Yes 
Audio:
  Device-1: NVIDIA driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  chip ID: 10de:2291 
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
  vendor: Lenovo driver: N/A bus ID: 06:00.5 chip ID: 1022:15e2 
  Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel 
  v: kernel bus ID: 06:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.13.0-25-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Lenovo driver: r8169 v: kernel port: 2000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: eno1 state: down mac: <filter> 
  Device-2: Realtek vendor: Lenovo driver: rtw89_pci v: N/A port: 1000 
  bus ID: 04:00.0 chip ID: 10ec:8852 
  IF: wlp4s0 state: up mac: <filter> 
  IF-ID-1: gpd0 state: down mac: N/A 
Drives:
  Local Storage: total: 953.87 GiB used: 185.70 GiB (19.5%) 
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFS512GDE9X084N 
  size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: 41010C22 
  scheme: GPT 
  ID-2: /dev/nvme1n1 vendor: Team model: TM8FP4001T size: 953.87 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: ECFM13.4 scheme: GPT 
Partition:
  ID-1: / size: 930.09 GiB used: 185.67 GiB (20.0%) fs: ext4 
  dev: /dev/nvme1n1p4 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Info:
  Processes: 371 Uptime: 13h 17m Memory: 15.48 GiB used: 3.74 GiB (24.1%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: zsh 
  v: 5.8 running in: gnome-terminal inxi: 3.0.38

With my laptop display, I am using an Acer 27'' LCD monitor in a extend mode. My current power settings are as follows -

• Turn off the screen when inactive for - 30 min (on A/C power), 10 min (on battery power)
• Suspend when inactive for - Never (on A/C power), 30 minutes (on battery power)
• When the lid is closed - Suspend (on A/C power), Suspend (on battery power)

Most of the time my laptop is plugged on A/C power (99% of the time). Whenever I usually leave my desk, I have a habit of closing my lid, hence the power settings of suspend. Whenever I come back to my desk and open my lid, my laptop display becomes inactive and only my second monitor is chosen as the active display. And as soon as I change display settings to make the laptop display, everything starts working again. But it is a real pain to enable my main display every time I resume from suspend by opening the lid. Does someone know what is the problem here?

[SMG]

I have a Lenovo Legion 5 15ACH6 laptop with Linux Mint 20.3 Una dual boot with Windows.

Welcome to the forum, unkemptArc99.

Your laptop has a CPU which indicates you have a dual-graphics laptop, Nvidia and AMD. Do you have the graphics setting in the BIOS/UEFI set for only Discrete (Nvidia)?

There have been a number of people with Ryzen laptops who have had issues with the AMD graphics resuming from suspend. I have a feeling the AMD may have priority for your laptop's screen and that may be why the laptop screen is not resuming properly, but I do not know that for sure.

Normally, on dual-graphics laptops, the ports for external monitors are run only by the Nvidia GPU, so AMD graphics issues would not affect it.

There is a newer kernel available, 5.13.0-27. Maybe upgrading to it will help.

System:
Kernel: 5.13.0-25-generic x86_64 bits: 64 compiler: N/A
Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0
Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal

[unkemptArc99]

Thank you for your response, SMG.

Yes, it is indeed a dual-graphics laptop - AMD Ryzen 7 5800H with the Radeon graphics and NVIDIA RTX 3050Ti. In the UEFI, I have made it such that it uses the Discrete Graphics for the display (instead of Dynamic, where the laptop uses the onboard graphics for all stuff until unless specified to use discrete - for power saving reasons). The Dynamic Graphics work well in Windows, because of good support from NVIDIA control panel. But even with that good support, I have had headaches using the Dynamic option. Hence, switched to the Discrete option.

I have a feeling the AMD may have priority for your laptop's screen and that may be why the laptop screen is not resuming properly, but I do not know that for sure.

That is very weird because this priority does not exist when there are no external monitors connected. Resuming from standby works perfectly when the laptop is not connected to any external monitor, and I believe even then the display should be under control from NVIDIA discrete GPU. But I do agree that this might be AMD graphics issue.

There is a newer kernel available, 5.13.0-27. Maybe upgrading to it will help.

Fun fact - I just updated to this yesterday No difference. Do you think there are more fixes for AMD graphics in kernel >= 5.15?

[SMG]

That is very weird because this priority does not exist when there are no external monitors connected. Resuming from standby works perfectly when the laptop is not connected to any external monitor, and I believe even then the display should be under control from NVIDIA discrete GPU.

If this is the case, maybe there is an issue with the Nvidia driver. Did you try the long-term branch driver, the Nvidia-470? The Nvidia-495 is part of the short-term experimental branch.

Do you think there are more fixes for AMD graphics in kernel >= 5.15?

I do not know, but I sure hope there are.

[unkemptArc99]

Did you try the long-term branch driver, the Nvidia-470?

So, downgrading to 470 makes no difference. But downgrading to 460 has a different problem now. After closing my laptop lid, it doesn't go into suspend and continues displaying on the external monitor. Do you know what might be causing this problem?

[SMG]

So, downgrading to 470 makes no difference. But downgrading to 460 has a different problem now. After closing my laptop lid, it doesn't go into suspend and continues displaying on the external monitor. Do you know what might be causing this problem?

The Nvidia-460 driver had some known issues related to suspension, so I would guess that driver version is the problem. I recall quite a few people wanting to switch back to the Nvidia-450 when the Nvidia-460 first came out. I do not think the Nvidia-450 works with your GPU (I think your GPU is too new for it, but I can not recall for sure).

I believe Nvidia has already released a newer version than the 495 for Windows, so I expect there to be a newer Linux driver available soon. At this point, it sounds like staying with the Nvidia-495 or Nvidia-470 until a newer driver is release may be your best option.

[unkemptArc99]

Oh I guess another big wait for Linux users because of corporate interests

But thanks anyway SMG (actually how does one tag other users in posts around here?) I hope this post is useful for others to know that they have to wait if they are seeing a similar problem. I will keep waiting for the driver and update the version in this post when it fixes my issue.