Wake up from suspend problem

No, did you install zram-generator with zypper?

@panorain The BIOSRenamer is an .exe so not usable in linux.
When I downloaded and extracted the file I manually renamed it and copied it to a fat32 formatted usb stick. One of the instruction I read was to turn off the system, insert the usb stick in the usb drive intended for flashing the bios then press the flash bios button etc… and it says flash it with just the mobo and the cpu if I remember it right.

Oh my bad. I didn’t.

@malcolmlewis
So is this the error?

 # systemctl enable --now systemd-zram-setup@zram0.service
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
 
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some

@conram yup, so now if you run free -h you should see zram in use for swap and also in the output of lsblk -f

@malcolmlewis

free -h
               total        used        free      shared  buff/cache   available
Mem:            31Gi       2.2Gi        27Gi        86Mi       1.7Gi        28Gi
Swap:           15Gi          0B        15Gi

zram0
     swap   1     zram0 5522cd17-065b-4822-b3ad-f4a4ebd594c6  

@conram So does it suspend and resume now? Is that swap good enough for your image processing?

I just tried it. Still no go. I guess have to try the bios update tomorrow.
Thanks for helping really appreciate the time and effort you put up to help me.

I am still open to more ideas. It’s like my signature in the old form

If you don't break things first, you will never learn anything :grinning:

Sounds like a plan. What about Blender how is that performing?

Some additional thoughts:

Please see archlinux forums Post #46 Black screen after resuming from sleep (Page 2) / Newbie Corner / Arch Linux Forums
on down to the last post #71

They are discussing the mt7921e chipset, it this on your board?

Disable the systemd bluetooth service:
# systemctl bluetooth disable

Check logs as malcolmlewis suggested

-Thanks

1 Like

Got busy today composting leaves in my garden. @malcolmlewis I think there is some
effect on the cpu using the zram. In blender when trying to render even using gpu the cpu temp. shoot up to 90 degrees in a few seconds, with my previous swap from HDD, CPU is only around 40-50 degrees while using the GPU to render. How do I revert back or take out the zram?

I flash the bios this evening to the latest with the date of 09-20-2025 bios rev 3287.
I check it and it was all good. I use the usb to flash the bios using the flash bios button at the rear end of the mobo (io). I rebooted the machine but unfurtunately still no go.

My guess is it doesn’t play well with the latest kernel in tumbleweed because in the older tumbleweed with kernel 6.12.6-1 suspend works but waking up the monitor is no longer detected.

@conram Not unusual, because CPU and iGPU share the same die… Is it using the discrete card?

How much RAM and swap is being consumed?

All you have to do is stop the systemd-zram-setup@zram0.serviceand disable, I would leave in case you want to use…

The just remove the comment from /etc/fstab the run swapon -a should suffice to switch back.

1 Like

@malcolmlewis Thanks. I didn’t checked how much RAM I just got alarmed when I saw the rise in temperature so I halted the blender render.

It is now getting weirder. A few minutes ago I installed the nvidia driver NVIDIA-Linux-x86_64-508.105.08.run As soon as the driver installation started the monitor turned blank and have to blindedly press the return key. The installation of the driver was successful but I always reject the installation of 32bit compatibility and I didn’t have the visual to reject it.

On the side, I still have one much older tumbleweed on a spare SSD. I will try to boot it using the sata to usb connection and see what happens.

@ malcolmlewis So I booted the old tumbleweed with kernel 6.6.3-1
and bingo suspend to ram works like a charm.


That is the old tumbleweed I booted from the usb drive

@conram so a regression…

Yes, it’s best to switch to a tty, then switch to multi-user systemctl isolate multi-user.target to avoid a blank screen…

I use command line options with the run file, for example (it’s a script);

#!/usr/bin/bash

if (( $# != 1 )); then
	echo "Usage: $0 <RUN_VERSION>" >&2
	exit 1
fi

RUN_VERSION=$1

NVIDIA-Linux-x86_64-$RUN_VERSION.run \
    --ui=none \
    --no-questions \
    --accept-license \
    --disable-nouveau \
    --no-install-libglvnd \
    --no-cc-version-check

There are more you can add…

1 Like

Thanks, I will do this next time when I install a new driver.

Good news!!!
The latest tumbleweed dup today made the suspend to RAM worked .kernel6.17.8--1

Please consider this topic as ā€œsolvedā€ and can be closed.

2 Likes

A Sapphire Pulse Radeon RX550 worked flawlessly with the i7-6700K. For the time being it sits on the shelf.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.