You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The last batch of darp8 do not de-assert the PLTRST# virtual wire on S3 resume, causing the system to hang on wake.
Steps to reproduce
Switch to S3 suspend: echo deep | sudo tee /sys/power/mem_sleep
Suspend the system: sudo systemctl suspend
Wake the system: Press the power button
Expected behavior
System resumes to desktop.
Actual behavior
System hangs with solid green LED and black screen.
Additional info
This is seemingly an unidentified BOM change from Clevo, as the engineering units we originally received and first batch of production units that customers received (which also had an unidentified change that broke on our firmware) do not have the issue.
CSME should be enabled when S0ix is used for power savings during
suspend. TGL-U is just one case where we default as our TGL-U models
do not support S3. Other models may use S0ix as well, such as darp8 and
darp9 due to new batches just not working with S3 anymore [1].
[1]: #507
Signed-off-by: Tim Crawford <tcrawford@system76.com>
CSME should be enabled when S0ix is used for power savings during
suspend. TGL-U is just one case where we default as our TGL-U models
do not support S3. Other models may use S0ix as well, such as darp8 and
darp9 due to new batches just not working with S3 anymore [1].
[1]: #507
Signed-off-by: Tim Crawford <tcrawford@system76.com>
The last batch of darp8 do not de-assert the
PLTRST#
virtual wire on S3 resume, causing the system to hang on wake.Steps to reproduce
echo deep | sudo tee /sys/power/mem_sleep
sudo systemctl suspend
Expected behavior
System resumes to desktop.
Actual behavior
System hangs with solid green LED and black screen.
Additional info
This is seemingly an unidentified BOM change from Clevo, as the engineering units we originally received and first batch of production units that customers received (which also had an unidentified change that broke on our firmware) do not have the issue.
Ref: #469
The text was updated successfully, but these errors were encountered: