Skip to content

Add TPM note to troubleshooting guide #500

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.

Sign up for GitHub

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

Merged
tashian merged 1 commit into from
Mar 23, 2026
Merged

Add TPM note to troubleshooting guide #500

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions platform/troubleshooting-agent.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -181,13 +181,14 @@ Each check validates a specific aspect of the agent's functionality. A **PASS**
- **systemd** (Linux only) - Confirms systemd is running for managing network connections

**Common failure reasons:**
- No TPM 2.0 module present or enabled in BIOS/UEFI
- No TPM 2.0 module present or enabled in BIOS/UEFI/Virtual Machine
- TPM is locked or inaccessible
- User lacks permissions to access the TPM (Linux)
- systemd is not the init system (Linux)

**Troubleshooting steps:**
1. Verify TPM 2.0 is enabled in your system BIOS/UEFI settings
1. Verify TPM 2.0 is enabled in your system BIOS/UEFI settings.
In a virtual machine environment, you will need to either enable "TPM Passthrough" (which uses the host's hardware TPM), or enable TPM emulation for the machine. While emulated TPMs do not offer full hardware attestation, they can be useful for testing environments.
2. On Linux, check TPM permissions: `ls -l /dev/tpm*`
3. On Linux, ensure the user has read/write access to `/dev/tpmrm0`
4. On Windows, verify TPM is enabled: Run `tpm.msc` or check Device Manager
Expand Down
Loading