Thank you! I’ve learned my lesson about downgrading the firmware - at I least I hope I did. 
Is there a way to find online the packages included in the live usb image, in order not to have to reboot in usb every time and take screenshots?
When you download the ISO from downloads section of garudalinux website the dropdown mentions a package option you can view the list of package with their version there. → https://iso.builds.garudalinux.org/iso/garuda/dr460nized/231029/garuda-dr460nized-linux-zen-231029.pkgs.txt
4 Likes
I’m sure there is a list of the packages contained in each ISO. However, I’m not sure where exactly you’d find that info as I’m not involved in the development process. You could simply boot the live version one time and save a list to USB thumb drive of your installed packages.
Edit: I now see @NaN provided a way to find that info for you.
Also be sure to read the Arch Wiki entries regarding power management:
https://wiki.archlinux.org/title/Power_management#Audio
See section 3.8.2 PCI Runtime Power Management for writing a udev rule to prevent a USB device from disrupting suspend.
2 Likes
Thanks again @NaN and @tbg, I’ll be sure and do my homework.
Then I’ll update this thread accordingly.
1 Like
There are also many systemd services that can affect suspend. You may want to consider downgrading systemd itself, (if you have no success with downgrading my other package suggestions).
Edit:
I believe I asked you before, but I don’t recall you confirming. Have you tested suspending from the terminal using the command systemctl suspend. Sometimes you will get a different result when initiating suspend in this way.
1 Like
Unfortunately these are more recent ISOs: my linux-firmware is from april I think, given the file name. Maybe there’s a way via terminal from inside the live environment, I’ll look around. 
You’re right, I forgot to try this, sorry.
Now I did and the result was the same (with a downgraded linux-firmware): seemed to suspend, but never fully woke up, fans spinning but black screen. 
It could be Nvidia causing the issue. Take a look at this article when you have a chance:
https://wiki.archlinux.org/title/NVIDIA/Troubleshooting#System_does_not_return_from_suspend
4 Likes
Could be powerdevil & ddcutil running under Plasma? I had to downgrade them both–a recent, known problem. (In Arch, I should mention, not Garuda.)
But as far as Intel goes–if that’s the problem–I usually use an /etc/modprobe.d config one-liner, listed below:
options snd_hda_intel power_save=0
And saved as “snd_hda_intel.conf” in modprobe.d.
And my PCs never wake up arbitrarily.
2 Likes
Thanks! I tried… Unfortunately it seemed to suspend but, again, never correctly woke up: fans spinning, keyboard lighted but only a black inert monitor. 
Hi.
I had a similar problem in the beginning when i installed Garuda. The laptop went sleep or not but never i cant wake it up.
I changed the setting in the “Power management ==> energy saving ==> suspend session” from " Hybrid Sleep" to " Sleep"
1 Like
Thanks! Unfortunately it was already on “Suspend” and also trying “Hybrid suspend” did not change anything in my case, it didn’t even sleep at all.
…and, again unfortunately, the one liner conf did not work either. 
But thank you for the suggestion!
Just a quick update: at the moment I could not locate the problematic service/firmware by downgrading. After a couple of difficult garuda-update round (the now solved problem and another one with slow package retrieving, failing the update process) my system is now fully updated again.
And… it seems to suspend.
But it never ever really wakes up. 
Same old fans spinning, keyboard lighting up, black screen remaining in standby.
Try putting your system into airplane mode before initiating suspend, just in case Bluetooth is messing with resuming.
1 Like
I just noticed this pic of your bios (as I usually ignore all pics).
Have you tried setting the mouse & keyboard to “Enabled” ?
Edit:
Also test enabling “PCI Devices Power On” as I found an old Arch forum post stating this may help with an Intel Sandy Bridge mobo.
4 Likes
Tried everything without any improvements, except your last edit about PCI: later I’ll try that as well! Thank you. 
(oh, and I could not find an airplane mode, so I just disabled bluetooth)
Tried it: it made things worse, since the system didn’t go to sleep (only black screen for like a minute) and then come back to the desktop but freezed. I could move the cursor but that was it, no windows selectable, no button clickable, black wallpaper instad of my regular wallpaper. 
Thanks nonetheless.
Most of the posts about Intel’s Sandy Bridge mobos are very old as this model is ancient by today’s standards. There was a ton of suspend issues in the early years with these models that were mostly fixed with bios or kernel updates over the years. Unfortunately, this model being so old (released 2012 I believe) it is losing support by Intel at this point. I read a report from this year saying because of this lack of support those owning these Sandy Bridge models should consider it end of life and start looking for a replacement.
I’ll keep looking for further suggestions, but there’s not a lot of recent posts about these models as they are so old they’re not in common use these days. There were some kernel parameters I saw posted that helped with suspend in the very early years, but updates to the kernel and bios made these unnecessary after a few years. I guess it might be worth testing these old kernel params, because kernel changes often make old solutions worth trying again. The kernel team is not focusing on keeping hardware this old working properly anymore, and the fewer of these machines in usage the less likely they will ever get verifiable bug reports. I’m thinking you should start planning for this laptops retirement, or consider trying a distro that uses a very old LTS kernel with a few years of support left. Unfortunately, even this solution is running out of time on the meter, as the kernel team has decided to no longer provide the extended service releases that used to be supported for up to six years. I could be wrong, but I think they’ve decided on only providing kernel support for LTS kernels for 3 years maximum. So the clock is definitely ticking on these old Sandy Bridge models.
1 Like
Run this command before suspending:
sudo rmmod -v intel_lpss_pci
If resume is successful afterwards then we can blacklist the module to hopefully correct your issue.