-
Notifications
You must be signed in to change notification settings - Fork 0
Quick Start
Andrew Mello edited this page May 26, 2026
·
1 revision
Two-minute activation on Arch / Manjaro.
yay -S intel-amt-activateThis pulls in rpc-go-bin automatically.
sudo modprobe mei_me
sudo amt-activateThe script:
- Verifies
/dev/mei0exists andrpcis installed - Checks
rpc amtinfoforpre-provisioning state - Generates a 18-char password (upper + lower + digit + special) and saves it to
~/.amt-mebx-password.txt(mode 0600) - Runs
sudo rpc activate -local -ccm -password "$PW"and tees output to/tmp/amt-activate.log - Re-runs
rpc amtinfoto confirm CCM and report the AMT IP (may take 15–30s for DHCP)
Total time: ~40 seconds on CSME 16.1+. Up to 15 minutes on AMT 18.x (Meteor Lake) due to firmware-side handshake delay.
==> Checking AMT state...
Control Mode : pre-provisioning state
==> AMT password saved to /home/you/.amt-mebx-password.txt (mode 0600, 18 chars)
==> Activating Intel AMT — Client Control Mode...
time="..." level=info msg="Failed to connect to LMS, using local transport instead."
time="..." level=warn msg="Execution timeout after 20s"
time="..." level=warn msg="Execution timeout after 20s"
time="..." level=info msg="Status: Device activated in Client Control Mode"
==> Activation successful.
==> Verifying state (AMT IP may need 15-30s for DHCP)...
Control Mode : activated in client control mode
DHCP Mode : active
AMT IP Address : 192.168.1.106
yay -S intel-amt-linux
intel-amt-linuxConnect to the AMT IP shown above, username admin, password from ~/.amt-mebx-password.txt.