azorius.net

Tuxedo OS (Ubuntu-based) with KDE/Wayland - waking from Sleep freezes the computer. Help?
from Alaknar@lemm.ee to linux@lemmy.ml on 29 Mar 20:44
https://lemm.ee/post/59831665

Hi all!

I recently installed Tuxedo OS with KDE and Wayland. I’m fairly new to Linux and, so far, the distro is great. With one caveat.

As far as power options go, everything works fine EXCEPT for Sleep. I can put the PC to sleep, but when I wake it up, I land on the login screen wallpaper with the login/password fields barely visible, as if frozen around the second frame of a fade-in animation.

Nothing works. The mouse cursor doesn’t move, the keyboard doesn’t do anything. The only way out of this state is to hold the power button until the PC shuts down and then turn it back on again.

I did some digging, but couldn’t find a solution. Some threads mentioned modifying something in systemd, but those were from years ago, so I didn’t want to risk that.

One fairly recent thread had a proposed solution of adding “mem_sleep_default=deep” to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

That didn’t work for me, though.

I’d love to fix this, but I’m out of ideas. Any help welcome!

EDIT

Forgot it might be a driver issue, people were complaining about Nvidia gear!

I currently don’t have a dedicated GPU. I only have Ryzen 7 7800X3D running on MSI B650 Gaming Plus WIFI ATX AM5 MoBo.

#linux

threaded - newest

Maxy@lemmy.blahaj.zone on 29 Mar 20:52 next collapse

Do you have a Nvidia GPU?

Alaknar@lemm.ee on 29 Mar 21:54 collapse

Sorry, forgot to mention hardware in the OP. I have a Ryzen 7 7800X3D and no dedicated GPU (yet).

ReversalHatchery@beehaw.org on 30 Mar 20:20 collapse

so you use the integrated graphics of the ryzen, right? you can check in KDE’s info center, to make sure

Alaknar@lemm.ee on 30 Mar 20:40 collapse

Don’t need to check, I built the PC myself - it’s currently running on the iGPU from the 7800x3d.

pogodem0n@lemmy.world on 29 Mar 20:59 next collapse

What’s your hardware? And did you regenerate grub’s config after editing the file you mentioned?

Alaknar@lemm.ee on 29 Mar 21:52 collapse

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.

pogodem0n@lemmy.world on 29 Mar 22:15 next collapse

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.

Alaknar@lemm.ee on 29 Mar 23:14 next collapse

I moved to Tuxedo from Kubuntu after having MASSIVE problems there, but I honestly can’t remember if I was using the Sleep feature.

pogodem0n@lemmy.world on 29 Mar 23:38 collapse

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.

Alaknar@lemm.ee on 30 Mar 10:12 collapse

11:48 - Sleep

11:50 - Wake

11:52 - Reboot

Password to the file:

spoiler

helpm.ee.lemm.ee

Log 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.

pogodem0n@lemmy.world on 30 Mar 12:29 collapse

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.

Alaknar@lemm.ee on 30 Mar 15:15 collapse

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.

pogodem0n@lemmy.world on 30 Mar 16:32 collapse

Can you check the system journal (just like before) to see whether there were any logs about it?

Alaknar@lemm.ee on 29 Mar 23:49 collapse

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).

pogodem0n@lemmy.world on 30 Mar 08:22 collapse

Did you nuke your Tuxedo OS install? It would have been better to, at least, have a look at system logs to see if there’s anything there.

What problems exactly did you have with Kubuntu?

Alaknar@lemm.ee on 30 Mar 09:31 collapse

Did you nuke your Tuxedo OS install?

No, I’m still running it. Other than Sleep, everything else works mostly fine. Just the regular “linuxiness” here and there that’s either easy to sort out, or easy to ignore.

What problems exactly did you have with Kubuntu?

Wow, that’s a whole list… :D

On my laptop, I had zero touchpad gestures. Once I switched from X11 to Wayland I managed to get Firefox to handle pinch-to-zoom and forward/back, but nothing else and in no other application.

Bluetooth drivers were crap, made my $300 headphones sound like $10 headphones.

I accidentally set the wrong keyboard language during installation, changed it without any issues after signing in… But to this day that previous layout pops up on the login screen. The only advice I found online required quite heavy Terminal “hacking”… and didn’t work anyway.

Updates are all over the place. They’re coming in constantly, practically every day, often requiring a reboot. It also doesn’t install any updates on its own, so even if there are smaller, security updates that don’t require a reboot, you have to manually click through the notification and apply them. There was supposed to be another “hack” that makes it apply updates automatically, but it doesn’t work.

I recently connected my Linux laptop to an external screen. All good, but… The login screen was displayed on both monitors. I clicked the login field on the external screen, started typing and nothing happened. Fiddled with that for a bit before, just out of curiosity, trying again, but this time fully on the laptop screen. Worked like a charm, zero issues.

That was the laptop. Then on my PC, I suddenly realised that I have not application menu (the one with “File”, “View”, “Edit”, etc.). Just gone. Wasn’t able to restore it.

Also, my secondary SSD would not stay mounted. Any time I rebooted, it was just gone - and that was a problem for me because I had my Steam library there and wanted to have Steam auto-starting on logon. That I was able to fix by editing fstab, but was still super annoying.

The move to Tuxedo OS was very smooth. Almost everything worked out of the box (still had to do the fstab bit), the Bluetoot driver is MUCH better, updates are more controlled. It’s just this bloody Sleep feature that doesn’t work. :D

pogodem0n@lemmy.world on 30 Mar 13:02 collapse

Hmm, let me clarify some of the challenges you had.

Lack of touchpad gestures is due X11. It simply does not support anything you may be used to from Windows or macOS. X11 is currently regarded as a legacy display system due it’s lack of modern features (such as VR, VRR and HDR) and security issues. Firefox supports your typical Wayland gestures since it is one of the few apps implementing new Linux features properly. On Windows and macOS you are locked down to a particular windowing system, so applications can expect such features being available on every single system reliably. The number of choices Linux presents to its users is also the greatest weakness of it, in my opinion. Wayland is still relatively new in most used distributions and I expect things to get better in the next five years.

Majority of the drivers are baked into the kernel on Linux. Without knowing the version of Kubuntu you were using, it is hard to judge why Tuxedo OS played better with your headphones. I am using Sony WH-1000XM5 on Fedora with kernel 6.13 and works perfectly.

Regarding updates: almost every package on nearly every Linux distro (except the kernel) can be updated without rebooting. It is just that Ubuntu (Kubuntu is just Ubuntu with KDE Plasma desktop) is configured to apply updates at reboot to minimize any breakages. So is Fedora that I am using and I really like it. You can update the system through a terminal if you want to do so without rebooting.

The login issue you encountered is due to SDDM - login manager used by KDE Plasma. KDE is planning to replace it with something they develop themselves.

I don’t really understand this one. Did the toolbar just disappear from all apps? They usually do that when you add a global menu widget to your desktop, but shouldn’t otherwise.

Automatic mounting of drives is done easiest through editing the /etc/fstab file in Linux. I am not aware any other methods that are more user-friendly.

Unless you have a specific reason for using Tuxedo OS, I would highly recommend Fedora with KDE Plasma desktop environment. Tuxedo OS is still pretty niche and targets Tuxedo’s (the company) own laptops. Fedora has much larger user base so issues like this are solved faster. It also ships with the latest versions of the kernel, so you’ll have less driver issues.

Alaknar@lemm.ee on 30 Mar 15:24 collapse

(K)Ubuntu is configured to apply updates at reboot to minimize any breakages

That’s the problem - it never did apply the updates. I even tested that by manually telling it to download them all and then rebooting once they were all ready to install. I had to re-download them all after logging back in.

I also noticed that one account was always getting app updates while OS updates were ONLY showing up for the primary account,

I get how this may be “by design”, but it’s an infuriating design. :D

Did the toolbar just disappear from all apps?

Correct. It was just not there. I was able to add the Global Toolbar widget and get a “Mac-like” experience, or add it as a hamburger button on the titlebar, but that’s it.

Automatic mounting of drives is done easiest through editing the /etc/fstab file in Linux. I am not aware any other methods that are more user-friendly

Which is also extremely bad design, if you ask me. For removable drives - sure, why not. But if it’s a bloody NVMe sitting on the motherboard? Also: there just should be a prompt going “do you want to auto-mount this” the moment the user mounts it through Dolphin for the first time.

Unless you have a specific reason for using Tuxedo OS, I would highly recommend Fedora with KDE Plasma desktop environment

As of right now, I’m having a great time with Tuxedo OS - other than the Sleep function not working, everything else is smooth sailing. I don’t want to use Fedora, because I’m more familiar (if still barely) with the Debian Linux family.

It also ships with the latest versions of the kernel, so you’ll have less driver issues.

Is there an easy way to check the kernel version I’m running vs the latest available?

pogodem0n@lemmy.world on 30 Mar 16:30 collapse

Most graphical system updaters (e.g Discover) use packagekit instead of calling on apt directly. This may lead to them having conflicting list of upgradable packages. Updating through either way will eventually refresh the cache and things will go back to normal.

I have never had to share a computer with other people, so can’t really comment on that.

I did try messing around with my Plasma desktop to try and replicate that, but did not find that option. Though, I am sure that’s configurable and you changed it accidentally. You should ask around KDE forums about that.

I understand your frustration as an end-user, coming from other operating systems. But, you should keep in mind that Linux is just the kernel and it was made to be as modular as possible. Since you can use it with many different desktops, there needs to be a common way apps from those desktops can perform this. I believe Gnome can do this graphically through its Disks utility, which just edits the /etc/fstab file in the background. ~~You could request this feature from the KDE developers though.~~

Edit: sorry, I now remember KDE Partition Manager and it can do the same, like Gnome Disks.

Since you are new to Linux, the differences Fedora and Ubuntu will have for you will come down to the package manager (dnf vs. apt), and since you prefer to update your system graphically, you shouldn’t notice any difference.

You can find your kernel version by searching “About this System” in KDE Plasma, or using the following command:

$ uname -r

The latest version of the kernel can be found in the official website of the Linux kernel.

catloaf@lemm.ee on 29 Mar 23:11 collapse

I don’t see a list of hardware in your edit.

Alaknar@lemm.ee on 29 Mar 23:52 collapse

What else do you need? CPU+GPU is there. MoBo? It’s an MSI B650 Gaming Plus WIFI ATX AM5.

catloaf@lemm.ee on 30 Mar 00:08 collapse

Anything that might interfere with sleep. Literally any attached device might have a buggy driver.

Scholars_Mate@lemmy.world on 29 Mar 21:11 next collapse

It might be due to 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.

Alaknar@lemm.ee on 29 Mar 22:12 collapse

Just tried it now. Does it need a reboot first? As in: should I try again?

Scholars_Mate@lemmy.world on 29 Mar 22:20 collapse

As long as you ran systemctl daemon-reload, you should be able to try sleeping without needing to reboot.

Alaknar@lemm.ee on 29 Mar 23:15 collapse

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” to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

Should I remove that?

Scholars_Mate@lemmy.world on 29 Mar 23:49 collapse

You can leave it.

Corngood@lemmy.ml on 29 Mar 21:33 next collapse

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

Alaknar@lemm.ee on 29 Mar 21:59 collapse

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…

Corngood@lemmy.ml on 29 Mar 23:35 next collapse

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: wiki.archlinux.org/title/Linux_console

catloaf@lemm.ee on 30 Mar 01:24 next collapse

What are the crazy historical reasons? As far as I know, running six ttys and one graphical session, in that order, has been standard.

The really crazy historical way to test for crashes is num/scroll/caps lock. That’s handled by a very low-level kernel driver. If those are responsive, it’s probably just your display (gpu, X, wayland, or something) that’s locked up. If they’re unresponsive, your kernel is locked up. (If you’re lucky, it’s just gotten real busy and might catch up in a minute, but I’ve only seen that happen once.)

Alaknar@lemm.ee on 30 Mar 10:16 collapse

I was able to make some progress in troubleshooting.

I went to the Screen Locking options and disabled “Lock after waking from sleep”. Now I get to see the screen when I wake the computer back up, frozen as it was when I issued the sleep command.

All devices are disconnected - no network, no Bluetooth, no audio, all the “tray” icons are greyed out and/or showing errors, time is stopped at the moment I clicked the “Sleep” button.

Not sure if that helps at all.

ReversalHatchery@beehaw.org on 30 Mar 20:03 collapse

after wake up, does the numlock button change its light when you press it?

Alaknar@lemm.ee on 30 Mar 20:46 collapse

No, the keyboard is unresponsive. I also tried Ctrl+Alt+F1…F7, and got absolutely nothing.

I did a BIOS update, as advised here, and the behaviour changed! Now the freeze happens BEFORE the PC goes to sleep. As in: it gets to the frozen state the moment I click the button and the screens remain on.

Alaknar@lemm.ee on 30 Mar 10:20 collapse

OK, I tried that. Ctrl+Alt+F2 gives me a black screen.

Ctrl+Alt+F1 brings me back to my desktop.

Ctrl+Alt+F3-F6 all have a text login screen. F7+ don’t do anything.

I was able to grab the journalctl logs. You can find them (and an extra bit about the computer state I was able to get) HERE.

ReversalHatchery@beehaw.org on 30 Mar 20:15 collapse

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

Alaknar@lemm.ee on 30 Mar 20:50 collapse

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.

ReversalHatchery@beehaw.org on 31 Mar 00:46 collapse

here is the low-level documentation on sleep on linux, and the ways you can initiate it: docs.kernel.org/admin-guide/pm/sleep-states.html#…

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: wiki.archlinux.org/title/…/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

[deleted] on 29 Mar 23:05 next collapse

ronflex@lemmy.world on 30 Mar 00:08 next collapse

This is not a solution at all and just what I usually resort to, I always disable sleep on every OS and computer I use. I’ve always had strange issues after waking up from sleep that persist until reboot and I can’t even remember what they are now because it’s been so long since I’ve used it.

Akip@discuss.tchncs.de on 30 Mar 00:33 next collapse

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, tomshardware.com/…/bios-beginners,1126-8.html or checking if the latest bios is installed red.artemislena.eu/…/gigabye_b650_aorus_elite_ax_…

Alaknar@lemm.ee on 30 Mar 09:37 collapse

Hmm… Wouldn’t I also have sleep problems on Windows if this was a BIOS issue?

Akip@discuss.tchncs.de on 30 Mar 09:43 next collapse

I don’t know enough to rule out that windows could overwrite bios.

Alaknar@lemm.ee on 30 Mar 10:29 collapse

There’s no Windows, I nuked the drive before installing Tuxedo OS.

Akip@discuss.tchncs.de on 30 Mar 12:10 collapse

In the sense of windows boots and changes values of the bios that aren’t saved between boots. Similar to how fan curves can be changed or GPUs overclocked.

Alaknar@lemm.ee on 30 Mar 20:43 collapse

I did some more digging and in System Settings → Screen Locking found an option called “Lock after waking from sleep”. Since the OS was freezing on the lock screen, I disabled that to see what happens.

The OS freezes completely just before the shutdown to sleep - I can see ALL devices get booted out - network, BT, audio, mouse, keyboard - everything gets disconnected and then freeze happens.

I have updated the BIOS to the latest version and since then the freeze happens BEFORE the OS goes to sleep. As in: I click the Sleep button, everything freezes, that’s it, the screens never turn off.

So it doesn’t seem like it’s something that’s happening in BIOS during wake-up/reboot, right?

Akip@discuss.tchncs.de on 30 Mar 21:41 collapse

Does the system also freeze on lock screen without the sleep? superkey(winkey)+L

I’m no expert on TuxedoOS you might need to contact their support www.tuxedocomputers.com/en/Help-Support.tuxedo I also found this while digging. reddit.com/…/how_to_enable_hibernation_in_tuxedo_…

Alaknar@lemm.ee on 30 Mar 22:13 collapse

Does the system also freeze on lock screen without the sleep? superkey(winkey)+L

No, lock screen works fine.

Cheers for the links, I’ll look into that!

ReversalHatchery@beehaw.org on 30 Mar 20:18 collapse

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

just_another_person@lemmy.world on 30 Mar 00:52 next collapse

Is your root partition encrypted?

Give the output of lsblk if you could.

Alaknar@lemm.ee on 30 Mar 09:36 collapse

alaknar@HostName:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0     4K  1 loop /snap/bare/5
loop1         7:1    0 104,2M  1 loop /snap/core/17200
loop2         7:2    0  55,4M  1 loop /snap/core18/2855
loop3         7:3    0  63,7M  1 loop /snap/core20/2496
loop4         7:4    0  73,9M  1 loop /snap/core22/1802
loop5         7:5    0 164,8M  1 loop /snap/gnome-3-28-1804/198
loop6         7:6    0   516M  1 loop /snap/gnome-42-2204/202
loop7         7:7    0  91,7M  1 loop /snap/gtk-common-themes/1535
loop8         7:8    0  10,8M  1 loop /snap/snap-store/1248
loop9         7:9    0  44,4M  1 loop /snap/snapd/23771
nvme1n1     259:0    0 931,5G  0 disk 
├─nvme1n1p1 259:1    0   300M  0 part /boot/efi
└─nvme1n1p2 259:2    0 931,2G  0 part /
nvme0n1     259:3    0   1,8T  0 disk 
└─nvme0n1p1 259:4    0   1,8T  0 part /media/alaknar/BigStorage

just_another_person@lemmy.world on 30 Mar 10:10 collapse

I’m not seeing any swap space, so that could be it. Check this post out.

It could also be that your BIOS settings for suspend/resume aren’t set to something compatible with your existing config as well though, if the above doesn’t work, or you’re not comfortable with that level of interaction, check your BIOS first, then try the above maybe.

Alaknar@lemm.ee on 30 Mar 10:30 collapse

Everything worked fine on Windows - wouldn’t BIOS misconfiguration also cause problems there?

just_another_person@lemmy.world on 30 Mar 10:33 collapse

Not necessarily. Your OS and config may only support certain sleep states in combination with your motherboard and hardware.

Fizz@lemmy.nz on 30 Mar 02:28 next collapse

I’m pretty sure tuxedo support should be able to cover this for you. Its one of the bonuses of buying a Linux laptop.

Alaknar@lemm.ee on 30 Mar 09:34 collapse

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.

original_reader@lemm.ee on 30 Mar 02:59 next collapse

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?

Thorned_Rose@sh.itjust.works on 30 Mar 06:42 next collapse

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.

Alaknar@lemm.ee on 30 Mar 09:33 next collapse

Yeah, had a brain fart. It’s a freeze.

cypherpunks@lemmy.ml on 30 Mar 19:14 collapse

you could edit your post title

Alaknar@lemm.ee on 30 Mar 20:46 collapse

Oh, yeah, that’s true! Didn’t know that’s a thing here, good to know!

flubba86@lemmy.world on 30 Mar 20:53 collapse

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.

eugenia@lemmy.ml on 30 Mar 07:04 next collapse

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.

Alaknar@lemm.ee on 30 Mar 15:15 collapse

Well, I updated the BIOS - no change so far. I guess I’m stuck without Sleep. :/

Peffse@lemmy.world on 30 Mar 17:19 next collapse

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.

eugenia@lemmy.ml on 30 Mar 17:59 collapse

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.

ReakDuck@lemmy.ml on 30 Mar 20:26 collapse

I have it too now with KDE. Seems like something new

BoxOfFeet@lemmy.world on 30 Mar 12:46 next collapse

That exact issue is why I stopped using KDE. I never did figure it out.

zer0squar3d@lemmy.dbzer0.com on 30 Mar 21:25 collapse

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.

BoxOfFeet@lemmy.world on 31 Mar 00:20 collapse

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

ReakDuck@lemmy.ml on 30 Mar 19:06 next collapse

Having the same issue on Intel + AMD GPU.

Arch Linux with newest KDE.

Alaknar@lemm.ee on 30 Mar 20:52 collapse

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.

Bogus007@lemm.ee on 31 Mar 10:02 next collapse

Did you contact TUXEDO Support Centre?

Alaknar@lemm.ee on 31 Mar 18:53 collapse

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.

Bogus007@lemm.ee on 31 Mar 20:57 collapse

Give it a try. Perhaps they may give you at least a hint.

spacemanspiffy@lemmy.world on 31 Mar 12:13 collapse

What kernel version? I had similar issues on similar hardware. These have gone away in more recent kernels though.

Alaknar@lemm.ee on 31 Mar 18:53 collapse

6.11.0-109019-tuxedo.

Not the latest, right? I guess I’ll wait for an update.

spacemanspiffy@lemmy.world on 31 Mar 22:39 collapse

No, but I don’t believe I saw the issue until the 6.13.x kernels either