I was running KDE Neon on ThinkBook 15 G2 and had deep sleep working after adding mem_sleep_default=deep to GRUB_CMDLINE. It worked for a while until it didn’t. I didn’t do anything other than running regulat updates. Since couple weeks back, when going to sleep, it shows BIOS Recovery progress bar or something and restarts.

I switched to Debian and the behavior is the same. S2 sleep is next to useless as it drains something like 10% battery / hour, and the lap top is warm to touch.

  • Aurix@lemmy.world
    link
    fedilink
    arrow-up
    45
    arrow-down
    1
    ·
    9 months ago

    Yeah, my sleep schedule is pretty bad since the holiday… Oh, Oooooh.

  • fxdave@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    9 months ago

    You still had deep sleep until now? Lucky you. To me Dell forbided S3 way earlier.

  • stepanzak@iusearchlinux.fyi
    link
    fedilink
    arrow-up
    3
    ·
    9 months ago

    Is deep sleep the same thing as hibernation? Hibernation is broken for me even on new EndeavourOS install on two different laptops.

    • Tushta@programming.devOP
      link
      fedilink
      arrow-up
      3
      ·
      9 months ago

      No, hibernation saves state to disk, and turns the computer off, drawing no power. Deep sleep is what was for me just sleep until recently: it uses power to keep data in ram, so it’s faster to wake up than hibernation. The amount of power used is really small, so unless you don’t use your lap top for a couple of days, it won’t deplete the battery. New hardware has this new “S2 Idle” state, that is basically an “On” state minus the screen and it’s OS’s job to try to use as little power as possible usually by telling each and every device to chill as much as possible (this is my understanding, but don’t quote me on this). On Windows, with the first party device drivers, this sorta works OK + OS drops to deep sleep or hibernation depending on battery or something.

  • skillissuer@discuss.tchncs.de
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    9 months ago

    have you updated EFI/BIOS recently? maybe S3 sleep is not supported on your system anymore and instead you get suspend-to-idle as S0ix (Modern Standby) notoriously shitty under linux. sometimes you can flip it back in EFI/BIOS

    • Tushta@programming.devOP
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      I have a Windows dual boot, and Windows did install some updates, and Lenovo site indicates that the latest BIOS version was released mid November, so that could be it.