NeonGeckoCom / NeonGeckoCom/neon-docs

[FEAT] Mark2 power troubleshooting

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation enhancement help wanted
Dominant language
No language data
Stars
5
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Objective

Document what to do if a Mark2 has no display output.

Initial Implementation Requirements

Document that it can happen and the solution is to shutdown and re-power the device (not just restart).

Other Considerations

As reported on Mattermost: https://mycroft.cloud.mattermost.com/community/pl/ab8bsxoas3dqtkm4pshccagupa

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by finding the Mark2 hardware troubleshooting section in neon-docs. Document that no display output can occur and that the device must be shut down and re-powered, rather than merely restarted; use the linked Mattermost report for context.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.