this post was submitted on 29 Mar 2025
68 points (94.7% liked)
Linux
52674 readers
579 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What's your hardware? And did you regenerate grub's config after editing the file you mentioned?
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-grubafter making the changes. That and rebooting a bunch of times since.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.
I moved to Tuxedo from Kubuntu after having MASSIVE problems there, but I honestly can't remember if I was using the Sleep feature.
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:
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.logto the command above to output logs to a file, in case that makes copy and pasting easier for you.11:48 - Sleep
11:50 - Wake
11:52 - Reboot
Password to the file:
spoiler
helpm.ee.lemm.eeLog 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.
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:
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.
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.Can you check the system journal (just like before) to see whether there were any logs about it?