MX Linux Forum

Posted: **Fri Sep 06, 2024 2:50 am**

I've been plagued by suspend not working properly since installing MX23 (previous releases were fine): sometimes the computer refuses to suspend (goes to black screen then comes back locked up), sometimes it seems to have worked but won't wake up necessitating a reboot, other times it wakes but the keyboard doesn't work. I've tried different kernels, systemd/init boot methods, removing the screensaver etc etc to no avail.

I could just about put up with it not working (I'm on and off the PC all day long so it's a regular issue) but having bought a new monitor yesterday another problem has been introduced - if suspend does work it brings up the display settings window on waking and has the wrong refresh rate set ie it fails to remember the correct settings. I could even live with hibernate instead of suspend but that doesn't work at all, instead of coming back up as expected it reboots.

Any suggestions please?

Code: Select all

System:
  Kernel: 6.4.0-1mx-ahs-amd64 [6.4.4-1~mx23+1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4.0-1mx-ahs-amd64 root=UUID=<filter> ro quiet splash
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.3_ahs_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASRock model: B450M-HDV R4.0 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: P3.20 date: 07/31/2019
CPU:
  Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
    built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 576 KiB
    desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1558 high: 1999 min/max: 1550/3400 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1500 2: 1999 3: 1550 4: 1550 5: 1547 6: 1550
    7: 1550 8: 1543 9: 1550 10: 1550 11: 1546 12: 1270 bogomips: 81438
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  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, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine driver: amdgpu
    v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 3
    speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DVI-D-1
    bus-ID: 08:00.0 chip-ID: 1002:67df class-ID: 0300 temp: 47.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: VA24EHF serial: <filter> built: 2022 res: 1920x1080
    hz: 60 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon RX 570 Series (polaris10 LLVM
    15.0.6 DRM 3.52 6.4.0-1mx-ahs-amd64) direct-render: Yes
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: XFX Pine
    driver: snd_hda_intel v: kernel bus-ID: 3-2:2 pcie: chip-ID: 08bb:2902 gen: 3 class-ID: 0300
    speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 1002:aaf0 class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Texas Instruments PCM2902 Audio Codec type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.4.0-1mx-ahs-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: ASRock driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
  IF-ID-1: br-254cee80ca73 state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Drives:
  Local Storage: total: 465.76 GiB used: 183.94 GiB (39.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS500G2B0B-00YS70 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 40WD
    scheme: MBR
Partition:
  ID-1: / raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 183.94 GiB (40.2%) fs: ext4
    dev: /dev/sda1 maj-min: 8:1
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: 37.0 C mobo: N/A gpu: amdgpu temp: 47.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 1893
Repos:
  Packages: 2873 pm: dpkg pkgs: 2868 libs: 1565 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 5
  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/google-earth-pro.list
    1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
    2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm ahs
Info:
  Processes: 413 Uptime: 6m wakeups: 8 Memory: 15.54 GiB used: 2.1 GiB (13.5%) 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: BIOS (legacy, CSM, MBR)

Posted: **Fri Sep 06, 2024 4:48 am**

I can only suggest you simply turn the monitor off. Either let the OS do it, or use the power button. I bought a minipc specifically so I could leave it on 24/7 and use it as my media pc connected to my nas. I just physically turn my monitor off and let the pc idle. No suspend, nothing and I don't care if it works either. On my laptop with 23.3 suspend doesn't work I noticed, but, I have successfully gotten hibernate to work. I literally have to wait for the screen to flash twice and then I hit the power button once and then hold it down til the laptop dies. It successfully hibernates only in this manner.
It seems all newer pc's, windows incl., are trying to control everyone's device via it's power and each device seems to have a mind of it's own. I completely removed IntelME from my laptop specifically because I do not want anyone but me in complete control of my pc.
It's not really the OS at fault but more the manufacturers of the hardware itself. More control for them, less for you.

Posted: **Fri Sep 06, 2024 5:36 am**

davidy wrote: Fri Sep 06, 2024 4:48 am ... I completely removed IntelME from my laptop

Interesting, how did you manage that? I heard it can't be done.

Posted: **Fri Sep 06, 2024 5:40 am**

@PaulR I would first try changing the kernel using MX Package Installer.

Also: did you use the ahs version of MX 21 where everything worked? With only a single core on a 5 yr old machine I'm not sure that you need it.

Posted: **Fri Sep 06, 2024 5:42 am**

davidy wrote: Fri Sep 06, 2024 4:48 am I can only suggest you simply turn the monitor off. Either let the OS do it, or use the power button. I bought a minipc specifically so I could leave it on 24/7 and use it as my media pc connected to my nas. I just physically turn my monitor off and let the pc idle. No suspend, nothing and I don't care if it works either. On my laptop with 23.3 suspend doesn't work I noticed, but, I have successfully gotten hibernate to work. I literally have to wait for the screen to flash twice and then I hit the power button once and then hold it down til the laptop dies. It successfully hibernates only in this manner.
It seems all newer pc's, windows incl., are trying to control everyone's device via it's power and each device seems to have a mind of it's own. I completely removed IntelME from my laptop specifically because I do not want anyone but me in complete control of my pc.
It's not really the OS at fault but more the manufacturers of the hardware itself. More control for them, less for you.

Thanks for the info and suggestion. There are related two reasons I don't want to leave the PC on idle: it's bad for the planet and it's bad for my electricity bill. It would mean having the PC on from around 6am until maybe 10pm, usually I'd use it for around a third of that time, much of it for short periods (5-20 mins) with some longer sessions so rebooting is a pain even with SSD.

I switched the PC off after the original post and when I put it back on to check the forum I was presented with two instances of the display properties window, both showing the wrong refresh rate!! What the....

Posted: **Fri Sep 06, 2024 5:48 am**

Jerry3904 wrote: Fri Sep 06, 2024 5:40 am @PaulR I would first try changing the kernel using MX Package Installer.

Also: did you use the ahs version of MX 21 where everything worked? With only a single core on a 5 yr old machine I'm not sure that you need it.

Thanks for this but I've already been down that route without success. I honestly can't recall if I was using the advanced hardware version previously. I only built this PC about 2yrs ago, I'm guessing that date is the BIOS version date and according to AMD it's a 6 core processor. I'm not greatly interested in the minutiae of hardware I just bought the components for a half decent PC which works great apart from this issue (and the new one related to the new monitor!).

Posted: **Fri Sep 06, 2024 5:54 am**

Oh, I think I just solved the monitor issue - went to advanced tab and set it to do nothing when a 'new' monitor is connected. Manually opening the display settings seems it remembered the proper refresh rate.

Posted: **Fri Sep 06, 2024 7:41 am**

Excellent. If that is persistent, please mark your thread "solved" (little check mark in upper right corner of your post)

Posted: **Fri Sep 06, 2024 8:39 am**

Jerry3904 wrote: Fri Sep 06, 2024 7:41 am Excellent. If that is persistent, please mark your thread "solved" (little check mark in upper right corner of your post)

Sorry, that's just the monitor issue mentioned incidentally, I'm afraid the suspend issue persists. I've tested various settings in the BIOS in case they're having some effect but that didn't help. :(

Posted: **Fri Sep 06, 2024 10:14 am**

Jerry3904 wrote: Fri Sep 06, 2024 5:40 am
Also: did you use the ahs version of MX 21 where everything worked? With only a single core on a 5 yr old machine I'm not sure that you need it.

@Jerry3904 The AMD Ryzen 5 2600 is a 6 core 12 thread CPU.

Code: Select all

CPU:
  Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
    built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 576 KiB

Posted: **Fri Sep 06, 2024 10:19 am**

Does suspend work with the live ISO? (that is Debian's 6.1 kernel)

Posted: **Fri Sep 06, 2024 11:02 am**

OK, just misread the QSI

Posted: **Fri Sep 06, 2024 11:12 am**

The xfce4-screensaver is known to cause such problems but you already removed that.

What if you suspend with this?

Code: Select all

sudo pm-suspend

Posted: **Fri Sep 06, 2024 11:22 am**

Jerry3904 wrote: Fri Sep 06, 2024 11:02 am OK, just misread the QSI

Took me a second myself but I believe it reads like this. The "cpu: 1x" line just means there is only 1 CPU in the machine.

Code: Select all

cpus: 1x
cores: 6
threads: 12

Posted: **Fri Sep 06, 2024 11:43 am**

Just going to throw this out there... I had some issues on an HP with this, until I went into the bios and turned off Fast Boot. Once that was off, the system worked very well on suspend. (Hibernate actually) .

Your system sounds a little like what I saw, but it was worse on mine. ( Black screen and unable to get out of it (some times;-/), wireless was WAY weird, keyboard and touchpad were sometimes non-existent. )

You might check that.

Posted: **Sat Sep 07, 2024 12:18 pm**

Kermit the Frog wrote: Fri Sep 06, 2024 11:12 am The xfce4-screensaver is known to cause such problems but you already removed that.

What if you suspend with this?
Code: Select all
sudo pm-suspend

Thanks for the suggestion. I've tried it before and like the xfce4-session-logout --suspend I'm currently using, it gives variable results: sometimes everything is fine other times it locks up with a black screen and other times it comes back with a dead keyboard. That's what seems to make it so difficult to diagnose.

Posted: **Sat Sep 07, 2024 12:19 pm**

CharlesV wrote: Fri Sep 06, 2024 11:43 am Just going to throw this out there... I had some issues on an HP with this, until I went into the bios and turned off Fast Boot. Once that was off, the system worked very well on suspend. (Hibernate actually) .

Your system sounds a little like what I saw, but it was worse on mine. ( Black screen and unable to get out of it (some times;-/), wireless was WAY weird, keyboard and touchpad were sometimes non-existent. )

You might check that.

Thank you, I'll give it a shot and report back although it might take a day or two as the fault is intermittent.

Posted: **Sat Sep 07, 2024 12:22 pm**

Since it's sometimes (random):

Take the rams out then re-seat (take them out no matter they look tight).

(Since it's a desktop it won't be difficult)

Posted: **Sat Sep 07, 2024 1:26 pm**

PaulR wrote: Sat Sep 07, 2024 12:19 pm
CharlesV wrote: Fri Sep 06, 2024 11:43 am Just going to throw this out there... I had some issues on an HP with this, until I went into the bios and turned off Fast Boot. Once that was off, the system worked very well on suspend. (Hibernate actually) .

Your system sounds a little like what I saw, but it was worse on mine. ( Black screen and unable to get out of it (some times;-/), wireless was WAY weird, keyboard and touchpad were sometimes non-existent. )

You might check that.
Thank you, I'll give it a shot and report back although it might take a day or two as the fault is intermittent.

Just checked and fast boot is already disabled.

Posted: **Sat Sep 07, 2024 1:37 pm**

Kermit the Frog wrote: Sat Sep 07, 2024 12:22 pm Since it's sometimes (random):

Take the rams out then re-seat (take them out no matter they look tight).

(Since it's a desktop it won't be difficult)

Could try it I guess but don't see why that would only affect suspend/resume and nothing else.

Posted: **Sat Sep 07, 2024 1:40 pm**

That's also true. No random freezings ... Just, no harm.

In the meantime no need to lose time with mem-test cause many times with such issues it showed everything was ok, then re-seating the rams solved the issue.

You can (also) try the most recent "Liquorix" kernel even from the original source (or just from MXPI).

https://liquorix.net/debian/pool/main/l ... _amd64.deb

https://liquorix.net/debian/pool/main/l ... _amd64.deb

Posted: **Sat Sep 07, 2024 2:54 pm**

LU344928 wrote: Fri Sep 06, 2024 5:36 am
davidy wrote: Fri Sep 06, 2024 4:48 am ... I completely removed IntelME from my laptop
Interesting, how did you manage that? I heard it can't be done.

Sytem76 has a bootable iso to do just that (49mb "lemp10-disable-me.img") but it would of course only work on their hardware such as the Lemur Pro I bought. Wish they'd had an amd laptop when I purchased. Their brand new lightweight amd laptop is hundreds less than what i payed and with much better hardware AND doesn't have intelme by default cause it's amd. I can't afford to spend $1300 right now when my lemur pro is perfect still. Makes me think my laptop is some kind of unicorn but I know others have done the same with this laptop.

"Bad for your electricity bill?". I bought one of those kill-a-watt meters. My nas Idles at around 65W (jumps to 110+W at boot) and is on 24/7 cause that's how they are supposed to work. Other than buying a solar panel and using a battery to run my computers, which I'd love to do, there is no help in that. Turn other lights off if you're so worried. The main thing to consider when running a pc 24/7 is dust infiltration, not the electric bill, and that requires a filter on the intake vents. I buy those thin 4"x12" electrostatic dust filters and put one on both my minipc's which have tiny little fans just so I could leave it on 24/7 and not worry about dirt collecting on the inside. That alone will increase the lifespan. My nas has no filter because I'd practically have to wrap it and that would look ridiculous. I also bought a Datavac Electric Duster. 4A blower cleaner. Either that or simply get a minpc with zero moving parts such as the Protectli device in my sig. The thing is if it gets no power it is useless to begin with so worrying about your electric bill is a waste of time when you do have options.

Posted: **Sat Sep 07, 2024 4:34 pm**

I removed xfce4-screensaver in 21.3 and from this post realized it was reintroduced in 23.3. After removing it , again, suspend functions properly. Like I said every pc is slightly different in regards to hardware, drivers, software, and personal configs and you have to find what works for you and what doesn't. TG suspend is not a requirement of any kind for regular usage but I hope you figure out what your configuration is doing, or not, that prevents suspend from happening.
Check your services too. I disable anything unnecessary myself just to keep the footprint as small as possible. I connect to my nas using ftp so I completely disabled samba altogether. Point is you need to know exactly what the pc is running to narrow down the suspend problem.

Posted: **Sun Sep 08, 2024 5:11 am**

davidy wrote: Sat Sep 07, 2024 4:34 pm I removed xfce4-screensaver in 21.3 and from this post realized it was reintroduced in 23.3. After removing it , again, suspend functions properly. Like I said every pc is slightly different in regards to hardware, drivers, software, and personal configs and you have to find what works for you and what doesn't. TG suspend is not a requirement of any kind for regular usage but I hope you figure out what your configuration is doing, or not, that prevents suspend from happening.
Check your services too. I disable anything unnecessary myself just to keep the footprint as small as possible. I connect to my nas using ftp so I completely disabled samba altogether. Point is you need to know exactly what the pc is running to narrow down the suspend problem.

Thanks for this. I've been trying to solve it for maybe a year but still no closer. I don't have deep enough knowledge (or time to investigate them) to figure out what services can be safely removed, I'm pretty much resigned to living with a hobbled system for the time being.

Posted: **Wed Apr 30, 2025 11:19 am**

Just a bump for this topic with a bit of additional info: As a long term experiment, in January I replaced MX with the latest version of Mint (MATE). I've used it solidly until yesterday and found that both suspend and hibernate worked perfectly every time I used them so it's not a hardware or BIOS issue as far as I can tell.

I've now re-installed MX Linux 23.6 and the old issues have reappeared ie sometimes suspend doesn't 'stay down', it comes back up immediately but the keyboard is dead necessitating a reboot (not log out). Other times it goes down but won't come back up at all. I've tried it by manually clicking the option on the 'log out' menu and via both the Power Manager app's power button setting and the system power saving tab inactivity timeout.

Any more thoughts would be welcome (to save reading the entire thread I've tried other kernels, fast boot BIOS setting, re-seating RAM, using 'sudo pm-suspend' command and removing XFCE screensaver all to no avail).

Posted: **Wed Apr 30, 2025 11:52 am**

Are you still using the default Debian kernel? There's ample evidence here in the forums that Ryzen based systems just work better overall when a Liquorix kernel is deployed.

Posted: **Wed Apr 30, 2025 2:55 pm**

j2mcgreg wrote: Wed Apr 30, 2025 11:52 am Are you still using the default Debian kernel? There's ample evidence here in the forums that Ryzen based systems just work better overall when a Liquorix kernel is deployed.

I'm using whatever is in the standard distro. Which of those Liquorix kernels is recommended - the latest?

Posted: **Wed Apr 30, 2025 3:03 pm**

Hmm, I looked in Software Manager and these are installed, not sure what I should do:

Posted: **Wed Apr 30, 2025 3:31 pm**

PaulR wrote: Wed Apr 30, 2025 3:03 pm Hmm, I looked in Software Manager and these are installed, not sure what I should do:

Post your current QSI. It will give an accurate view of what's in use.

Posted: **Wed Apr 30, 2025 4:21 pm**

Here you go:

Code: Select all

System:
  Kernel: 6.14.4-1-liquorix-amd64 [6.14-6~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.14.4-1-liquorix-amd64
    root=UUID=<filter> ro quiet splash resume=UUID=<filter> resume_offset=30240768
  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_ahs_x64 Libretto April 13  2025 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Desktop Mobo: ASRock model: B450M-HDV R4.0 serial: <superuser required>
    UEFI-[Legacy]: American Megatrends v: P3.20 date: 07/31/2019
CPU:
  Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 2 level: v3 note: check
    built: 2018-21 process: GF 12nm family: 0x17 (23) model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 576 KiB
    desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 1549 high: 1550 min/max: 1550/3400 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1550 2: 1547 3: 1548 4: 1550 5: 1550 6: 1548
    7: 1550 8: 1550 9: 1550 10: 1550 11: 1550 12: 1550 bogomips: 81437
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT vulnerable
  Type: spec_rstack_overflow mitigation: Safe RET
  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; STIBP: disabled; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] vendor: XFX Pine driver: amdgpu
    v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 1
    speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: HDMI-A-1 empty: DP-1,
    DP-2, DP-3, DVI-D-1 bus-ID: 08:00.0 chip-ID: 1002:67df class-ID: 0300 temp: 42.0 C
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu 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: HDMI-A-1 mapped: HDMI-A-0 model: VA24EHF serial: <filter> built: 2022 res: 1920x1080
    hz: 60 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: AMD Radeon RX 570 Series (radeonsi polaris10
    LLVM 15.0.6 DRM 3.61 6.14.4-1-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: XFX Pine
    driver: snd_hda_intel bus-ID: 3-2:2 v: kernel pcie: chip-ID: 08bb:2902 gen: 3 class-ID: 0300
    speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 1002:aaf0 class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
  Device-3: Texas Instruments PCM2902 Audio Codec type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.14.4-1-liquorix-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/8211/8411 PCI Express Gigabit Ethernet vendor: ASRock
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 465.76 GiB used: 129.18 GiB (27.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WDS500G2B0B-00YS70 size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 40WD
    scheme: GPT
Partition:
  ID-1: / raw-size: 465.76 GiB size: 457.38 GiB (98.20%) used: 129.18 GiB (28.2%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 19.56 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 38.2 C mobo: N/A gpu: amdgpu temp: 42.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 712
Repos:
  Packages: 2569 pm: dpkg pkgs: 2564 libs: 1385 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0 pm: flatpak pkgs: 5
  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://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
    2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm ahs
Info:
  Processes: 380 Uptime: 1h 30m wakeups: 1 Memory: 15.56 GiB used: 2.65 GiB (17.0%) 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: BIOS (legacy, CSM, MBR)

Posted: **Thu May 01, 2025 5:11 am**

This seems to be going from bad to worse. I disabled all power management features and the XFCE screensaver. If I choose 'suspend' from the log out window the system suspends as expected and the display goes off (shows yellow powered-but-not-active light). When I press a key to bring the computer back up it comes to life but the monitor stays off (its light stays yellow).

I then tried setting the display power management settings as per this image just to see what happened. When I returned after about 10 mins the display was off (yellow light), the CPU was on (as expected) but the display wouldn't come back up when a key was pressed or if I turned it off and on (shows 'No HDMI Signal' message). I know there's nothing wrong with the monitor, it has to be something else.

Just a thought - I don't know anything about these things in detail but would it be worth trying Fluxbox instead of XFCE or is that unlikely to be where the problem lies?

Posted: **Thu May 01, 2025 6:11 am**

I installed Fluxbox and so far suspend is working perfectly! I just need to learn how to use a different window manager but that's better than not having the suspend issue for me.

MX Linux Forum

More 'suspend' issues

More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues

Re: More 'suspend' issues