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?
this post was submitted on 29 Mar 2025
69 points (94.8% liked)
Linux
52711 readers
457 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.
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.
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!
Did you contact TUXEDO Support Centre?
Haven't had the time yet, but it's on my to-do list. Just not sure if they will support this as I'm running it on my own hardware, not their laptop.
Give it a try. Perhaps they may give you at least a hint.
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.
load more comments
(12 replies)
load more comments
(3 replies)
What kernel version? I had similar issues on similar hardware. These have gone away in more recent kernels though.
6.11.0-109019-tuxedo.
Not the latest, right? I guess I'll wait for an update.
No, but I don't believe I saw the issue until the 6.13.x kernels either
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.
load more comments
(4 replies)
Having the same issue on Intel + AMD GPU.
Arch Linux with newest KDE.
That's interesting! Might be KDE bug then.
Could you try going to System Settings → Screen Locking and de-select "Lock after waking from sleep"? I wonder if you'll get the same result as I'm getting.
Before I updated the BIOS to the latest version, once I woke it up, I'd see the desktop exactly frozen as it was the moment I pressed the "Sleep" button.
Now, after the update, that freeze happens BEFORE the PC goes to sleep - the monitors stay on.
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.
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
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.
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)
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
(4 replies)
That exact issue is why I stopped using KDE. I never did figure it out.
Specs for computer havibg the issue ans how long ago did this happen? Seems like a bug that neexs to be reported and more data for devs the better.
Tried it November of 2024, ended up switching to Mint with Cinnamon, zero issues since.
Dell XPS 8930
i7 9700 (no K)
32GB ram
NVidia RTX 2060
240gb ssd
2tb hdd
view more: next ›