Wayland is pretty darn great nowadays, hell I’m running KDE and got HDR on my desktop; haven’t had any odd goings on since 2023 (though nvidia is still meh)
Same. Intel ran it great, but Nvidia is still pretty bad about running Wayland.
When the Steam Deck dropped I got an AMD GPU and it’s close.to Intel levels of seamless. That’s when I knew that Wayland is more than ready, Nvidia just still is not.
Works great… until you realize your GPU isn’t liked by Wayland when you have more than one monitor lol. Then Wayland is uninstalled and you go back to Xorg or XFCE.
It’s weird, had this issue with multiple monitors where wayland is either a glitchy refresh rate mess or just doesn’t recognize at all. Nvidia, amd, discrete or dedicated, native driver or oem driver: they’re all finicky under wayland when multiple monitors are used.
It’s funny. I used gnome for a long time, and after I fully switched to Debian, I didn’t have any problems with my nvidia card with gnome + wayland. But I switched to plasma recently, and it’s janky. I figured out my vsync issues, but it still runs a post when I wake it from sleep, which just defeats the purpose of sleep mode. I might as well shut it down every time I’m done using it like it’s 1997.
But I started using X + KDE, and most of my problems went away. Still takes forever to wake from sleep. But that’s it, really.
Years ago Nvidia employed a developer who fixed incompatibilities with their proprietary driver. He looked at what caused the issue and even had the driver fixed when Plasma exposed a driver bug.
Then Nvidia decided not to continue this and most KDE development now happens on hardware supported by FOSS drivers. Valve investing in KDE because of Steam Deck and its FOSS Radeon drivers underlined this trend.
Yeah, in this day and age, why even keep the computer running if there aren’t any important tasks running? I’ve always shut my computers down at the end of the day, but mainly because I’m poor and watch my bills very closely… :P
I keep mine running 24/7 because it puts less thermal wear on the hardware. But I pay a flat rate for my electricity included in my rent, so it doesn’t cost any extra.
May I ask how does turning it off cause more wear and tear? From my understanding, running it constantly wears it out, but I’ve never heard that turning it off causes it to thermal wear?
Thermal expansion and contraction is what can lead to the die cracking.
Not really a problem on anything other than laptops with shitty coolers which can reach 110C.
Yeah, and I don’t see the risk being there when you look at the numbers. My CPU is sitting at around 30C right now, and if I shut it down, it might gradually drop by as much as 10 degrees over a period of hours.
But if I start an encode, the temperature will rise by 20-30 degrees in seconds, then drop back down 20-30 degrees in seconds when the encode stops. And if I run some ridiculous synthetic stress testing tool for stability testing an overclock, that could make the core temp shoot up and down by 60 degrees.
I usually leave it on all the time though, because it does server stuff too.
LMDE Cinnamon user here. There’s a setting in the power options that tells the computer to switch to hibernate if it remains in suspend for a certain amount of time. Hibernated computers suspend to disk rather than RAM and are basically switched off, so need to POST to come back online.
It took me a while to find that setting, and it might be the same case with whatever you’re using.
What’s more, it only took effect if I used the GUI to put the computer into suspend mode. I usually use a keyboard combo to suspend the computer at night, but occasionally I’d use the GUI and come back in the morning to a hibernated computer.
Thought I’d been taking crazy pills or that there was something wrong.
My main gripes are that inconsistency between suspend methods and also that there’s no setting for how long to stay in suspend before hibernating. I have no idea if that’s a UEFI thing or something that could be set elsewhere, but I’d probably use that feature if I could set it.
As it is I’m giving the hybrid option a try. Basically it suspends like normal, but also sets up a hibernated restart for if the power goes out. That hasn’t happened yet, so can only assume it’ll work when the time comes.
Late edit: The delay between suspend and hibernate is set in /etc/systemd/sleep.conf with the setting HibernateDelaySec=. Manual page reading is required, but even so, this feature is not well documented there or out on the Internet.
There may be syntax available to specify other units of time with a suffix. For example, my computer’s related SuspendEstimationSec= option is given as 60min in the example and not 3600.
I still haven’t been able to get wake from sleep working in distros with Wayland on my PC with an NVIDIA GPU. Tried in EndeavourOS and Garuda. It crashes trying to wake from sleep every time. I’ve tried everything in the arch wiki and search engine results like modifying config files and whatnot, no dice.
It really is pretty great nowadays. I always had both my laptops with fractional scaling and currently it all seems to work very well, no more weird renderings anywhere. And a greater thing, I had a external screen I left unused for multiple years because it needed to be used with a different fractional scaling than the laptop it was connected and now it just works and I can finally use it. It’s nice. I don’t have hdr needs but color management seems to be properly in place now and the bugs I had previously with it are also gone - like it did something weird on some video recording app and some weird stuff with that thing that changes the color of the screen when it’s night - it all just works now.
Electron apps are still broken if you’re on Hyprland and NVIDIA. They just randomly stop working, and when I last checked, nobody had yet figured out why.
It’s why I’m on KDE, because that’s been perfectly stable for me. Plus, KDE is great anyway.
Wayland is pretty darn great nowadays, hell I’m running KDE and got HDR on my desktop; haven’t had any odd goings on since 2023 (though nvidia is still meh)
Same. Intel ran it great, but Nvidia is still pretty bad about running Wayland.
When the Steam Deck dropped I got an AMD GPU and it’s close.to Intel levels of seamless. That’s when I knew that Wayland is more than ready, Nvidia just still is not.
Works great… until you realize your GPU isn’t liked by Wayland when you have more than one monitor lol. Then Wayland is uninstalled and you go back to Xorg or XFCE.
It’s weird, had this issue with multiple monitors where wayland is either a glitchy refresh rate mess or just doesn’t recognize at all. Nvidia, amd, discrete or dedicated, native driver or oem driver: they’re all finicky under wayland when multiple monitors are used.
When isn’t nvidia meh?
It’s funny. I used gnome for a long time, and after I fully switched to Debian, I didn’t have any problems with my nvidia card with gnome + wayland. But I switched to plasma recently, and it’s janky. I figured out my vsync issues, but it still runs a post when I wake it from sleep, which just defeats the purpose of sleep mode. I might as well shut it down every time I’m done using it like it’s 1997.
But I started using X + KDE, and most of my problems went away. Still takes forever to wake from sleep. But that’s it, really.
Years ago Nvidia employed a developer who fixed incompatibilities with their proprietary driver. He looked at what caused the issue and even had the driver fixed when Plasma exposed a driver bug.
Then Nvidia decided not to continue this and most KDE development now happens on hardware supported by FOSS drivers. Valve investing in KDE because of Steam Deck and its FOSS Radeon drivers underlined this trend.
Hello, I shut down PC every time I’m done using it like it’s 1997
25 W idle * 1 year = 219kWh
ANS * 0.21 EUR/kWh = 45.99 EUR
I’d say that’s still a significant amount, even if you subtract from that amount the time you use the computer.
Yeah, in this day and age, why even keep the computer running if there aren’t any important tasks running? I’ve always shut my computers down at the end of the day, but mainly because I’m poor and watch my bills very closely… :P
I keep mine running 24/7 because it puts less thermal wear on the hardware. But I pay a flat rate for my electricity included in my rent, so it doesn’t cost any extra.
May I ask how does turning it off cause more wear and tear? From my understanding, running it constantly wears it out, but I’ve never heard that turning it off causes it to thermal wear?
Thermal expansion and contraction is what can lead to the die cracking. Not really a problem on anything other than laptops with shitty coolers which can reach 110C.
Yeah, and I don’t see the risk being there when you look at the numbers. My CPU is sitting at around 30C right now, and if I shut it down, it might gradually drop by as much as 10 degrees over a period of hours.
But if I start an encode, the temperature will rise by 20-30 degrees in seconds, then drop back down 20-30 degrees in seconds when the encode stops. And if I run some ridiculous synthetic stress testing tool for stability testing an overclock, that could make the core temp shoot up and down by 60 degrees.
I usually leave it on all the time though, because it does server stuff too.
LMDE Cinnamon user here. There’s a setting in the power options that tells the computer to switch to hibernate if it remains in suspend for a certain amount of time. Hibernated computers suspend to disk rather than RAM and are basically switched off, so need to POST to come back online.
It took me a while to find that setting, and it might be the same case with whatever you’re using.
What’s more, it only took effect if I used the GUI to put the computer into suspend mode. I usually use a keyboard combo to suspend the computer at night, but occasionally I’d use the GUI and come back in the morning to a hibernated computer.
Thought I’d been taking crazy pills or that there was something wrong.
My main gripes are that inconsistency between suspend methods and also that there’s no setting for how long to stay in suspend before hibernating. I have no idea if that’s a UEFI thing or something that could be set elsewhere, but I’d probably use that feature if I could set it.
As it is I’m giving the hybrid option a try. Basically it suspends like normal, but also sets up a hibernated restart for if the power goes out. That hasn’t happened yet, so can only assume it’ll work when the time comes.
Late edit: The delay between suspend and hibernate is set in
/etc/systemd/sleep.confwith the settingHibernateDelaySec=. Manual page reading is required, but even so, this feature is not well documented there or out on the Internet.There may be syntax available to specify other units of time with a suffix. For example, my computer’s related
SuspendEstimationSec=option is given as60minin the example and not3600.Pull the plug on your computer sometime to try it out?
Yeah, I really should. I’ll have a piece of hardware to install soon, so I might test it before I do that. Gotta switch off anyway so might as well.
I still haven’t been able to get wake from sleep working in distros with Wayland on my PC with an NVIDIA GPU. Tried in EndeavourOS and Garuda. It crashes trying to wake from sleep every time. I’ve tried everything in the arch wiki and search engine results like modifying config files and whatnot, no dice.
It really is pretty great nowadays. I always had both my laptops with fractional scaling and currently it all seems to work very well, no more weird renderings anywhere. And a greater thing, I had a external screen I left unused for multiple years because it needed to be used with a different fractional scaling than the laptop it was connected and now it just works and I can finally use it. It’s nice. I don’t have hdr needs but color management seems to be properly in place now and the bugs I had previously with it are also gone - like it did something weird on some video recording app and some weird stuff with that thing that changes the color of the screen when it’s night - it all just works now.
Electron apps are still broken if you’re on Hyprland and NVIDIA. They just randomly stop working, and when I last checked, nobody had yet figured out why.
It’s why I’m on KDE, because that’s been perfectly stable for me. Plus, KDE is great anyway.
Is it a wayland exclusive? I couldn’t find it in the x11 kde.
HDR is pretty much impossible in X11; especially since there are 0 plans for it, and no plans to do anything than bare minimum updates
To add to what you said, X11 is unmaintained software.
Xorg will be maintained because of XWayland for quite some time but it’s use cases outside this scope that are increasingly ignored.
HDR? Pretty much yeah.
HDR? Pretty sure it’s wayland only