• Lucy :3@feddit.org
    link
    fedilink
    arrow-up
    17
    ·
    1 day ago

    I’m always so amused when people are like “Uhm, actually, when you shutdown your PC it’s not turned off, it’s sleeping so it ca…” - Bro, no. sudo poweroff. It’s off. Completely off. In fact, it would be hella annoying and fucking useless to configure sleeping.

      • Lucy :3@feddit.org
        link
        fedilink
        arrow-up
        2
        ·
        1 day ago

        Depends on which suspend tho. iirc there’s one system that’s forcefully being discontinued by big corpo, while the replacement is still very buggy everywhere.

        • muhyb@programming.devOP
          link
          fedilink
          arrow-up
          5
          ·
          1 day ago

          Hmm, do you remember which one was it? Personally I never had problems with systemctl suspend or loginctl suspend.

          • Lucy :3@feddit.org
            link
            fedilink
            arrow-up
            7
            ·
            edit-2
            1 day ago

            Found it. AW article

            It’s called S0ix/Modern Standby/s2idle. It was designed to replace S3, but not only is it shit on Winshit and kekOS, it’s also very unreliable on Linux in my experience. The true issue it that manufacturers started to discontinue S3 (so shallow/standby and deep/s2ram) in favor of s2idle. You can check which actions are theoretically possible in the kernel docs, and check which are supported on your system (and enabled) by cat-ing /sys/power/mem_sleep. That’s what systemctl suspend chooses. My PC and Server still have deep, but my Laptop already only has s2idle.