Hi all!

I recently installed Tuxedo OS with KDE and Wayland. I’m fairly new to Linux and, so far, the distro is great. With one caveat.

As far as power options go, everything works fine EXCEPT for Sleep. I can put the PC to sleep, but when I wake it up, I land on the login screen wallpaper with the login/password fields barely visible, as if frozen around the second frame of a fade-in animation.

Nothing works. The mouse cursor doesn’t move, the keyboard doesn’t do anything. The only way out of this state is to hold the power button until the PC shuts down and then turn it back on again.

I did some digging, but couldn’t find a solution. Some threads mentioned modifying something in systemd, but those were from years ago, so I didn’t want to risk that.

One fairly recent thread had a proposed solution of adding "mem_sleep_default=deep" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

That didn’t work for me, though.

I’d love to fix this, but I’m out of ideas. Any help welcome!

EDIT

Forgot it might be a driver issue, people were complaining about Nvidia gear!

I currently don’t have a dedicated GPU. I only have Ryzen 7 7800X3D running on MSI B650 Gaming Plus WIFI ATX AM5 MoBo.

  • pogodem0n@lemmy.world
    6·
    3 days ago

    I assume your issue is reproducible every time, right? If yes, do so and reboot. Use the following command to obtain logs from the previous boot, where you had the problem:

    $ journalctl -r -b -1

    Before resuming from sleep, wait for about a minute or so to check for that time gap in the logs to easily find the logs of the resuming process.

    You can append >> file_name.log to the command above to output logs to a file, in case that makes copy and pasting easier for you.

    • Alaknár@lemm.eeOP
      3·
      2 days ago

      11:48 - Sleep

      11:50 - Wake

      11:52 - Reboot

      Password to the file:

      spoiler

      helpm.ee.lemm.ee

      Log file (on Filen.io).

      I noticed something that might be helpful, not sure.

      I was fiddling with settings to see if I can do anything about this on my own. Found the “Screen Locking” settings and disabled “Lock after waking from sleep”. Got some interesting results!

      Nothing changes when I put the device to sleep, but now, when I wake it up, I can see the desktop, as it was when I issued the sleep command. Everything is frozen and all devices are disconnected - no network, no Bluetooth, no audio, all the “tray” icons are greyed out and/or showing errors.

      • pogodem0n@lemmy.world
        3·
        2 days ago

        Thanks.

        Unfortunately, your system printed absolutely no logs when waking up.

        Though, looking at them, I can see that your BIOS is wildly out-of-date:

        mar 30 11:45:37 HostName kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E26/B650 GAMING PLUS WIFI (MS-7E26), BIOS 1.10 05/23/2023

        In fact, it is the one it was shipped with from the factory. First and foremost, you should update it to the latest one available from MSI’s website. Latest one is from a week ago.

        Also, try your best to undo any changes you made to your system following this post, including the grub config change. It is best to troubleshoot making as little change as possible at every step.

        • Alaknár@lemm.eeOP
          1·
          2 days ago

          OK, that was journey… I’m on the latest BIOS version now! Of course I forgot to check ALL the settings before I installed it, so I ended up in a boot loop. All good now, hopefully.

          There IS a behaviour change on the Sleep front - it now never actually goes to sleep, the screen freezes like before, I can see ALL devices getting kicked out, and then nothing more happens.

          Before doing the update I removed the "mem_sleep_default=deep" bit from grub, tested, added it back in, tested again. No change noted.