Hacker News Reader

Comment by rjzzleep | Hacker News Reader

It's not really Linux' fault. Most It's Microsoft that forced this, and most vendors don't know how to deal with this and work proper firmware. I think Framework and Valve fixed theirs. I have a GPD and just found out that the reason I kept getting it wake from sleep was some MS related option triggering an ACPI IRQ 9 sleep wake.

On another note, I actually think that the most important things that work better on the Apple devices is the mic and camera, the rest is somewhat unimportant on the go if you work at a desk.

View on HN

As a user I don't care whose fault is it. I want my laptop to go to sleep when I close the lid; I want it to stay asleep while the lid is closed; I want it to wake when I open the lid. Only macs seem to be able to do that consistently; I'd be glad to be proven wrong, but over the past decade I haven't found a counterexample yet.

I’ve never had a problem with a system76 or tuxedo computers laptop using suspend correctly. If you want it to just work, you may need to buy from a manufacturer who you pay to make it just work. Otherwise you’re comparing a dyi setup to Apple.

I don't think that's even true with my m3 mbp16. I haven't tweaked with the power settings but I'm pretty sure it is in a connected sleep state when I close the lid; at least when I'm hotspotting my phone will register it as a connected device.

Yes, I can confirm. But i thought that was by design

This can be enabled or disabled under the System Settings > Battery > Options > Wake for network access (Always / Power adapter / Never). Or possibly the phone registers it as connected for a while after it sends its last packet?

IIRC, Macs also do tricky networking things to make it faster to come back online from sleep. I'd be curious if the computer is actually sending packets vs. just keeping the address configured and waiting.

(That may just be on iOS though...)

Dell latitude laptops sleep very reliably. I have had 4 in a row now since 2007.

Also as a side note, as a user, I agree you don't care whose fault is it, but then this is hacker news where we are interested in whose fault it is.

I think Intel is partially at fault. On Apple’s Intel hardware, suspend and resume worked, but it was very slow due to the weirdly baroque power management. The M1 MacBooks were a revelation; the screen woke instantly when you opened it.

AMD removed s3 suspend support on Phoenix due to Microsoft pressure. So you can enter S3, but the GPU can't resume from it.

Reply on news.ycombinator.com