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.

  • Alaknár@lemm.eeOP
    link
    fedilink
    arrow-up
    1
    ·
    3 days ago
    alaknar@HostName:~$ lsblk
    NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
    loop0         7:0    0     4K  1 loop /snap/bare/5
    loop1         7:1    0 104,2M  1 loop /snap/core/17200
    loop2         7:2    0  55,4M  1 loop /snap/core18/2855
    loop3         7:3    0  63,7M  1 loop /snap/core20/2496
    loop4         7:4    0  73,9M  1 loop /snap/core22/1802
    loop5         7:5    0 164,8M  1 loop /snap/gnome-3-28-1804/198
    loop6         7:6    0   516M  1 loop /snap/gnome-42-2204/202
    loop7         7:7    0  91,7M  1 loop /snap/gtk-common-themes/1535
    loop8         7:8    0  10,8M  1 loop /snap/snap-store/1248
    loop9         7:9    0  44,4M  1 loop /snap/snapd/23771
    nvme1n1     259:0    0 931,5G  0 disk 
    ├─nvme1n1p1 259:1    0   300M  0 part /boot/efi
    └─nvme1n1p2 259:2    0 931,2G  0 part /
    nvme0n1     259:3    0   1,8T  0 disk 
    └─nvme0n1p1 259:4    0   1,8T  0 part /media/alaknar/BigStorage
    
    • just_another_person@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      3 days ago

      I’m not seeing any swap space, so that could be it. Check this post out.

      It could also be that your BIOS settings for suspend/resume aren’t set to something compatible with your existing config as well though, if the above doesn’t work, or you’re not comfortable with that level of interaction, check your BIOS first, then try the above maybe.

      • Alaknár@lemm.eeOP
        link
        fedilink
        arrow-up
        1
        ·
        3 days ago

        Everything worked fine on Windows - wouldn’t BIOS misconfiguration also cause problems there?