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
Add FAQ page for doc/On-Premises-FPGA-Getting-Started #1612
base: main
Are you sure you want to change the base?
Conversation
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.
You need to point to this file in the index.rst
(otherwise it won't get rendered).
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.
The file should also not be named "Template" since it's not being templatized. Or IMO, this might be better to be added to each FPGA section as a template (i.e. each FPGA part of the docs has it's own FAQ).
|
||
To streamline the set-up process, we provide fix suggestions to the following errors that might appear during the process for reference. | ||
|
||
**SSH Setup** |
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.
This should be a subtitle not bold.
|
||
Please also note that ssh-agent might need to be set-up each time a new terminal is started. | ||
|
||
**Build Bitstream** |
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.
Ditto
To streamline the set-up process, we provide fix suggestions to the following errors that might appear during the process for reference. | ||
|
||
**SSH Setup** | ||
``build bitstream`` process stuck at :: |
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.
This isn't unique to just the buildbitstream
... this happens on a lot of FireSim steps. I would generalize a bit more here.
[localhost] local: pwd | ||
[localhost] run: ... |
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.
Use the code-block directive (search in other parts of the docs)
[localhost] run: ... | ||
|
||
|
||
The manager machine should be able to use ssh protocal to connect to build_farm and run_farm machines without providing password or passphrase duirng the connection process. |
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.
Instead, I would say that there is no passwordless access to the machine in question (i.e. localhost). And I would add a link to SSH setup docs that already exist.
Verify this by using ``ssh`` command from the manager machine. If a password or passphrase prompt appears, ssh-agent can be used to store and automatically provide login credentials. :: | ||
|
||
ssh-agent -s > AGENT_VARS | ||
source AGENT_VARS | ||
ssh-add ~/.ssh/firesim.pem |
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.
I would try to dedup. this with the other parts of the documentation (for easier future maintenance).
source AGENT_VARS | ||
ssh-add ~/.ssh/firesim.pem | ||
|
||
Please also note that ssh-agent might need to be set-up each time a new terminal is started. |
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.
Nit: Anything that is referenced in the code (or must be typed in the CLI) should be put in backticks (`)
|
||
This error is probably due to shell login scripts writing to standard out. | ||
|
||
Edit ``~/.bashrc`` and/or other login scripts to make sure standard out writing commands such as ``echo`` are either commented out or only executed when the shell is in interactive mode(directly receving commands typed by a user). |
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.
Edit ``~/.bashrc`` and/or other login scripts to make sure standard out writing commands such as ``echo`` are either commented out or only executed when the shell is in interactive mode(directly receving commands typed by a user). | |
Edit ``~/.bashrc`` and/or other login scripts to make sure that commands that write to stdout (such as ``echo``) are either commented out or only executed when the shell is in interactive mode (directly receiving commands typed by a user). |
Related PRs / Issues
None
UI / API Impact
No impact
Verilog / AGFI Compatibility
No impact
Contributor Checklist
changelog:<topic>
label?ci:fpga-deploy
label?Please Backport
label?Reviewer Checklist (only modified by reviewer)
Note: to run CI on PRs from forks, comment
@Mergifyio copy main
and manage the change from the new PR.changelog:<topic>
label?