Hi Fottach,
Suspend should work without any problem, we will try to find out what happened.

Please check what BIOS and EC version you have installed and let us know:
https://slimbook.com/en/blog/guides-2/post/how-to-check-if-your-slimbook-has-the-latest-bios-and-ec-version-392

The latest BIOS 1.14GOS02 and EC 2.07 are here:
https://slimbook.com/downloads?ruta=Evo/Ryzen-8845HS/BIOS/

But I also inform you that a new version will be released this week. It would be interesting to know before if your problem occurs with the current version.

On the other hand, it could also happen due to a component, such as the wifi card, the ram memory, or the hard drive. I cannot locate any order with your current user account, please provide us with your order number to check the assembled components.

Regards,

Hi Alejandro,

thank you on quick reply.
I was not patient, so now I'm back on freshly installed Slimbook OS. :)

Updated BIOS few days ago, as I saw that in Downloads section:

Evo_AMD8845HS_BIOS_N.1.14GOS02_EC_2.07.00.000.zip
Size: 17.22 MB
Last modified: Tue. January 7th, 2025 - 01:25pm

So, current version is

 boris    sudo dmidecode -s bios-version
N.1.14GOS02

I opened account as private, however, this is company laptop. "2e Systems" ordered 2 laptops on 08.11.2024.  and as I understood we just ordered 2 more. I can get order number for this one on Monday.

----------
EDIT: order number is S21261


Regards,
Boris

Good afternoon,

I see that you have installed kernel 6.8.0-51-generic.
Please install the following kernel and check how it works on your computer. We have tested it and it works for us.

sudo apt install linux-oem-24.04b
reboot

Kind regards,

Hello Eusebio,

I wrote in my previous post, I was impatient so I reinstalled original Slimbook OS.
So, OS and kernel are now:

root@boris-evo14a8:/var/log# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Slimbook OS
Release:        24.0
Codename:       noble
root@boris-evo14a8:/var/log# uname -r
6.11.0-1011-oem

An, I just tried suspend mode trough Fn-F1 combination, it woke up from suspend in just a few seconds.
These looks like most interesting parts of the syslog:

2025-01-20T15:03:13.667511+01:00 boris-evo14a8 kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
2025-01-20T15:03:13.667538+01:00 boris-evo14a8 kernel: atkbd serio0: Use 'setkeycodes e078 <keycode>' to make it known.
2025-01-20T15:03:14.493246+01:00 boris-evo14a8 wpa_supplicant[925]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-60 noise=9999 txrate=6000
2025-01-20T15:03:14.588845+01:00 boris-evo14a8 ModemManager[1002]: <msg> [sleep-monitor-systemd] system is about to suspend
2025-01-20T15:03:14.592584+01:00 boris-evo14a8 dbus-daemon[847]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=922 comm="/usr/sbin/NetworkManager --no-daemon" label="unconfined")
...
2025-01-20T15:03:15.678361+01:00 boris-evo14a8 systemd[1]: Reached target sleep.target - Sleep.
2025-01-20T15:03:15.699699+01:00 boris-evo14a8 systemd[1]: Starting systemd-suspend.service - System Suspend...
2025-01-20T15:03:15.711412+01:00 boris-evo14a8 systemd-sleep[6076]: storing slimbook configuration:0
2025-01-20T15:03:15.713704+01:00 boris-evo14a8 systemd-sleep[6071]: Performing sleep operation 'suspend'...
2025-01-20T15:03:15.713917+01:00 boris-evo14a8 kernel: PM: suspend entry (s2idle)
2025-01-20T15:03:15.720921+01:00 boris-evo14a8 kernel: Filesystems sync: 0.007 seconds
2025-01-20T15:03:21.325514+01:00 boris-evo14a8 kernel: Freezing user space processes
2025-01-20T15:03:21.325826+01:00 boris-evo14a8 kernel: Freezing user space processes completed (elapsed 0.002 seconds)
2025-01-20T15:03:21.325838+01:00 boris-evo14a8 kernel: OOM killer disabled.
...
2025-01-20T15:03:21.325884+01:00 boris-evo14a8 kernel: fxpm, fxgmac_suspend callout to sleep
2025-01-20T15:03:21.325885+01:00 boris-evo14a8 kernel: ACPI: EC: interrupt blocked
2025-01-20T15:03:21.325886+01:00 boris-evo14a8 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.ACDC.RTAC], AE_NOT_FOUND (20240322/psargs-330)
2025-01-20T15:03:21.325887+01:00 boris-evo14a8 kernel: 
2025-01-20T15:03:21.325888+01:00 boris-evo14a8 kernel: 
2025-01-20T15:03:21.325892+01:00 boris-evo14a8 kernel: Initialized Local Variables for Method [_DSM]:
2025-01-20T15:03:21.325893+01:00 boris-evo14a8 kernel:   Local0: 00000000d2f4aa98 <Obj>           Integer 0000000000000001
2025-01-20T15:03:21.325894+01:00 boris-evo14a8 kernel: 
2025-01-20T15:03:21.325895+01:00 boris-evo14a8 kernel: Initialized Arguments for Method [_DSM]:  (4 arguments defined for method invocation)
2025-01-20T15:03:21.325896+01:00 boris-evo14a8 kernel:   Arg0:   0000000038aa27c1 <Obj>           Buffer(16) 56 0D E0 11 64 CE CE 47
2025-01-20T15:03:21.325897+01:00 boris-evo14a8 kernel:   Arg1:   000000009d8ceb70 <Obj>           Integer 0000000000000000
2025-01-20T15:03:21.325897+01:00 boris-evo14a8 kernel:   Arg2:   00000000bc0c03c2 <Obj>           Integer 0000000000000004
2025-01-20T15:03:21.325919+01:00 boris-evo14a8 kernel:   Arg3:   0000000001ce62ce <Obj>           Package 0000000001ce62ce
2025-01-20T15:03:21.325920+01:00 boris-evo14a8 kernel: 
2025-01-20T15:03:21.325922+01:00 boris-evo14a8 kernel: ACPI Error: Aborting method \_SB.PEP._DSM due to previous error (AE_NOT_FOUND) (20240322/psparse-529)
2025-01-20T15:03:21.325923+01:00 boris-evo14a8 kernel: ACPI: EC: interrupt unblocked
2025-01-20T15:03:21.325924+01:00 boris-evo14a8 kernel: fxpm, fxgmac_resume callin
2025-01-20T15:03:21.325926+01:00 boris-evo14a8 kernel: nvme nvme0: D3 entry latency set to 10 seconds
2025-01-20T15:03:21.325927+01:00 boris-evo14a8 kernel: [drm] PCIE GART of 512M enabled (table at 0x000000801FD00000).
2025-01-20T15:03:21.325928+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: SMU is resuming...
2025-01-20T15:03:21.325930+01:00 boris-evo14a8 kernel: fxgmac_net_powerup callin
2025-01-20T15:03:21.325932+01:00 boris-evo14a8 kernel: fxgmac start callin here.
2025-01-20T15:03:21.325933+01:00 boris-evo14a8 kernel: CHIP_RESET 0x80000001
2025-01-20T15:03:21.325934+01:00 boris-evo14a8 kernel: nvme nvme0: 16/0/0 default/read/poll queues
2025-01-20T15:03:21.325936+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: SMU is resumed successfully!
2025-01-20T15:03:21.325937+01:00 boris-evo14a8 kernel: fxgmac_write_ephy_reg id 16,  ok,  ctrl=0x08100204,  data=0x0000006a
2025-01-20T15:03:21.325939+01:00 boris-evo14a8 kernel: fxgmac_write_ephy_reg id 30,  ok,  ctrl=0x081e0204,  data=0x00000052
...
2025-01-20T15:03:21.326097+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
2025-01-20T15:03:21.326098+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
2025-01-20T15:03:21.326099+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
2025-01-20T15:03:21.326101+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
2025-01-20T15:03:21.326102+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
2025-01-20T15:03:21.326103+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
2025-01-20T15:03:21.326104+01:00 boris-evo14a8 kernel: amdgpu 0000:65:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
2025-01-20T15:03:21.326105+01:00 boris-evo14a8 kernel: [drm] ring gfx_32776.1.1 was added
2025-01-20T15:03:21.326106+01:00 boris-evo14a8 kernel: [drm] ring compute_32776.2.2 was added
2025-01-20T15:03:21.326107+01:00 boris-evo14a8 kernel: [drm] ring sdma_32776.3.3 was added
2025-01-20T15:03:21.326108+01:00 boris-evo14a8 kernel: [drm] ring gfx_32776.1.1 ib test pass
2025-01-20T15:03:21.326109+01:00 boris-evo14a8 kernel: [drm] ring compute_32776.2.2 ib test pass
2025-01-20T15:03:21.326110+01:00 boris-evo14a8 kernel: [drm] ring sdma_32776.3.3 ib test pass
2025-01-20T15:03:21.326111+01:00 boris-evo14a8 kernel: OOM killer enabled.
2025-01-20T15:03:21.327836+01:00 boris-evo14a8 kernel: Restarting tasks ... done.
2025-01-20T15:03:21.327847+01:00 boris-evo14a8 kernel: random: crng reseeded on system resumption
2025-01-20T15:03:21.334552+01:00 boris-evo14a8 systemd-resolved[816]: Clock change detected. Flushing caches.
2025-01-20T15:03:21.334842+01:00 boris-evo14a8 gnome-shell[2186]: no authentication service is enabled, using password authentication
2025-01-20T15:03:21.337014+01:00 boris-evo14a8 systemd-sleep[6071]: System returned from sleep operation 'suspend'.
2025-01-20T15:03:21.337314+01:00 boris-evo14a8 bluetoothd[846]: Controller resume with wake event 0x0
2025-01-20T15:03:21.337845+01:00 boris-evo14a8 kernel: PM: suspend exit
2025-01-20T15:03:21.342114+01:00 boris-evo14a8 systemd-sleep[6160]: loading slimbook configuration:0
2025-01-20T15:03:21.348567+01:00 boris-evo14a8 gnome-shell[2186]: no authentication service is enabled, using password authentication
2025-01-20T15:03:21.364697+01:00 boris-evo14a8 rtkit-daemon[1350]: Successfully made thread 2215 of process 2186 owned by '1000' high priority at nice level 0.
2025-01-20T15:03:21.364859+01:00 boris-evo14a8 rtkit-daemon[1350]: Supervising 9 threads of 6 processes of 1 users.
2025-01-20T15:03:21.369866+01:00 boris-evo14a8 rtkit-daemon[1350]: Supervising 8 threads of 5 processes of 1 users.
2025-01-20T15:03:21.370756+01:00 boris-evo14a8 rtkit-daemon[1350]: Supervising 8 threads of 5 processes of 1 users.
2025-01-20T15:03:21.371015+01:00 boris-evo14a8 systemd[1]: systemd-suspend.service: Deactivated successfully.
2025-01-20T15:03:21.371416+01:00 boris-evo14a8 systemd[1]: Finished systemd-suspend.service - System Suspend.
2025-01-20T15:03:21.372186+01:00 boris-evo14a8 systemd[1]: Stopped target sleep.target - Sleep.
2025-01-20T15:03:21.372264+01:00 boris-evo14a8 systemd[1]: Reached target suspend.target - Suspend.
2025-01-20T15:03:21.373486+01:00 boris-evo14a8 ModemManager[1002]: <msg> [sleep-monitor-systemd] system is resuming

I will provide more info as needed, of course.

Regards,
Boris

Additional note:
it seems that first suspend after power-on, works fine, but laptop wakes up quickly after any additional attempt to put it in sleep mode.

Good morning,

We are still investigating the problem, since for example in Linux Mint it doesn't happen.
In the meantime, you can test this parameter in the grub (mem_sleep_default=deep)
sudo nano /etc/default/grub
Edit the line:
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash” to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep”
Save and exit
sudo update-grub
reboot

Kind regards,

Hi Eusebio,

thank you, I applied the changes in GRUB as suggested, and it seems it helped.
I'm on Slimbook OS now and several suspend tests so far were successful.

I'll keep an eye on this in next few days, but hopefully this issue is resolved.

Thanks and best regards,
Boris

Hi Slimbook,

(sorry I cannot to use "Comment" option as it requires too much karma)

It is quite interesting, previously it was asked and said that Slimbook doesn't support ACPI S3 (aka Suspend to RAM, aka deep) mode but nevertheless does this "mem_sleep_default=deep" proves that it does? (So far what I see that this can be used only if it is supported)

Can I ask what do these return:
#cat /sys/power/mem_sleep
#dmesg | grep -i supports | grep -i acpi

-Eugene

Hi Eugene,
last night I left laptop in sleep mode for 12 hours and battery drained about 8%.

Here are  command results you asked for:

$ cat /sys/power/mem_sleep
s2idle
$ sudo dmesg | grep -i supports | grep -i acpi
[    0.265863] ACPI: USB4 _OSC: OS supports USB3+ DisplayPort+ PCIe+ XDomain+
[    0.269961] ACPI: PM: (supports S0 S4 S5)
[    0.306565] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI EDR HPX-Type3]

Thank you very much, so it doesn't support S3/deep, it is weird that it helped, something else is changed or kernel behaves differently in s2idle if deep is specified, interestingly that s2idle isn't in brackets how supposedly should be default used mode, how in my system for example (not a Slimbook, or it thinks that with the only one mode available it doesn't make sense use them).

# cat /sys/power/mem_sleep
s2idle [deep]

I've briefly checked Kernel sources and see that even with one mode available it should be in brackets, like [s2idle]
Picture isn't completely clear but most likely Kernel doesn't contain enough checks to ignore "mem_sleep_default=deep" if isn't supported so set internal variables to "deep" but "cat /sys/power/mem_sleep" doesn't show default/current mode as it isn't in supported list.
Why it solved problem is a mystery or a lucky glitch that something works in a way that it isn't supposed to work (and shouldn't be suggested to try as must do nothing in not supported configuration).

If it works it can be probably fine for now but in general it would be a good idea to ask Kernel developers about this (I want to believe that Slimbook can do that).
Regarding original problem I did faced similar problem once (on different configuration) and spent not small amount of time to find workaround (without clear understanding who is guilty - hardware, firmware or software).

I don't keep used links but to just briefly mention, just in case, it was needed to enable /sys/power/pm_trace (and various ACPI traces), check /sys/power/pm_wakeup_irq and corresponding /proc/acpi/wakeup & /proc/interrupts to see that in my case instant wake up was triggered by pinctrl_amd/AMDI0030...

Hello to all,

I wanted to update the situation. The dev team is still investigating the issue. 

Best regards.

Hello Vaja,

Thank you for the update.
Since adding the "mem_sleep_default=deep" parameter, I haven't experienced any issues with suspend behavior and have stopped tweaking it. ;)
Anyway, I'm here in case you need any additional information.

Best regards,
Boris

Hi

I have the same problem and am using the same wokaround. It's working for me too.

I've checked this around again (out of curiosity) and haven't found any ways how directly it can work when clearly isn't supposed/expected to work when not supported.
But then I started to check indirect ways and saw that actually it can affect Keyboard initialization
https://github.com/torvalds/linux/blob/8f6629c004b193d23612641c3607e785819e97ab/drivers/input/serio/i8042.c#L424
So by default it will try to device_set_wakeup_enable() but with "mem_sleep_default=deep" it won't as pm_suspend_default_s2idle() will return false as it points to "deep" (even if deep isn't actually supported and won't work anyway as it depends on a "hardware/firmware" layer)

and then I started to check around keyboard configurations and issues and finally found very similar with "quirk" applied for the Framework laptop.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/platform/x86/amd/pmc/pmc-quirks.c?id=a55bdad5dfd1efd4ed9ffe518897a21ca8e4e193
(additional link with discussion about probably exactly the same problem - https://www.reddit.com/r/framework/comments/19bf3ki/linux_suspend_and_amd_reminder/)

I'm having what appears to be very similar to what is described here, but:

1) suspends properly until it doesn't, and never does again until a poweroff (reboot isn't enough)

2) when it doesn't suspend, it also doesn't even detect the charger properly (behaviour observed also in UEFI, so it's not just an OS issue)

3) although lspci shows an ethernet controller, no ethernet card is detected (it's like I have none, when the issue happens or not).

I believe it's a hardware/firmware issue and not an OS issue.

Hi Slimbook,

Regarding “Fix Sleep Issues on Linux” (https://slimbook.com/en/blog/guides-2/post/fix-sleep-issues-on-linux-448)

Of course I’m 3rd person here but I’m third exactly because of Slimbook decided to not support "deep sleep" (and I decided to not buy it) and now you are making statement This tweak configures the system to use "deep sleep," that you can just simply enable it by mem_sleep_default=deep" that for me seems complete misinformation/rubbish (even if it solves problem but for other reasons that I tried to "hint" here).

Clearly ACPI S3 is still not supported, here we can see that system uses “PM: suspend entry (s2idle)”, with the statement above could Slimbook confirm that with mem_sleep_default=deep we may expect “PM: suspend entry (deep)” (as in my system with S3/deep support)

if not could you be more precise with explanations of what described changes do or persons like me can see that and want to buy it again because it can do normal deep sleep when it doesn't.

Hello SWAN_UA,  

We have attempted to force the implementation of S3 (in fact, I just tested it, and it does not recover from suspension). AMD 8845HS processor (and any modern CPU) does not support S3. It is deprecated and is being replaced by Modern Standby.  

Now, why does the `mem_sleep_default=deep` parameter work? It optimizes `s2idle` to allow the system to enter a deeper sleep state. AMD Ryzen and modern platforms exclusively use `s2idle` because S3 is not supported. In many cases, `s2idle` in its default configuration allows multiple devices (USB, PCIe, network, etc.) to wake up the system with any activity. The `mem_sleep_default=deep` parameter optimizes `s2idle`, ensuring the system enters a deeper sleep state by disabling some unnecessary wake-up events.  

Unfortunately, you will have to forget about S3 support on ALL modern laptops, not just Slimbook. This is not a decision made by laptop manufacturers but by processor manufacturers, over which we have little to no control.  

Best regards.

“Funny” thing, the first thing that I faced on a “Modern Standby” only laptop was exactly “it does not recover from suspension”.
Regarding “AMD Ryzen and modern platforms exclusively use `s2idle` because S3 is not supported”  - my latest AMD Ryzen 9700X on X670E supports it fine (not a laptop though but pretty latest). Also I tried really hard and haven’t found any document/standard with that statement so still think/suppose that manufactures silently decided that (maybe under pressure of MS and/or Intel, just a lot of gossips).
Also it is still possible to find a laptop with S3 support.

By the code I haven’t seen that “mem_sleep_default=deep” optimizes “s2idle” it is just a bug that it works, in this case it is a lucky bug that can be exploited in a GOOD way but without any intention to optimize s2idle or to be used in this mode (another affected area can be in AHCI SATA usage but probably in laptop case it should be unaffected).

While I don’t want to accuse Slimbook with anything and do believe and not everything directly depends on you, here I’m just trying to emphasize that things should be as clear as possible, you cannot say that it you can put system in deep while deep is not supported (or say that it will optimize anything if there is no such statement from the Kernel), it is just workaround that can be exploited so far, until more permanent and proper solution is developed, for a "spurious" keypresses as for this case….

Don't be unsted, tuxedo also told me that modern laptops don't support S3, and I'm going to believe what people who talk to the manufacturer say before someone who doesn't have a laptop, but rather a desktop with a completely different architecture.
My company bought a tuxedo laptop, and in recent months I've found more help on the slimbook forum than in tuxedo's support department, and other reddit users have told me the same thing.
I don't understand how users like SWAN_UA, who don't seem to own a slimbook laptop, waste time criticizing, unless they get something out of it.

Viva Slimbook <3

To clarify things:
- there is no questions about quality of support - it is good and fair enough (as for me and yes better than some others).
- there is no question of why S3 isn’t supported by Slimbook, in this topic it is considered as the fact (even if I’d like to discuss and have what to say it is out of topic).
- there is no empty critics and just attempt to to explain/clarify things to not be misleading, as for particular issue there is already link that explains why in particular case “mem_sleep_default=deep” solves the problem, because of this

https://github.com/torvalds/linux/blob/8f6629c004b193d23612641c3607e785819e97ab/drivers/input/serio/i8042.c#L424

    /*
     * On platforms using suspend-to-idle, allow the keyboard to
     * wake up the system from sleep by enabling keyboard wakeups
     * by default.  This is consistent with keyboard wakeup
     * behavior on many platforms using suspend-to-RAM (ACPI S3)
     * by default.
     */
     
ie because of not enough checks in the Kernel this code can be skipped and think that currently ACPI S3 is used and skip corresponding/specific processing as for the s2idle (it may require Kernel with this change as well - https://github.com/torvalds/linux/commit/9bc4ffd32ef8943f5c5a42c9637cfd04771d021b).

so “mem_sleep_default=deep” here isn’t a tweak that configures the system to use "deep sleep" (as published by Slimbook article said) as deep isn't supported and system will still use s2idle and it isn’t specific optimization that can optimize something, it is a bug in mem_sleep_default processing by the Kernel that can be utilized so far to cover other bugs (and may introduce others as system mislead itself with this setting in provided configuration).

...

Hello SWAN_UA,

I understand your concerns, and I appreciate your detailed response.

You're absolutely right that mem_sleep_default=deep does not enable a true "deep sleep" mode, as s2idle remains the only available state. Instead, the observed effect is due to how the kernel handles suspend behavior.

I fully agree that transparency is essential. The goal is not to claim deep sleep support where none exists but rather to share practical solutions that enhance the user experience within the constraints of current hardware and software. If a more robust solution becomes available in the future, it would certainly be preferable.

I'll review how this information is communicated to ensure there is no potential misunderstanding. Your input is genuinely valuable, and I appreciate the constructive discussion.

Regarding S3 support, while it's true that some desktop platforms (such as the Ryzen 9700X on X670E) may still support S3, modern laptops have almost entirely transitioned to Modern Standby, with s2idle as the primary sleep state. Whether this shift was purely a technical decision or influenced by external factors (such as Microsoft or Intel) is difficult to say with certainty. However, the trend across all recent laptop models clearly indicates a move away from S3. If you’re aware of any manufacturer that still supports S3 by default on modern hardware, feel free to share that information.

Best regards.

While it is difficult to say in a generic way about S3 support it is just because manufactures/vendors don’t provide that information in specs but if asked (what I did):
- I had confirmation that AMD based StarFighter laptop supports S3 (configuration seems not changed since so I suppose it is still true)
- I had confirmation that System76 Darter Pro with CoreBoot supports it (but not Pangolin that isn’t CoreBoot)
- NovaCustom seems had statement at some point that S3 isn’t supported but now they say - The laptop only supports modern standby (S0ix) for Windows and Linux. It might support S3 suspend mode (iGPU without NVIDIA only), but has to be forced. Qubes OS S3 suspending works out-of-the-box.
- There are a lot of confusing information about Lenovo, they clearly played with disabling S3 as well but may still have that option in BIOS and I had confirmation about one particular model based on AMD 6000 some time ago that it supports S3 (BTW Tuxedo says that 6000 doesn’t support it).
- There is still an option with modifying DSDT (search for “DSDT s3 enable”) that may work if confirmed or you a lucky...
- ...

Wow, modern standby have 13 years old!

Major manufacturers like Asus, Dell, and MSI announced this several years ago.

https://www.dell.com/support/kbdoc/en-ck/000177661/what-is-modern-standby-and-how-does-it-differ-from-s3-standby

https://au.msi.com/blog/why-modern-standby-matters-for-business-laptop

https://www.asus.com/me-en/support/faq/1035447/