Can't Wake From Suspend With Key Any More [Solved]

[AltairIV]

Until a few days ago, I could wake my computer with a press of a keyboard key, which I loved.
Then weirdness set in.....suspend would wake itself after a few minutes.
That has now stopped but now I can only wake by pressing the power button which is a pain as the laptop is on the floor with the cover closed and the power button is on the inside.
Just remembered that the other day I had to go into the other SSD (Windows 7, MBR non EUFI) so had to disable EUFI and reset to default Boot settings then enabled EUFI to boot to MX. Have done this before without causing the wake from suspend issue.
If it's not that, then the only other thing I can think of is update related.
My snapshots are daily but only the current snapshot is kept so it won't be old enough to help.
Would appreciate any help with this, but please keep the instructions basic, thanks.

Code: Select all

System:
  Kernel: 6.1.0-38-amd64 [6.1.147-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-38-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.6_x64 Libretto April 13  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop System: Notebook product: P17SM-A v: N/A serial: <superuser required>
  Mobo: Notebook model: P17SM-A serial: <superuser required> UEFI: American Megatrends v: 4.6.5
    date: 09/12/2014
CPU:
  Info: model: Intel Core i7-4710MQ bits: 64 type: MT MCP arch: Haswell gen: core 4 level: v3
    note: check built: 2013-15 process: Intel 22nm family: 6 model-id: 0x3C (60) stepping: 3
    microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 923 high: 1019 min/max: 800/3500 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 899 2: 993 3: 1019 4: 800 5: 989 6: 987 7: 800 8: 900
    bogomips: 39903
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: CLEVO/KAPOK driver: i915
    v: kernel arch: Gen-7.5 process: Intel 22nm built: 2013 ports: active: DP-2,HDMI-A-2 off: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:0416 class-ID: 0300
  Device-2: NVIDIA GM204M [GeForce GTX 960 OEM / 970M] vendor: CLEVO/KAPOK driver: N/A
    alternate: nouveau non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx
    process: TSMC 28nm built: 2014-19 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:13d8 class-ID: 0300
  Device-3: Bison BisonCam NB Pro type: USB driver: uvcvideo bus-ID: 2-10:7 chip-ID: 5986:055c
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99")
  Monitor-1: DP-2 pos: primary model: Dell P2225H serial: <filter> built: 2025 res: 1920x1080
    hz: 60 dpi: 102 gamma: 1.2 size: 476x268mm (18.74x10.55") diag: 546mm (21.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 model: Sony TV 00 serial: <filter> built: 2015
    res: 1920x1080 hz: 60 dpi: 40 gamma: 1.2 size: 1218x685mm (47.95x26.97") diag: 1397mm (55")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-3: eDP-1 note: disabled model: AU Optronics 0x149d built: 2009 res: 1920x1080 dpi: 128
    gamma: 1.2 size: 381x214mm (15x8.43") diag: 437mm (17.2") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4600 (HSW GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: CLEVO/KAPOK
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c class-ID: 0403
  Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: CLEVO/KAPOK 8
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20 class-ID: 0403
  Device-3: NVIDIA GM204 High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fbb class-ID: 0403
  API: ALSA v: k6.1.0-38-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: CLEVO/KAPOK
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 05:00.2
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 bus-ID: 06:00.0 chip-ID: 8086:08b1 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 2-4:5
    chip-ID: 8087:07dc class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 6 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0
    sub-v: e00 hci-v: 4.0 rev: e00
  Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony
Drives:
  Local Storage: total: 1.82 TiB used: 29.34 GiB (1.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 3B6Q scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 840 EVO 1TB size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: BB6Q
    scheme: GPT
Partition:
  ID-1: / raw-size: 931.26 GiB size: 915.57 GiB (98.31%) used: 29.34 GiB (3.2%) fs: ext4
    dev: /dev/sdb2 maj-min: 8:18
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/sdb1 maj-min: 8:17
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2441 libs: 1298 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bookworm main non-free
Info:
  Processes: 244 Uptime: 9h 21m wakeups: 12 Memory: 15.53 GiB used: 2.21 GiB (14.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[j2mcgreg]

On which of your two Samsung SSDs have you installed MX?

[AltairIV]

On which of your two Samsung SSDs have you installed MX?

MX is on ID-2 840 Evo, though it is in the primary slot. The other slot, ID-1 860 Evo (Win7) is in the slot under the CD drive which I would have thought is secondary.
I haven't changed the boot order as only one of the SSD's can be found/can boot, depending on whether UEFI is enabled or not. Unless I reset default boot settings, the Win7 SSD isn't found.

[j2mcgreg]

On which of your two Samsung SSDs have you installed MX?

MX is on ID-2 840 Evo, though it is in the primary slot. The other slot, ID-1 860 Evo (Win7) is in the slot under the CD drive which I would have thought is secondary.
I haven't changed the boot order as only one of the SSD's can be found/can boot, depending on whether UEFI is enabled or not. Unless I reset default boot settings, the Win7 SSD isn't found.

I asked because that SSD is at least thirteen years old and should be replaced fairly soon. See here:
https://www.techpowerup.com/ssd-specs/s ... o-1-tb.d42
It may not be as responsive as it was when it was new.

[AltairIV]

I asked because that SSD is at least thirteen years old and should be replaced fairly soon. See here:
https://www.techpowerup.com/ssd-specs/s ... o-1-tb.d42
It may not be as responsive as it was when it was new.

It doesn't really explain why wake from suspend has transferred from key stroke to power button.
Also that SSD was only in use for about 5 years and that was light use.... before being put back into service for MX. SSD's don't fail because of age alone.
Nor have there been any other potential signs of the SSD failing.

[AltairIV]

I fixed it.
I changed the power management settings, re-started, then changed the settings back to how they were and it fixed the problem.

[j2mcgreg]

@AltairIV wrote:

Also that SSD was only in use for about 5 years and that was light use.... before being put back into service for MX. SSD's don't fail because of age alone.

Actually they do because their plastic housings can shrink over time causing improper connections.

[AltairIV]

@AltairIV wrote:

Also that SSD was only in use for about 5 years and that was light use.... before being put back into service for MX. SSD's don't fail because of age alone.

Actually they do because their plastic housings can shrink over time causing improper connections.

Well the assumption was clearly continual use over at least 13 years where memory degradation would be the most usual cause of deterioration.
That assumption was wrong, now you move the goal posts to some sort of shrinkage. A transfer of key stroke to power button with no other potential symptoms of SSD failure does not point to SSD failure and as it turned out,
it was the power management settings which had gone awry.

Do feel free to misuse the QSI rule to sneer away at my aged system and make assumptions (wrongly) about it's failure.
Some of you people never give up on the chance to humiliate and sneer. You force us to provide a lot of personal information by use of a system of rather rude bullying.
That information provides location by the mirror indicated and a person's economic position.
Having forced us to give up that information to get help, you are not then to misuse that information to humiliate us with.

[j2mcgreg]

@AltairIV wrote:

Do feel free to misuse the QSI rule to sneer away at my aged system and make assumptions (wrongly) about it's failure.
Some of you people never give up on the chance to humiliate and sneer.

Lose the attitude. The simple truth is that all technology eventually dies and part of my job here is to warn users of the situation before they encounter a catastrophic failure. Now that you are aware of the situation, it is still your machine and you can do with what you want.

[AltairIV]

@AltairIV wrote:

Do feel free to misuse the QSI rule to sneer away at my aged system and make assumptions (wrongly) about it's failure.
Some of you people never give up on the chance to humiliate and sneer.

Lose the attitude. The simple truth is that all technology eventually dies and part of my job here is to warn users of the situation before they encounter a catastrophic failure. Now that you are aware of the situation, it is still your machine and you can do with what you want.

You and some of your colleagues need to "lose the attitude" and stop being so damn rude to us. This technology has not died, you were wrong and aren't big enough to admit it but like some of your colleagues, you believe that the normal rules don't apply to you. You think you are untouchable gods.
You broadcast the age of my SSD and your incorrect assumption of it's failure without knowing the facts.
Yes it's my machine and I am well aware that I can do what I want with it without you telling me, thank you.

There is a difference between moderating these boards and stalking them for a sense of power over others.