69
Tuxedo OS (Ubuntu-based) with KDE/Wayland - waking from Sleep freezes the computer. Help? (lemm.ee)
submitted 1 year ago* (last edited 1 year ago) by to c/linux@lemmy.ml
91 comments fedilink hide all child comments
 

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.

top 50 comments

sorted by: hot top controversial new old
[–] 23 points 1 year ago* (5 children)

Not really related to the issue. If I understand correctly, your device isn't bricked, but freezes. A bricked device doesn't boot anymore, a frozen device is unresponsive. Or am I misunderstanding this?

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 3 points 1 year ago

    Yep, not bricked. Just frozen.

    There are two forms of bricked:

    1. hard bricked. This is when a software change (eg, installing a custom firmware) caused the system to fail to boot, and there is no possible way to ever get it to run again.
    2. soft bricked. Where a software change caused the failure to boot but there is a way (eg, reflashing using UART) to recover back to an older version that does boot.

    Both are terms from the Phone modding community (ie, a phone has become as useful as a brick after this update) it's quite hard to actually brick a modern PC.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 13 points 1 year ago (26 children)

    What's your hardware? And did you regenerate grub's config after editing the file you mentioned?

  • permalink
  • fedilink
  • source
  • hideshow 26 child comments
    •
  • [–] [S] 4 points 1 year ago* (25 children)

    Sorry, forgot to mention hardware! Added in an edit now!

    I have a Ryzen 7 7800X3D and no dedicated GPU (yet).

    I ran sudo update-grub after making the changes. That and rebooting a bunch of times since.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 25 child comments
    •
  • [–] 4 points 1 year ago (21 children)

    Did you try any other distro or Windows on this system to narrow down the issue to Tuxedo OS itself? It could be an issue with your motherboard.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 21 child comments
    •
    • load more comments (6 replies)
    • load more comments (3 replies)
    • [–] 10 points 1 year ago (4 children)

    It might be due to https://github.com/systemd/systemd/issues/33083.

    Try disabling user session freezing when sleeping:

    sudo systemctl edit systemd-suspend.service

    Add the following to the file:

    [Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"

    Reload systemd:

    sudo systemctl daemon-reload

    After that, try sleeping and waking again.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
    load more comments (4 replies)
    [–] 6 points 1 year ago (10 children)

    I would try:

    • see if you can get logs of the resume process
    • suspend from a text VT and see if that changes the behaviour
    • boot into single user mode and try suspend from there
    • boot an older LTS or a newer test kernel and see if it has the same problem
  • permalink
  • fedilink
  • source
  • hideshow 10 child comments
    •
  • [–] [S] 4 points 1 year ago (9 children)

    Sorry, mate, I'm a Linux noob.

    I have no clue where to find the logs for this.

    No idea what a VT is.

    Don't know how to boot into single user mode....

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 2 points 1 year ago (5 children)

    Fair enough, most of that isn't something a user should have to worry about.

    VT is just Virtual Terminals. You always have one of them active, and in most distros you can switch to others by Ctrl-Alt-F1 through F12. In some distos it's just Alt-F1.

    So if you press Ctrl-Alt-F2 you should be brought to a text login. For crazy historical reasons you may have to either press Ctrl-Alt-F1 or Ctrl-Alt-F7 to get back to your usual graphical session.

    Arch docs for example: https://wiki.archlinux.org/title/Linux_console

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] [S] 1 point 1 year ago*

    OK, I tried that. Ctrl+Alt+F2 gives me a black screen.

    Ctrl+Alt+F1 brings me back to my desktop.

    Ctrl+Alt+F3-F6 all have a text login screen. F7+ don't do anything.

    I was able to grab the journalctl logs. You can find them (and an extra bit about the computer state I was able to get) HERE.

  • permalink
  • fedilink
  • source
  • parent
    • load more comments (4 replies)
  • [–] 2 points 1 year ago (2 children)

    logs are mostly at 2 places.

    kernel logs are read with the dmesg command. use the --follow parameter if you want it to keep printing new messages.
    dmesg does not save logs to disk.

    broader system logs are read with journalctl. use -f for it to keep printing. the journal records kernel messages, but it only shows them when you specifically request it. you can find the param for that in man journalctl.
    the journalctl (journald actually) saves logs to disk. but if you don't/can't shut down the system properly, the last few messages will not be there.

    some system programs log to files in /var/log/, but that's not relevant for now.

    if you switch to a VT as the other user described, you should see a terminal prompt on aback background. log in and run dmesg --follow > some_file, some_file should not be something important that already exists in the current directory. switch to another VT, log in, and run sleep. try to wake up. see if you could have waken up, and if not check the logs you piped to the file, maybe post it here for others to see.

    also, what did you do after setting the deep sleep kernel param? did you rebuild the grub config, and reboot before trying to sleep with it? that change only gets applied if you do those in that order.
    there's an easier way to test different sleep modes temporarily, let me know if it would be useful

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    load more comments (2 replies)
    • [–] 5 points 1 year ago (1 child)

    I'm pretty sure tuxedo support should be able to cover this for you. Its one of the bonuses of buying a Linux laptop.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 3 points 1 year ago (3 children)

    Do you have a Nvidia GPU?

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
    load more comments (3 replies)
    [–] 3 points 1 year ago (1 child)

    Having the same issue on Intel + AMD GPU.

    Arch Linux with newest KDE.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    load more comments (1 reply)
    [–] 3 points 1 year ago (5 children)

    First, update your computer's BIOS/firmware. If that doesn't fix it, then try Arch, or Fedora beta. If the problem exists there too, then it's a kernel issue in general, and it might get fixed in the future. OR, if the computer BIOS is buggy, Linus has been clear that they won't do workarounds for buggy firmwares. In which case, you'd need a new computer that's actually compatible with Linux.

    Most of the computers out there have buggy firmwares that go around for Windows, but Linus has been adamant that he wouldn't do workarounds because they bloat the kernel.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
    load more comments (5 replies)
    [–] 2 points 1 year ago* (4 children)

    Is your root partition encrypted?

    Give the output of lsblk if you could.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 1 year ago (3 children) 
    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
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
    load more comments (3 replies)
    • [–] 2 points 1 year ago (2 children)

    That exact issue is why I stopped using KDE. I never did figure it out.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    load more comments (2 replies)
    [–] 2 points 1 year ago (2 children)

    Did you contact TUXEDO Support Centre?

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    load more comments (2 replies)
    [–] 1 point 1 year ago (1 child)

    @Alaknar Sounds like a bug this developer found and fixed:
    https://nyanpasu64.gitlab.io/blog/amdgpu-sleep-wake-hang/

    Basically the fix should ship with kernel 6.14. I'm on ubuntu 25.04 which runs that kernel, and I haven't seen it since. I was seeing it every once in awhile.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    load more comments (1 reply)
    load more comments
    view more: next ›