amd64-microcode

I had the same problem with screen not coming back up after suspend, I didn't have the amd-firmware installed nor the microcode package installed, so I went and installed both at the same time, so i'm not sure which one solved the issue or if both are needed, but it all works fine now.

But this in in daedalus, I haven't messed with excalibur yet.

have tried these "fixes" here

"Enabling/disabling wake up from suspend for USB devices"
https://askubuntu.com/questions/848698/ … usb-device

"udev rule"
https://gist.github.com/bendavis78/57e9 … 75acdba394

but it does not make any difference, have also tried attaching a usb keyboard to see if it wakes from that, to no avail;
as said, the keyboard, which normally wakes, is on the ps/2 port, but actually it has a usb-connector (it is one of those cherry, which comes with ps/2 adapter)
those ps/2 port seem not covered by these "hacks" above with lsusb etc.

possibly the "excalibur" is not ready yet, lets hope the best.

EDIT: @greenjeans, could you please the share name for "microcode" you installed, since have also AMD graphics card installed (rx 7000).

sudo apt install firmware-
firmware-amd-graphics         firmware-linux-free
firmware-ast                  firmware-linux-nonfree
firmware-ath9k-htc            firmware-marvell-prestera
firmware-atheros              firmware-mediatek
firmware-b43-installer        firmware-misc-nonfree
firmware-b43legacy-installer  firmware-myricom
firmware-bnx2                 firmware-netronome
firmware-bnx2x                firmware-netxen
firmware-brcm80211            firmware-nvidia-graphics
firmware-carl9170             firmware-nvidia-gsp
firmware-cavium               firmware-nvidia-tesla-gsp
firmware-cirrus               firmware-qcom-media
firmware-intel-graphics       firmware-qcom-soc
firmware-intel-misc           firmware-qlogic
firmware-intel-sound          firmware-realtek
firmware-ipw2x00              firmware-samsung
firmware-ivtv                 firmware-siano
firmware-iwlwifi              firmware-sof-signed
firmware-libertas             firmware-ti-connectivity
firmware-linux                firmware-zd1211

That's why we recommend using codenames in sources.list.

So that may be why you're getting an error.

Also I don't think using the "testing" repo is the same exact thing as using the excalibur repo. I've loaded the testing before just to look at what's available, but haven't peeked at excalibur. I could be wrong.

In addition to the AMD firmware package, I also have the microcode package, don't know if that makes a difference in this case though.

XFCE4 does wake from sleep on Devuan 5.0;
however upgrading to Devuan 6.0 does break it;

is there a solution , or do i just need another kernel?

i have installed just the standard ATI driver package

sudo apt-get install firmware-amd-graphics libgl1-mesa-dri libglx-mesa0 mesa-vulkan-drivers xserver-xorg-video-all

the solution provided by @tyrlak does not seem solve in my case, thanks.

EDIT: maybe the upgrade to Excalibur was not properly done, sine i am getting error like these

Error: The repository 'http://deb.devuan.org/merged testing-security Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Error: The repository 'http://deb.devuan.org/merged testing-updates Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

EDIT2:

during boot there are some status messages, the first one is

config failed: usb hub doesn't have any  ports

or similar.

my mainboard uses a ps/2 port where i have connected the keyboard?

- I clones this repo:  https://gitlab.com/kernel-firmware/linux-firmware.git
- I copied the amdgpu folder here --> /lib/firmware

Hope this can help someone else with this issue. Thank you everyone for your amazing support<3

[    3.746627] ACPI Warning: SystemIO range 0x00000000000004B0-0x00000000000004BF conflicts with OpRegion 0x0000000000000480-0x00000000000004BF (\_SB.PCI0.SBRG.SIOR.GPIO) (20220331/utaddress-204)
[    3.746637] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[    3.746639] ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x00000000000004BF (\_SB.PCI0.SBRG.SIOR.GPIO) (20220331/utaddress-204)
[    3.746644] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[    3.746645] lpc_ich: Resource conflict(s) found affecting gpio_ich

This has gone away after I run Xorg -configure, copied xorg.conf to /etc/X11 (it was probably not there for obvious "suggested" things) and after having set modesetting in Device=intel and after having removed xorg-input-video-driver rebooted... prompt. No slim login, good!!!

Reinstalled xorg driver mentioned, logged in, and it goes some sort of broken hybernate instead of suspend.

Than I checked the dmesg. ACPI warning gone. Perfect. Went to remove xorg.conf, rebooted, suspend, and if I plug in something usb flavored device going away for say 30 min I gotta kill xfw4. And its good. Better than suggested. I kinda like it. For me it is solved, don't know exactly what I did but... mmm

I've never looked into gnome. Maybe you can instal xfce4, it wont do any bad. You can than follow that xfwm4 problem above, and see.

Gnome AFAIK is not so happy with wildly killing processes to test or solve things but I don't know much of it.

Are you on xfce?

If yes (and if it is a xfwm4 related problem like mine is) the only process of xfwm4 present is the one I mentioned above. For me it solves the problem and I can get it to sleep many times before it reoccurs. I agree it has to do with peripherals (usb probably), I'm not an expert, and for now it is good like this.

I would try to automate a killing of that process while suspending the system. That 's the only thing I can tell you.

Either you can't use at all the monitor after suspend, or you see and move a mouse with black screen and nothing else.

If the second case: I was the same as you untill I reduced the power manager do almost nothing but  pop the screensaver and suspend instead of hibernate. After that I got finally the desktop but freezed up every time I came back from a sleep state. Then I did the search in a different tty with htop to find out the problem (which I have not managed to solve anyway, I just do this every freeze).

If the first case (Monitor unaccessible): that is not my case. Mine was as described.

For now is just this. I'm on a old 32 bit desktop, so I thought maybe a hardware related issue.

I couldn't see anything like what you described DevNUp, so didn't know how I could apply/test this.

xfwm4 --display :0.0 --sm-client -id [alfanumeric-value-blahblah]

in my case works.

But randomly the freeze reoccurs (a bit less frequently), even though I can not explain why I noticed on boot a NFS error which adresses another id related problem, could this be something?

I don't have u5 version of xserver packages but I have u2 and u7 from daedalus-security.

Do I have to change to devuan-security to find out them?