Linux

52683 readers

810 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Tuxedo OS (Ubuntu-based) with KDE/Wayland - waking from Sleep freezes the computer. Help? (lemm.ee)

submitted 2 days ago* (last edited 1 day ago) by [email protected] to c/[email protected]

79 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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 2 days 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

[–] [email protected] 4 points 2 days 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....

[–] [email protected] 2 points 1 day 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

[–] [email protected] 1 points 1 day ago (1 children)

So, I did a BIOS update, as advised here, and got some interesting results!

The freeze still happens - but it now freezes BEFORE the PC shuts down.

As in: I click the Sleep button, all devices get disconnected (audio, network, BT, input - all of it goes), the OS freezes, but the screens stay on. I cannot switch to a different VT at this point as everything is disconnected.

[–] [email protected] 2 points 1 day ago

here is the low-level documentation on sleep on linux, and the ways you can initiate it: https://docs.kernel.org/admin-guide/pm/sleep-states.html#standby

I would try if setting mem_sleep to any of its values and then sleeping fixes the issue. read this file first to know which options are available on your system, and what is the current default.
if none of them works, try to write freeze or standby into the state file to see of any of them works, in case your system does not do sleeping by writing mem into this file.

if this is a firmware issue, hopefully one of the ways that don't involve the firmware could work until a better solution is found.

the Arch Wiki has mostly the same info but with more (or different) details: https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate

it also mentions what are your options if deep sleep (which is real sleep) does not work.

let us know what results you got

load more comments (6 replies)