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.

  • Corngood@lemmy.ml
    2·
    3 days ago

    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

    • Alaknár@lemm.eeOP
      1·
      2 days 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.

    • catloaf@lemm.eeEnglish
      1·
      3 days ago

      What are the crazy historical reasons? As far as I know, running six ttys and one graphical session, in that order, has been standard.

      The really crazy historical way to test for crashes is num/scroll/caps lock. That’s handled by a very low-level kernel driver. If those are responsive, it’s probably just your display (gpu, X, wayland, or something) that’s locked up. If they’re unresponsive, your kernel is locked up. (If you’re lucky, it’s just gotten real busy and might catch up in a minute, but I’ve only seen that happen once.)

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

        I was able to make some progress in troubleshooting.

        I went to the Screen Locking options and disabled “Lock after waking from sleep”. Now I get to see the screen when I wake the computer back up, frozen as it was when I issued the sleep command.

        All devices are disconnected - no network, no Bluetooth, no audio, all the “tray” icons are greyed out and/or showing errors, time is stopped at the moment I clicked the “Sleep” button.

        Not sure if that helps at all.

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

            No, the keyboard is unresponsive. I also tried Ctrl+Alt+F1…F7, and got absolutely nothing.

            I did a BIOS update, as advised here, and the behaviour changed! Now the freeze happens BEFORE the PC goes to sleep. As in: it gets to the frozen state the moment I click the button and the screens remain on.