-
Notifications
You must be signed in to change notification settings - Fork 0
Framework 13 11th Gen S3 also not working properly in Windows #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Could you provide some more information about this please? S0 means the system is active, it's not a sleep mode. What are you trying to achieve? |
New version of what? Bios? Drivers? |
Do you want to use S3 not Modern Standby(S0iX)? |
So, I wanna use the S3 mode again, where the system is in actual sleep mode again. I didn't remove the registry entry that disables S0, so S3 is used, which is under: |
Device Information
System Model or SKU
Please select one of the following
BIOS VERSION
3.20
DIY Edition information
Memory: 2x Crucial CT32G4SFD832A.C16FF 32GB DDR4-3200
Storage: Samsung SSD 980 1TB
Port/Peripheral information
Standalone Operation
Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS?
Describe the bug
I've read under the Known issues that S3 might not work for Linux users. I"ve just installed the new version to hopefully get WiFi 6e to work (still won't work, Thanks Intel), not thinking that the issue also appears on Windows, bur here we are. I mostly set my Laptop into sleep (suspension) so I don't need to close and reopen most things the next day. The S3 mode seems to work just fine for around 2 minutes, after which it just turns on again.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
The laptop should stay in S3 until I press the power button or any key on the keyboard
Operating System
Additional context
I've added the registry entry in Windows so I don't have to suffer under Microsoft's shitty S0 implementation
The text was updated successfully, but these errors were encountered: