- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 17
Troubleshooting: expand and update #78
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
Conversation
Mention Secure Boot. Link to STABLE. Add a placeholder (ellipsis) for the desktop environment not appearing. Whilst here, reword things a little.
| Reviewer's Guide by SourceryThis pull request expands and updates the troubleshooting documentation, focusing on Secure Boot, hardware compatibility, and dual-GPU scenarios. State diagram for boot troubleshooting processstateDiagram-v2
    [*] --> CheckSecureBoot
    CheckSecureBoot --> DisableSecureBoot: Secure Boot enabled
    DisableSecureBoot --> AttemptBoot
    CheckSecureBoot --> AttemptBoot: Secure Boot disabled
    AttemptBoot --> Success: System boots
    AttemptBoot --> HardwareCheck: Boot fails
    HardwareCheck --> TryDifferentComputer: Hardware suspected
    TryDifferentComputer --> MediaCheck: Fails on different computer
    TryDifferentComputer --> HardwareIssue: Works on different computer
    HardwareCheck --> MediaCheck: Media suspected
    MediaCheck --> DownloadNewISO
    DownloadNewISO --> CreateNewUSB
    CreateNewUSB --> AttemptBoot
File-Level Changes
 Tips and commandsInteracting with Sourcery
 Customizing Your ExperienceAccess your dashboard to: 
 Getting Help
 | 
| https://docs.freebsd.org/en/books/faq/#hardware in the rewritten book of FAQ is not a good point of reference. Re: https://codeberg.org/grahamperrin/freebsd-doc/pulls/21 the first FAQ link for graphics is to https://wiki.freebsd.org/Graphics/Intel-GPU-Matrix, which is explicitly stale with an obsolete table; and so on. | 
For hardware components, the FreeBSD FAQ book currently lacks what's required. So, encourage people to read the much more informative hardware information that is provided by the FreeBSD Primary Release Engineering Team.
The first of the two symptoms is based on https://old.reddit.com/r/GhostBSD/comments/1h3cpjm/problem_for_install_ghostbsd/m3ljzbu/?context=2 The second is based on ghostbsd/issues#14 Revert to 'section' (not 'page') to describe what is incomplete.
Shorten the subheading. Be a little more descriptive about auto-config.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @grahamperrin - I've reviewed your changes - here's some feedback:
Overall Comments:
- There's a typo in the word 'occasionally' (spelled as 'ocassionally') that appears in the document.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Co-authored-by: Graham Perrin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| Thanks! Side notes: 
 | 
Add a section for Secure Boot.
Link to STABLE.
For hardware components, direct readers to hardware information that is provided by the FreeBSD Primary Release Engineering Team.
Add two dual-GPU scenarios.
Add a placeholder (ellipsis) subheading for the section that is incomplete.
Whilst here, reword things a little.
Original (draft) Summary by Sourcery
Expand and update the troubleshooting guide by adding Secure Boot information, updating links, and rewording sections for clarity.
Documentation: