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.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
@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.
Oh, nice! Thanks for the info!
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?
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:
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).
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.
I would try:
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....
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
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.
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.
Having the same issue on Intel + AMD GPU.
Arch Linux with newest KDE.
That exact issue is why I stopped using KDE. I never did figure it out.
Is your root partition encrypted?
Give the output of lsblk if you could.