Did you contact TUXEDO Support Centre?
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
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 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
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?
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.
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!
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.
What's your hardware? And did you regenerate grub's config after editing the file you mentioned?
load more comments
(17 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.
load more comments
(4 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.
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
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.
Well, I updated the BIOS - no change so far. I guess I'm stuck without Sleep. :/
You are not alone. There are many laptops that don't work with sleep on Linux. I used to have one of them, a Dell 3150. I simply disabled sleep in bios, and be done with it. I now buy laptops that I know they work 100% with Linux. It's impossible for Linux to support every hardware in the world, when these are specifically are made for Windows.
I have it too now with KDE. Seems like something new
I'm curious, did you dig around the BIOS/UEFI to see if there are any ACPI power states that can be disabled?
I had a very similar issue and turning off S3 worked around it. Of course, that meant higher power usage during sleep but it was a compromise over buying new hardware.
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
load more comments
(10 replies)
view more: next ›