I guess this vulnerability has been ignored for years, because hackers also ignored it for years.

There’s not a lot you can gain from this kind of vulnerability.

If the doctor is unimportant enough to have a helipad, the doctor can come to the billionaire.

I first understood that maybe 15 years ago, when I was in the UK during the supposed mass riots there. My parents read about that in the media (European public service broadcast news) about the anarchic circumstances and were worried about me.

I was in one of the cities hit hardest, according to the media, and my flat was actually right at the location this was about.

All that really happened was a single demonstration that was mostly peaceful without any vandalism. That’s it.

It does work fine too on my 2010 EEE PC running Antix running on a 5.10.x kernel. Seems to be more an issue with newer devices, since every single laptop I own that’s newer than maybe 2013 has these issues.

It’s essentially not different than the current situation from an exploitability aspect.

Currently every human being owns one “commercial robot”, aka their body. Theoretically this means that labor is distributed: Every person can perform the work of one person.

But that doesn’t stop capitalism to exploit that labor unfairly. A worker earning a company €1, gets only a very small fraction of that money.

That’s literally the system we have now.

And we aren’t even getting into what kind of robot one owns and that these robots perform wildly different depending on the task at hand (factory robot, vacuum cleaner robot, anything in between, …)

Loss is incredibly boring. It’s become the millenial equivalent of a boomer joke. Might have been funny 17 years ago. But that was 17 years ago. Get a new joke.

Every single one so far.

Fair.

The only purpose S0 standby has on my work laptop is to make sure that my bluetooth headset always prioritizes connecting to my sleeping laptop in my backpack over connecting to my phone that I want to watch youtube on while on the train.

The DOS BIOS was also sometimes called IOS, and the Input/Output Supervisor in the IBM OS/360 was also abbreviated as IOS.

The laptops are Lenovo LOQ, HP (work laptop) and Gigabyte.

It’s an EEE PC 1005P. It’s an outdated piece of garbage, but sleeping works perfectly and the battery life is crazy. 8 hours on its extended battery, 5 hours on the stock battery. And these aren’t new batteries either.

With AntiX Linux performance is ok enough for what I need it for.

I also had it that one laptop was configured to wake any time the mouse moved even a tiny bit. So walk past the laptop, laptop is now awake.

Sadly I cannot configure any of that on my work laptop, because helpdesk thinks allowing me to do so would be a security risk or something like that.

Instructions unclear, now my laptop is covered in sticky stuff.

Tbh, I don’t know. The last time I used a desktop on a daily basis was 2020, and that was just my work PC where I wouldn’t really care if it woke up while I wasn’t at work.

The last time I had a desktop PC at home was in 2009, so I really can’t say what is happening there in the meantime.

And at least to me, sleep on a laptop is much more important than on a desktop. Battery usage isn’t really a thing on a desktop (usually at least).

Interestingly, I do own a little 2010 netbook that I use as an ultra-mobile laptop when I really don’t need any kind of performance, and that one does all sleep states including hibernation perfectly out of the box. Even when just sleeping it loses maybe 1-2% of charge per day.

But all the other laptops I own suck when sleeping.

I wouldn’t mind if at least hibernation worked. But it always loses the state on hibernate and acts as if there was just a power loss. It boots up with a fresh state instead of the stored one.

Sleep and hibernate don’t work for me.

Hibernate just acts like a power loss. After shutting down the state is just lost and the laptop starts up with a fresh boot.

With Modern Sleep, kernels 6.11+ go to sleep fine, but don’t manage to wake back up. The keyboard lights up for half a minute, the fan goes on, the screen stays dark and after half a minute the laptop goes back to sleep. Kernel 6.10 sometimes works, sometimes behaves like 6.11+. I’d say it works 80% of the time.

I disabled Modern Sleep in BIOS and tried to enable S3, S2 and S2+S3 in BIOS instead. I set the corresponding sleep states in Linux as well, and no matter which one of the non-modern-sleep options I try, and no matter if I’m using kernel 6.10 or 6.15, it never manages to wake up (same symptoms as above).

Lenovo LOQ 15ARP9.

To unlock, go to the BIOS, open advanced settings, hold FN+R+N, release, press F10 to save and reboot, head back to the BIOS and all options are unlocked.

Some Lenovo laptops have other key combinations, some need a tool, some need a modified BIOS.

I unlocked my bios (luckily Lenovo allows that with just a “secret” key combination in the bios) and disabled modern sleep, enabled S3 and S2 and tried that, with the result that my Linux freezes every time on wake up instead of only half the time…

Don’t know what exactly they messed up there, but it’s frustrating.

Stuff can work, but it also cannot work. It really comes down to the exact hardware combination and the games you are running and often even plain luck.

And if you are in the “It doesn’t work” camp, then you are screwed without serious skill.

Gaming on Linux is kind of like relationships. If you are one of the lucky ones where it works without effort, be grateful and don’t go around telling everyone who has problems that it’s super easy. Because it’s more luck than skill and your experience might not fit the experience that others have.