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.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. 🇬🇧 Language/язык/Sprache
- This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
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.
It worked decades ago perfectly
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:
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
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.
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
He's saying they don't call it a "magic packet" for nothing.
it's almost like we peaked in the late 90s early 2000s.
Best I've had is to disable modern standby and re enable s3 standby.
Have you tried using nix-hardware repo? They have some device specific configs that apply.
If you are, have you tried doing it "raw" in the configs instead?
Also if you are using an AMD CPU, smokeless UMAF has more BIOS options, and you can try enabling/disabling modern standby as well as a LOT of other power options.
I'll try that. Thank you!
I am facing similar issues on an old laptop running debian. Sometimes work and sometimes doesn't but my guess is the kernel update but I don't use it enough to try and fix it. Try downgrading kernel, may help your case. It does run pretty well for a 10 yr old laptop without ssd so no complaints there.
Odd how this affects laptops. My desktop works perfectly with suspend, far better than It ever did with windows.
Desktops don’t normally have S0 suspend. Laptops have all switched over to that and it’s a pain in the ass.
My Asus ROG laptop does the same thing. 4080 laptop gpu Ryzen processor. Mine also if it darkens the screen and locks when I come back my external monitors resolution is wrong and requires me to fully unplug it from my laptop and plug it back in to get it correct again. Same when my laptop starts from full power off. I've also just kind of given up on these issues and have resulted to work around lol
I had this issue when I had my filesystem on an sdcard. Turns out they turn off after sleep and don't wake back up automatically.
X86 gonna x86.
mines been staying awake and asking me to confirm when I open it back up.
To fix this, I pass amd_iommu=off
as a kernel parameter in GRUB οptions.