I have had some luck disabling Wake-On-LAN on the systems that don’t need it, or enabling higher sleep modes on the systems where that is available. My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
or if you meant that, computers are normally not pingable when they are asleep. net adapters only wake the computer when seeing a magic packet with their mac address in it, and it is the operating system that receives the ping request and decides to send back a ping response.
an exception is when it is set up to wake on some network traffic pattern, but few net adapters support that mode of operation
I was saying that my theory is that this functionality is broken or being bypassed on Windows such that when it gets hit by for instance the Network Discovery or “Do you have this update already downloaded?” ping from another Windows computer it wakes up to have a chat. I meant other systems are looking for active machines and those pings are waking it up or keeping it from going to sleep. I may have chosen a bad slang since ‘ping’ is a net command.
This theory is based on my understanding that computers don’t go all the way to sleep anymore and reenabling S3 restores normal sleeping. I included WoL because I have a machine that doesn’t have the S3 option but disabling WoL seemed to help on that one.
This theory is based on my understanding that computers don’t go all the way to sleep anymore and reenabling S3 restores normal sleeping.
yeah, now that you say that is probably most laptops in the last few years. but I don’t think desktops do it. wrong, even my 4+ years old pc motherboard supports it according to /sys/power/mem_sleep
Meanwhile every Windows 10 install I’ve ever had fails to go to sleep 90% of the time, and none of the powercfg commands reveal why.
Can’t go to sleep if its busy doing telemetry
Almost like sleep mode on x86 is impossible to do correctly. I’m not even sure Windows does better or worse than Linux on this one.
Best I’ve had is to disable modern standby and re enable s3 standby.
I have had some luck disabling Wake-On-LAN on the systems that don’t need it, or enabling higher sleep modes on the systems where that is available. My pet theory is that a lot of systems are constantly looking at what is active on the network and those pings are keeping the machine awake.
its not the system that handles wol, it doesn’t need to ping anything. even the net adapter doesn’t need to do that
I’m not sure what you are trying to say.
I wanted to say this is not how it works:
or if you meant that, computers are normally not pingable when they are asleep. net adapters only wake the computer when seeing a magic packet with their mac address in it, and it is the operating system that receives the ping request and decides to send back a ping response.
an exception is when it is set up to wake on some network traffic pattern, but few net adapters support that mode of operation
https://wiki.archlinux.org/title/Wake-on-LAN#Enable_WoL_on_the_network_adapter
I was saying that my theory is that this functionality is broken or being bypassed on Windows such that when it gets hit by for instance the Network Discovery or “Do you have this update already downloaded?” ping from another Windows computer it wakes up to have a chat. I meant other systems are looking for active machines and those pings are waking it up or keeping it from going to sleep. I may have chosen a bad slang since ‘ping’ is a net command.
This theory is based on my understanding that computers don’t go all the way to sleep anymore and reenabling S3 restores normal sleeping. I included WoL because I have a machine that doesn’t have the S3 option but disabling WoL seemed to help on that one.
yeah, now that you say that is probably most laptops in the last few years.
but I don’t think desktops do it.wrong, even my 4+ years old pc motherboard supports it according to /sys/power/mem_sleepHe’s saying they don’t call it a “magic packet” for nothing.
Right but my point was that doesn’t matter if your machine is in S3 or S4 instead of S1.
it’s almost like we peaked in the late 90s early 2000s.