docs: black screen after idle is a failed s2idle resume - #55
Open
Weijtmans wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the one intermittent-black-screen case the existing list does not cover: the box is not overheating or crashing, it suspended and never came back. The BC-250 offers only s2idle and resume does not work on this hardware, so an idle timeout turns into a hang that needs a power cut.
What the new subsection gives:
PM: suspend entry (s2idle)with no resume line (journalctl -b -1 -n 5).Also adds a matching entry to the Bazzite page's Known Issues that links here, since that is where an affected user is likely to look first.
First-party: hit, diagnosed and fixed on the tested board.
mkdocs build --strictpasses.