I read how most laptop vendors nowadays force S0ix (Modern Standby). You can no longer pick S3.

On Linux the names for these policies in the kernel are:

  • deep, aka the S3 sleep or suspend to ram

  • s2idle, aka the new Modern Standby or S0ix or suspend to idle.

I am thinking of getting the new Framework laptop, but after talking with their CS, they mention that all Framework will run on S0ix and will not support S3 sleep.

There was a video of LTT bashing S0ix/Modern Standby years ago and he was correct. I had a Thinkpad and it defaulted to S0ix: resume and suspend were very unpredictable. Luckily that laptop also supports S3 so i can just switch to it.

Is resume / suspend getting better on Linux with this forced S0ix? Or i better hold on to an old laptop with S3 lol?

BTW, those with Framework, is resume/suspend reliable? Almost Mac like?

  • treadful@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 hour ago

    I’m running an OG Framework Laptop 13. s2idle works just fine, but it looks like S3 is also supported (this may not be the case for all their systems, of course).

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

    Honestly, I haven’t given it much thought. I just have my idle program run systemctl suspend and that’s that.

  • Dultas@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    My Thinkpad only supports s2idle (checked the bios no way to turn on s3). It truly sucks, the laptop won’t go 8 hours on idle without the battery dying. I used the amd-s2idle tester and it said the laptop was going to idle after 10 minutes but that was not reflected in real world use. Even after turning off every wakeup except the power button to prevent premature wakeup from wifi USB etc.

    My only solution was to re-enabling hibernate. It’s slower and takes disk space but it works. Laptop can go days on hibernate with no issue.

  • Eggymatrix@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    Honestly I usually don’t use either sleep or any suspensions. I prefer to turn the device off, since turning it on will take less than 20 seconds anyway.

    It was also a lot less supported some time ago so that is the reason I avoided it originally.

    I feel like these weird sleep things are some windows heritage to avoid reboot updates and edge browser queries or whatever other crap flies over there.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    arrow-up
    5
    ·
    4 hours ago

    S0ix is fine. LTT doesn’t know shit about shit. I use it on first gen Framework. It works way more reliably than S3 since there’s little nees for special handling in drivers and firmware. The Framework already consumes 3W when idle. S0ix brings that down to 1-2W. The first gen suppprts S3 and that doesn’t consume less power. So either way I need suspend-then-hibernate or suspend-to-both and that’s what you want as well. You’d have to forgo Secure Boot to enable hibernate. If root is on Ext4 on encrypted LVM, hibernate works even with a swapfile (default on modern Ubuntu). For fancier setups like root on ZFS you’d need to use encrypred swap partition for it. That’s what I currently use. If you want to know more details, have Qs, ask away.

  • UnLocoPoco@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    12 hours ago

    Fair point. Even my asus zenbook 2025 around 20% of times when I close my lid, it goes to hibernation and asus Software notifies that due to system not going to sleep within time, it was forced to go into hibernate. In Linux, forcing might work for s3 but u need to test out wirh everything. Else it’ll be stuck in between. Do you have a system currently which is comparable to framework specs? Yes I know they have much better out of the box suppoet for Linux but in this way you can test out you main Hardware for support. Try a live boot on a system and then check.

  • anon5621@lemmy.ml
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    edit-2
    5 hours ago

    Even if u force s3 with kernel ur hardware on uefi level will not handle it properly and change that it will not go deep sleep or stay somewhere in middle of getting sleep with big chance u will get just black screen and u will have to reboot in the end. I am sorry s3 is really dead

  • kylian0087@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    7
    ·
    15 hours ago

    So i have not used a laptop with linux for quite some time. Only desktop and servers for the most part.

    Recently however, I setup a dell XPS17 with opensuse Tumbleweed. This works great but I did run in to the issue initially that when using LUKS full disk encryption in combination with secure boot it disables the ability for hybernation. Something the due with kernel lockdown.

    The solution was to not use secure boot and that allows the laptop to hybernate even with LUKS.

    Something to keep in mind when setting up a laptop.

  • adeoxymus@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    15 hours ago

    I’m also interested in this. In my old xps 13 the s0 was very buggy. Would be a shame if you can’t switch to s3 at all. I thought it was a limitation of the x86 architecture actually?

    • Dultas@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 hours ago

      More and more are dropping s3. My Thinkpad doesn’t have it and I think some framework might be s2idle only.

    • njordomir@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      12 hours ago

      I had a similar experience with the XPS 13, which is odd because Dell explicitly supported Linux on this laptop. It was a good device and ran well for at least a decade.

      • whoiswrongwithyou@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        edit-2
        4 hours ago

        That’s what the landscape of sleep is like.

        E: The just read the thread and at this moment half the responses are some variation of “yeah I tried a bunch of stuff and it doesn’t work” and the other half are “it works perfectly for my precise state definition on this particular piece of hardware”. My comment is 100% correct and useful information about the state of sleep in Linux at the moment.

        Not everything is a fight. Consider reading people’s comments and posts in the voice of miss rachel or something.