Can Not Wake Mint Edge From Suspend

[MintMagoo]

First, I am assumming Suspend means suspend to ram (sleep), current state is held in active memory and everything else that can be powered down is turned off.

Anyways, when I try Suspend I can not wake the system back up. Not even sure what is supposed to be the correct way to wake back up. Tried various ways but none work. Only choice is to hold power button until the machine turns off and do a fresh boot.

Code: Select all

System:
  Kernel: 6.5.0-17-generic x86_64 bits: 64 compiler: N/A
    Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: LENOVO product: 82XV v: LOQ 15IRH8
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76530 WIN
    serial: <superuser required> UEFI: LENOVO v: LZCN32WW date: 09/23/2023
Battery:
  ID-1: BAT1 charge: 47.3 Wh (78.8%) condition: 60.0/60.0 Wh (100.0%)
    volts: 16.0 min: 15.4 model: BYD L22B4PA0 status: Not charging
CPU:
  Info: 12-core (4-mt/8-st) model: 13th Gen Intel Core i5-13500H bits: 64
    type: MST AMCP arch: N/A rev: 2 cache: L1: 1.1 MiB L2: 9 MiB L3: 18 MiB
  Speed (MHz): avg: 468 high: 793 min/max: 400/4700:3500 cores: 1: 400
    2: 400 3: 488 4: 400 5: 738 6: 793 7: 678 8: 400 9: 400 10: 400 11: 400
    12: 400 13: 400 14: 400 15: 400 16: 400 bogomips: 101990
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA vendor: Lenovo driver: nvidia v: 535.154.05
    bus-ID: 01:00.0
  Device-2: Luxvisions Innotech Integrated Camera type: USB
    driver: uvcvideo bus-ID: 1-7:2
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1920x1080~60Hz
  OpenGL: renderer: NVIDIA GeForce RTX 3050 6GB Laptop GPU/PCIe/SSE2
    v: 4.6.0 NVIDIA 535.154.05 direct render: Yes
Audio:
  Device-1: Intel vendor: Lenovo driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3
  Device-2: NVIDIA vendor: Lenovo driver: snd_hda_intel v: kernel
    bus-ID: 01:00.1
  Sound Server-1: ALSA v: k6.5.0-17-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel port: 4000 bus-ID: 07:00.0
  IF: enp7s0 state: down mac: <filter>
  Device-2: Realtek vendor: Lenovo driver: rtw89_8852be v: kernel
    port: 3000 bus-ID: 08:00.0
  IF: wlp8s0 state: up mac: <filter>
  IF-ID-1: ipv6leakintrf0 state: unknown speed: N/A duplex: N/A
    mac: <filter>
  IF-ID-2: pvpnksintrf0 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-3: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
  IF-ID-4: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
  IF-ID-5: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 1-10:4
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter>
    bt-v: 3.0 lmp-v: 5.2
Drives:
  Local Storage: total: 4.57 TiB used: 3.3 TiB (72.2%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFS001TEJ4X112N
    size: 953.87 GiB temp: 35.9 C
  ID-2: /dev/sda type: USB vendor: Seagate model: BUP Portable
    size: 3.64 TiB
Partition:
  ID-1: / size: 28.01 GiB used: 13.44 GiB (48.0%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 92.5 MiB used: 14 MiB (15.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 18.62 GiB used: 445.3 MiB (2.3%) fs: ext4
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: partition size: 9.55 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p4
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 40 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 367 Uptime: 27m Memory: 15.4 GiB used: 2.16 GiB (14.0%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.4.0 Packages: 2293 Shell: Bash
  v: 5.1.16 inxi: 3.3.13[code]

[SMG]

First, I am assumming Suspend means suspend to ram (sleep), current state is held in active memory and everything else that can be powered down is turned off.

Not all newer computers power everything down in sleep state (S3). A lot nowadays only have S2idle which does not power down as much hardware as S3 state.

Anyways, when I try Suspend I can not wake the system back up. Not even sure what is supposed to be the correct way to wake back up. Tried various ways but none work. Only choice is to hold power button until the machine turns off and do a fresh boot.

Have you checked to see if there is a newer BIOS/UEFI available? If this is the correct link, it appears 34 is available.

Machine:
Type: Laptop System: LENOVO product: 82XV v: LOQ 15IRH8
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0T76530 WIN
serial: <superuser required> UEFI: LENOVO v: LZCN32WW date: 09/23/2023

Does your computer have an option for switchable graphics in the BIOS/UEFI or is it Nvidia only?

[MintMagoo]

Updating the BIOS did not help.

Changing the GPU in BIOS from Discrete to UMA or Dynamic will allow the laptop to wake after suspend.

I have the recommended NVDIA driver installed.

I can wake from sleep on Discrete GPU in Windows (10/11), even when booting from an external drive.

Is this a driver issue or a kernel issue? Or am I missing something?

[SMG]

Updating the BIOS did not help.

Changing the GPU in BIOS from Discrete to UMA or Dynamic will allow the laptop to wake after suspend.

I have the recommended NVDIA driver installed.

I can wake from sleep on Discrete GPU in Windows (10/11), even when booting from an external drive.

Is this a driver issue or a kernel issue? Or am I missing something?

Considering you are using the same kernel in all cases, it doesn't sound like a kernel issue. Additionally, if you are using Dynamic mode, then both the Intel and Nvidia drivers are loaded and those would be the same drivers as when you are using Discrete or UMA.

It sounds to me like an issue related to how Lenovo may have wired the GPUs (only works if Intel is seen)?

If you get stuck and hit the power button, run the following after you reboot to see the last 100 lines of the log of the prior boot cycle.

Code: Select all

journalctl -b -1 | tail -n 100

Maybe that will provide clues as to what is happening.

[MintMagoo]

Code: Select all

Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/ldac_sq
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/ldac_mq
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/aptx_hd
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/aptx_hd
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/aptx
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/aptx
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/sbc
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/sbc
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Feb 16 00:14:17 HOSTNAME bluetoothd[850]: Endpoint registered: sender=:1.54 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Feb 16 00:14:17 HOSTNAME dbus-daemon[852]: [system] Activating via systemd: service name='org.blueman.Mechanism' unit='blueman-mechanism.service' requested by ':1.75' (uid=1000 pid=1944 comm="/usr/bin/python3 /usr/bin/blueman-applet " label="unconfined")
Feb 16 00:14:17 HOSTNAME systemd[1]: Starting Bluetooth management mechanism...
Feb 16 00:14:17 HOSTNAME dbus-daemon[852]: [system] Successfully activated service 'org.blueman.Mechanism'
Feb 16 00:14:17 HOSTNAME systemd[1]: Started Bluetooth management mechanism.
Feb 16 00:14:22 HOSTNAME systemd[1]: systemd-rfkill.service: Deactivated successfully.
Feb 16 00:14:30 HOSTNAME systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 16 00:14:30 HOSTNAME systemd[1]: Finished System Suspend.
Feb 16 00:14:30 HOSTNAME systemd[1]: Stopped target Sleep.
Feb 16 00:14:30 HOSTNAME systemd[1]: Reached target Suspend.
Feb 16 00:14:30 HOSTNAME systemd-logind[874]: Operation 'sleep' finished.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME kernel: Generic FE-GE Realtek PHY r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
Feb 16 00:14:30 HOSTNAME ModemManager[963]: <info>  [sleep-monitor-systemd] system is resuming
Feb 16 00:14:30 HOSTNAME NetworkManager[1046]: <info>  [1708060470.3762] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Feb 16 00:14:30 HOSTNAME NetworkManager[1046]: <info>  [1708060470.3763] device (enp7s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 16 00:14:30 HOSTNAME systemd[1]: Starting NVIDIA system resume actions...
Feb 16 00:14:30 HOSTNAME systemd[1]: Stopped target Suspend.
Feb 16 00:14:30 HOSTNAME suspend[3212]: nvidia-resume.service
Feb 16 00:14:30 HOSTNAME logger[3212]: <13>Feb 16 00:14:30 suspend: nvidia-resume.service
Feb 16 00:14:30 HOSTNAME systemd[1]: nvidia-resume.service: Deactivated successfully.
Feb 16 00:14:30 HOSTNAME systemd[1]: Finished NVIDIA system resume actions.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME vmnet-natd[1442]: RTM_NEWLINK: name:enp7s0 index:2 flags:0x00001003
Feb 16 00:14:30 HOSTNAME vmnetBridge[1420]: RTM_NEWLINK: name:enp7s0 index:2 flags:0x00001003
Feb 16 00:14:30 HOSTNAME NetworkManager[1046]: <info>  [1708060470.6003] device (wlp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 16 00:14:30 HOSTNAME NetworkManager[1046]: <info>  [1708060470.6013] device (p2p-dev-wlp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Feb 16 00:14:30 HOSTNAME NetworkManager[1046]: <info>  [1708060470.6016] manager: NetworkManager state is now DISCONNECTED
Feb 16 00:14:30 HOSTNAME kernel: r8169 0000:07:00.0 enp7s0: Link is Down
Feb 16 00:14:32 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:32 HOSTNAME ModemManager[963]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:07:00.0': not supported by any plugin
Feb 16 00:14:32 HOSTNAME ModemManager[963]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:08:00.0': not supported by any plugin
Feb 16 00:14:32 HOSTNAME acpid[846]: client connected from 1149[0:0]
Feb 16 00:14:32 HOSTNAME acpid[846]: 1 client rule loaded
Feb 16 00:14:32 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:32 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:34 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:40 HOSTNAME systemd-logind[874]: Power key pressed.
Feb 16 00:14:47 HOSTNAME systemd[1]: blueman-mechanism.service: Deactivated successfully.
Feb 16 00:14:52 HOSTNAME systemd-logind[874]: Power key pressed.

[SMG]

Code: Select all

Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:30 HOSTNAME systemd[1]: Starting NVIDIA system resume actions...
Feb 16 00:14:30 HOSTNAME systemd[1]: Stopped target Suspend.
Feb 16 00:14:30 HOSTNAME suspend[3212]: nvidia-resume.service
Feb 16 00:14:30 HOSTNAME logger[3212]: <13>Feb 16 00:14:30 suspend: nvidia-resume.service
Feb 16 00:14:30 HOSTNAME systemd[1]: nvidia-resume.service: Deactivated successfully.
Feb 16 00:14:30 HOSTNAME systemd[1]: Finished NVIDIA system resume actions.
Feb 16 00:14:30 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:32 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:32 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:32 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:34 HOSTNAME kernel: nvidia-modeset: WARNING: GPU:0: NVIDIA (DP-2): G-SYNC Compatible: EDID min refresh rate invalid, disabling G-SYNC Compatible.
Feb 16 00:14:40 HOSTNAME systemd-logind[874]: Power key pressed.
Feb 16 00:14:47 HOSTNAME systemd[1]: blueman-mechanism.service: Deactivated successfully.
Feb 16 00:14:52 HOSTNAME systemd-logind[874]: Power key pressed.

The data shows the computer is waking from suspend. However, it seems there is an issue with the EDID so no graphics are showing.

Please supply the output of

Code: Select all

inxi -Gxxxz

and

Code: Select all

xrandr

and enclose the results of each in code tags as described in this tutorial How to use code display tags on forums.linuxmint.com.

The initial inxi output you provided is an abbreviated version of what we normally request.

[MintMagoo]

Code: Select all

Device-1: NVIDIA vendor: Lenovo driver: nvidia v: 535.154.05 pcie:
    speed: 2.5 GT/s lanes: 8 ports: active: none off: eDP-1
    empty: DP-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:25ec class-ID: 0300
  Device-2: Luxvisions Innotech Integrated Camera type: USB
    driver: uvcvideo bus-ID: 1-7:2 chip-ID: 30c9:00a7 class-ID: fe01
    serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 143 s-size: 341x191mm (13.4x7.5")
    s-diag: 391mm (15.4")
  Monitor-1: DP-2 res: 1920x1080 hz: 60 dpi: 142
    size: 344x193mm (13.5x7.6") diag: 394mm (15.5")
  OpenGL: renderer: NVIDIA GeForce RTX 3050 6GB Laptop GPU/PCIe/SSE2
    v: 4.6.0 NVIDIA 535.154.05 direct render: Yes

Code: Select all

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080     60.00*+

[SMG]

Code: Select all

DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm
   1920x1080     60.00*+

This type of output is not unusual.

I searched on the EDID message and others see it as well so I'm not sure it is related to the system not waking up. That was on a different Lenovo laptop, but the problem they were having (flickering) was only happening in the Discrete mode.

What is the output of

Code: Select all

journalctl -b | grep -i "drm\|nvidia\|NVRM\|01:00.0"

[MintMagoo]

Code: Select all

Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: [10de:25ec] type 00 class 0x030000
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: reg 0x10: [mem 0x50000000-0x50ffffff]
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: reg 0x14: [mem 0x4000000000-0x41ffffffff 64bit pref]
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: reg 0x1c: [mem 0x4200000000-0x4201ffffff 64bit pref]
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: reg 0x24: [io  0x5000-0x507f]
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: reg 0x30: [mem 0xfff80000-0xffffffff pref]
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: BAR 1: assigned to efifb
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: PME# supported from D0 D3hot
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: 126.024 Gb/s available PCIe bandwidth, limited by 16.0 GT/s PCIe x8 link at 0000:00:01.0 (capable of 252.048 Gb/s with 16.0 GT/s PCIe x16 link)
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: vgaarb: setting as boot VGA device
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: vgaarb: bridge control possible
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0x51080000-0x510fffff pref]
Feb 19 12:20:54 HOSTNAME kernel: pci 0000:01:00.1: D0 power state depends on 0000:01:00.0
Feb 19 12:20:54 HOSTNAME kernel: ACPI: bus type drm_connector registered
Feb 19 12:20:54 HOSTNAME kernel: input: FOCA0001:00 2808:0106 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-FOCA0001:00/0018:2808:0106.0001/input/input5
Feb 19 12:20:54 HOSTNAME kernel: input: FOCA0001:00 2808:0106 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-FOCA0001:00/0018:2808:0106.0001/input/input6
Feb 19 12:20:54 HOSTNAME kernel: nvidia: loading out-of-tree module taints kernel.
Feb 19 12:20:54 HOSTNAME kernel: nvidia: module license 'NVIDIA' taints kernel.
Feb 19 12:20:54 HOSTNAME kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Feb 19 12:20:54 HOSTNAME kernel: nvidia: module license taints kernel.
Feb 19 12:20:54 HOSTNAME kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 237
Feb 19 12:20:54 HOSTNAME kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
Feb 19 12:20:54 HOSTNAME kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  535.154.05  Thu Dec 28 15:37:48 UTC 2023
Feb 19 12:20:54 HOSTNAME kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  535.154.05  Thu Dec 28 15:51:29 UTC 2023
Feb 19 12:20:54 HOSTNAME kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Feb 19 12:20:54 HOSTNAME kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
Feb 19 12:20:54 HOSTNAME systemd[1]: Starting Load Kernel Module drm...
Feb 19 12:20:54 HOSTNAME systemd[1]: modprobe@drm.service: Deactivated successfully.
Feb 19 12:20:54 HOSTNAME systemd[1]: Finished Load Kernel Module drm.
Feb 19 12:20:54 HOSTNAME kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
Feb 19 12:20:54 HOSTNAME systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:nvidia_0...
Feb 19 12:20:54 HOSTNAME systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:nvidia_0.
Feb 19 12:20:55 HOSTNAME kernel: nvidia-uvm: Loaded the UVM driver, major device number 234.
Feb 19 12:20:55 HOSTNAME kernel: input: FOCA0001:00 2808:0106 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-FOCA0001:00/0018:2808:0106.0001/input/input11
Feb 19 12:20:55 HOSTNAME kernel: input: FOCA0001:00 2808:0106 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-FOCA0001:00/0018:2808:0106.0001/input/input12
Feb 19 12:20:55 HOSTNAME kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
Feb 19 12:20:55 HOSTNAME kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
Feb 19 12:20:55 HOSTNAME kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
Feb 19 12:20:55 HOSTNAME kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
Feb 19 12:20:57 HOSTNAME audit[812]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=812 comm="apparmor_parser"
Feb 19 12:20:57 HOSTNAME audit[812]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=812 comm="apparmor_parser"
Feb 19 12:20:57 HOSTNAME kernel: audit: type=1400 audit(1708316457.107:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=812 comm="apparmor_parser"
Feb 19 12:20:57 HOSTNAME kernel: audit: type=1400 audit(1708316457.107:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=812 comm="apparmor_parser"
Feb 19 12:20:57 HOSTNAME systemd[1]: Starting NVIDIA Persistence Daemon...
Feb 19 12:20:57 HOSTNAME nvidia-persistenced[874]: Verbose syslog connection opened
Feb 19 12:20:57 HOSTNAME nvidia-persistenced[874]: Now running with user ID 128 and group ID 138
Feb 19 12:20:57 HOSTNAME nvidia-persistenced[874]: Started (874)
Feb 19 12:20:57 HOSTNAME nvidia-persistenced[874]: device 0000:01:00.0 - registered
Feb 19 12:20:57 HOSTNAME nvidia-persistenced[874]: Local RPC services initialized
Feb 19 12:20:57 HOSTNAME systemd[1]: Started NVIDIA Persistence Daemon.
Feb 19 12:21:00 HOSTNAME kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Feb 19 12:21:16 HOSTNAME kernel: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

[SMG]

All that looks normal.

Do you have an option in your BIOS/UEFI to set the Power> Sleep State? Some Lenovos have an option to set this to Windows or Other/Linux. See if you have that option and if switching the mode helps.

The only other idea I have is to try either an OEM kernel or a mainline (newer that what is available in Linux Mint) kernel. I can give instructions for those if either of those is something you want to try.

I checked the Lenovo Community forum and found this Lenovo LOQ sleep mode problem, but that seems to be a different problem than what you are seeing.

I also found this LOQ 15APH8 : not waking from sleep: taking time : black screen. which is for the AMD version and it seems to be the reverse issue (resume only works when in discrete mode). The suggestion there was to downgrade the Nvidia driver version. By the end of the topic, Lenovo support was hoping a future BIOS/UEFI update would help that issue.

[MintMagoo]

No switch for sleep.

Since we're changing the kernel is there any disadvantage going with a debian distro?

LMDE or Dedian Bookworm?

Or does Ubuntu offer something more advanced?

[SMG]

Since we're changing the kernel is there any disadvantage going with a debian distro?

LMDE or Dedian Bookworm?

Or does Ubuntu offer something more advanced?

You have very new hardware (13th-gen Intel CPU). You would have to backport a newer kernel with a Debian-based distro (which comes with 6.1) and even then you would still have an older graphics stack (rest of the packages) than what is available in Linux Mint/Ubuntu. Also, Debian only currently has the 525 Nvidia driver available in their repos.

[MintMagoo]

Ok.

How do we proceed with Mint?

[SMG]

Ok.

How do we proceed with Mint?

What Nvidia driver version are you using in Windows?

There is a both a 545 and a 550 beta available for Linux-based distros. While Windows does not use the same version numbers, they are usually close with the numbers so maybe you are using something newer in Windows?

[MintMagoo]

v. 537.70


I was wondering if I actually gain any benifit running in discrete mode? I don't play any games. I actually run everything in virtual machines including video editing/conversion. Also a real time trading app where responce time is critical. I often have multiple VM's running at the same time. My logic for discrete mode is to force as much RAM and processing as possible away from the CPU and on to the GPU for maximum performance. Always plugged in.

[SMG]

I was wondering if I actually gain any benifit running in discrete mode? I don't play any games. I actually run everything in virtual machines including video editing/conversion. Also a real time trading app where responce time is critical. I often have multiple VM's running at the same time. My logic for discrete mode is to force as much RAM and processing as possible away from the CPU and on to the GPU for maximum performance. Always plugged in.

On-demand mode gives you the opportunity to have certain programs use Nvidia so you may be able to do that to achieve your goals. However, I don't know how that works in VMs.

[MintMagoo]

I upgraded the driver to 545 but still have the issue with the display not waking from sleep.


Playing around with dynamic mode did reveal advantages leaving the setting on discrete

[SMG]

I upgraded the driver to 545 but still have the issue with the display not waking from sleep.

When your computer wakes from sleep, do you normally see a password screen? If so, maybe blindly typing the password will work. We've had situations in the past where that was the case.

The log you provided earlier indicates the operating system (and the nvidia suspend service) are both coming back from suspend so I'm unfortunately running out of ideas. This strikes me as something on Lenovo's end. Perhaps posting on their forum will provide some help.

[MintMagoo]

Yeah, I have been trying to type the password in, but nothing.

[MintMagoo]

Sorry, just noticed your instructions on how to properly post between the tags, thank you.

I just posted on Lenovo, was wondering if I should try NVIDIA and/or Ubunto also?

I did try plugging it into the TV using HDMI and the TV kicked in with an alternate desktop. Was still not able to find a way for the laptop monitor to kick back in though and had to reboot to get it back.


Thank you for your effort.