Not really related to the issue. If I understand currently, your device isn't bricked, but freezes. A bricked device doesn't boot anymore, a frozen device is unresponsive. Or am I misunderstanding this?
this post was submitted on 29 Mar 2025
67 points (94.7% liked)
Linux
53363 readers
517 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
Came here to say the same thing. Using the term "bricking" in the title had me very confused. It would be catastrophic if this was actually bricking computers.
Yeah, had a brain fart. It's a freeze.
you could edit your post title
Oh, yeah, that's true! Didn't know that's a thing here, good to know!
Yep, not bricked. Just frozen.
There are two forms of bricked:
- 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.
- 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.
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-grub after 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.
Windows worked flawlessly.
Kubuntu had massive issues with other things, but I didn't test Sleep (due to those other issues I only had it for a day or two).
load more comments
(14 replies)
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:
$ journalctl -r -b -1
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.log to 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.ee
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:
mar 30 11:45:37 HostName kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E26/B650 GAMING PLUS WIFI (MS-7E26), BIOS 1.10 05/23/2023
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.
load more comments
(2 replies)
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.
Just tried it now. Does it need a reboot first? As in: should I try again?
As long as you ran systemctl daemon-reload, you should be able to try sleeping without needing to reboot.
Would this part potentially get in the way of the method you suggested?
One fairly recent thread had a proposed solution of adding
"mem_sleep_default=deep"toGRUB_CMDLINE_LINUX_DEFAULTin/etc/default/grub.
Should I remove that?
You can leave it.
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
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....
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
load more comments
(2 replies)
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
load more comments
(5 replies)
I'm pretty sure tuxedo support should be able to cover this for you. Its one of the bonuses of buying a Linux laptop.
I'm running it on a desktop PC, so not sure if they'd cover it. But I might poke them about it, good idea.
Do you have a Nvidia GPU?
Sorry, forgot to mention hardware in the OP. I have a Ryzen 7 7800X3D and no dedicated GPU (yet).
load more comments
(2 replies)
Having the same issue on Intel + AMD GPU.
Arch Linux with newest KDE.
load more comments
(1 replies)
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.
load more comments
(5 replies)
That exact issue is why I stopped using KDE. I never did figure it out.
load more comments
(2 replies)
Is your root partition encrypted?
Give the output of lsblk if you could.
load more comments
(4 replies)
@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.
load more comments
(1 replies)
You could try a tool like LACT and setting your gpu power profile to always highest. Another thing you could check is your BIOS settings, https://www.tomshardware.com/reviews/bios-beginners,1126-8.html or checking if the latest bios is installed https://red.artemislena.eu/r/gigabyte/comments/1b3bffy/gigabye_b650_aorus_elite_ax_rev_10_sleeppower/
Hmm... Wouldn't I also have sleep problems on Windows if this was a BIOS issue?
windows may have a workaround for your hardware. It's relatively common for popular hardware to not work according to specifications, unfortunately, and that results in all kinds of mundane behaviour like this
view more: next ›