[gryf]

I've had 20 years of anxiety about closing the lid, hibernating, sleeping. Numerous working configurations became non working configurations after kernel updates and distribution upgrades.

And that doesn't include some of the problems with the desktop software I've had.

On the server, zero hassle.

[taxyz]

Came here to echo this sentiment. I even bought from a specialized Linux laptop retailer hoping that the hardware would have been selected because of its Linux compatibility; either an upgrade from Ubuntu 20 to 22 or a kernel upgrade or an nvidia update broke my ability to close the lid and trigger suspend.

I tried everything, dove semi-deep into systemd settings, spent hours online and pouring through logs and journald and forums and bug reports. Tried rolling back versions of damn near everything only to then break things I had installed after other upgrades. I tried doing some half-assed custom shell scripts that felt janky.

After several nights of losing all my free time after work only to wake up the next morning to a dead laptop battery, I treated myself to an m2 13” mbp.

No ragrets.

[Brian_K_White]

Suspend is an industry-wide new problem affecting almost all new hardware since Windows convinced hardware makers to make S0 the default, and some don't even support S3 in their bios any more.

Google about "modern standby".

It's driven by a software change in Windows, but it affects Linux too because all mamufacturers made bios changes to support the Windows change.

The point I'm making is, Windows machines have the same problem for the last 2 or 3 years. Even macs have an essentially the same problem, just that on mac it's easy to change a setting to fix it.

It's not a Linux problem, and by that I do not just mean the usual that it's not Linux's fault that hardware manufacturers cater to Windows. I mean everything has the same problem right now, and the fix is to A: hope both your hardware has a bios that still provides support for S3 standby, B: use it.

Seperately, I personally have just never used standby or hibernate. It's true that aside from the current industry-wide issue caused by "modern standby", it's always been a bit of a problem on linux. Especially since I dual boot and also just never know how long the machine will be turned off or how much charge it will have when I close the lid, or rather I don't want to have to worry about it. So I just decided decades ago that the entire suspend and hibernate concept was a bad idea and I don't use them, on any platform. My machines shut down and boot up every time on battery. Plugged in they merely go idle and turn the monitors off. No swap or hiberfile even cpnfigured on linux or windows. Ever since ssd's booting from scratch has been fast enough. Standby and hibernate are just fundamentally not good ideas IMO. I don't care how popular and how they work 99% of the time. I opt out of that whole idea, on any platform.

And everything else works great. My daily life on linux is all in all, less grief than Windows.

[chmod775]

> After several nights of losing all my free time after work only to wake up the next morning to a dead laptop battery, I treated myself to an m2 13” mbp.

LTT just did a video on something like this: https://www.youtube.com/watch?v=OHKKcd3sx2c

tl;dw: It may not be a OS problem, but rather a problem of which sleep states are supported by your firmware, which would explain why nothing you did helped. Possibly suspend never really worked and Ubuntu just got meaner on the battery. Getting a MBP is valid fix if you disable "Wake for network access" on it.

[pxc]

I've been using Linux for ~18 years, exclusively for ~12, and I haven't really had notable hardware issues in ~7-8. I definitely haven't had much frustration with working hardware breaking (and pretty close to none since I switched to NixOS).

I do feel your pain, though. I remember things being brittle and finicky for a long time back in the aughts. But these days, almost all of that disappears if you give Linux the same kind of hardware commitment you'd give macOS, and just buy hardware that is made or sold with it in mind. You do still have to pretty much stay entirely away from NVIDIA, though. Unfortunately Linux vendors still sell hardware with NVIDIA's shoddy components and drivers because CUDA dominates GPGPU applications.

[aussiesnack]

> if you give Linux the same kind of hardware commitment you'd give macOS, and just buy hardware that is made or sold with it in mind

This is true and good advice for those of us who are primarily committed to using Linux. It is however a significant disadvantage compared to Windows. It is quite a joy just not to have to think about precise hardware specs (& not to have to continually read up on their changes). Buy just about anything, from a top end laptop to some weird gadget from Alibaba, to vast scads of second hand machines and parts from ebay, and you can be near certain it will work with Windows. There's no point pretending that's not terrific.

It's also a real but lesser disadvantage against MacOS, because Apple do the hardware curation for you (part of what you're overpaying for of course).

On balance I still find Linux the best choice for my purposes.