Drivers and Secure Boot

Anti-Cheat

Epic's Easy Anti-Cheat (EAC) Linux v2 only runs on a system with a locked-down, verifiable boot chain. RakuOS checks those requirements for you.

Checking

sudo rakuos eac-check

Or open RakuOS System, page System, and click Anti-Cheat. The app shows a colored dot (green, yellow, red) and, when clicked, every requirement with how to fix it. Some items need root, so the terminal command gives the full picture.

It checks nine things:

  1. Secure Boot is on
  2. every enrolled key is a well-known one
  3. no unsigned driver is loaded, and signatures are enforced
  4. a TPM 2.0 is present
  5. measured boot works
  6. the IOMMU is on, without passthrough
  7. kernel lockdown is set at boot
  8. kexec is disabled at boot
  9. the BPF security module is active

Common fixes

ProblemFix
Secure Boot is offrun sudo rakuos enroll-secureboot-key first, then enable Secure Boot in the firmware settings and finish MOK Manager (password rakuos). See Secure Boot
"Not well-known: …" keyssudo rakuos enroll-secureboot-key, then choose Delete MOK at the next boot
No TPMenable fTPM (AMD) or PTT (Intel) in the firmware settings
An unsigned driver was loadedremove the akmod or DKMS package that built it. See Drivers
Booted in legacy BIOS modeneeds a reinstall in UEFI mode

Why it's yellow, not green

On a correctly set up machine the result is yellow: RakuOS meets every requirement on its side, but the RakuOS key still has to be added to Epic's list of well-known keys. We're waiting on Epic for that step, and EAC v2 games depend on it.

On the Steam Deck there's one more limit: Epic doesn't support EAC Linux v2 on it yet.