Update BusID patching page to include more concise information regarding specific port types. #142
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
1 participant
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.
I've found this information useful when trying to troubleshoot a display output problem on my machine since the whatevergreen configuration used BusID only meant for DisplayPort and changing it to one meant for HDMI fixed the issue.
Maybe a more proeminently featured section at the start talking about cycling BusID's to fix the display problem and how to do it would be better as I initially ignored the mapping without MacOS section given that I had 1 display working withing MacOS. Or updating the Mapping withing MacOS section to remove the kaby lake example and update it to include information on using something like ioregistry explorer to identify the currently working connection and then cycling the BusID's on the other connections until the issues is fixed.