Not sure if your solution will last come the next update? I see you have a similar Graphics Card to me I have GTX 1060 to your 1050ti & from another thread on here it seems they may be too old to support the power options hence the problem. With a bit of searching I found the following: from here https://download.nvidia.com/XFree86/Linux-x86_64/555.58.02/README/powermanagement.html
Known Issues and Workarounds (at bottom of page in chapter 21)
On some systems, where the default suspend mode is "s2idle", the system may not resume properly due to a known timing issue in the kernel. The suspend mode can be verified by reading the contents of the file /sys/power/mem_sleep. The following upstream kernel changes have been proposed to fix the issue:
https://lore.kernel.org/linux-pci/20190927090202.1468-1-drake@endlessm.com/
https://lore.kernel.org/linux-pci/20190821124519.71594-1-mika.westerberg@linux.intel.com/
In the interim, the default suspend mode on the affected systems should be set to "deep" using the kernel command line parameter "mem_sleep_default" -
mem_sleep_default=deep
So you could try checking that I then changed this in my boot file as per these instructions:
Changed with these instructions from Chat GPT
To set mem_sleep_default=deep in openSUSE, follow these steps:
1. Edit the Bootloader Configuration
Open a terminal and edit the GRUB configuration file:
sudo nano /etc/default/grub
Find the line that starts with:
GRUB_CMDLINE_LINUX_DEFAULT="..."
and append mem_sleep_default=deep to it. For example:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"
2. Update GRUB Configuration
After saving the file (Ctrl + X, then Y, then Enter), update GRUB:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
3. Reboot the System
Restart your machine to apply the changes:
sudo reboot
4. Verify the Setting
After rebooting, check if the setting is applied:
cat /sys/power/mem_sleep
The output should show:
s2idle [deep]
The deep option should be in brackets ([deep]), indicating that it is the active sleep mode.
Mine seems to be working fine now, but I don’t know if this “fix” will also get wiped out by the next kernel update? Maybe more knowledgeable admin types on here will be able to tell me if that’s the case or that this was a bad idea!? Hope this might help.