Skip to content
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

Trenchboot AEM crashes on Lenovo Thinkpad T14 Gen 1 (Intel) #25

Open
TommyTran732 opened this issue May 5, 2024 · 1 comment
Open
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior. W: todo Workflow: todo. The issue is in the initial to do state.

Comments

@TommyTran732
Copy link

TommyTran732 commented May 5, 2024

Affected component(s) or functionality
Trenchboot AEM.

Brief summary
On my T14, after booting Qubes with AEM is selected, Grub will attempt to load in the SINIT file CFL_SINIT_20221220_PRODUCTION_REL_NT_O1_1.10.1_signed. As it is loading it in, the system reboots, and if I choose Qubes with AEM again, I get the following error:

1000001763

I have verified that

  • The Thinkpad is booting in legacy boot mode
  • The SINIT binary one is the correct one (the CPU is an i7-10610U)
  • Intel TXT is enabled
  • Hyperthreading is enabled in firmware settings (Lenovo firmware does not require Hyperthreading to be enabled for TXT to work, but I know on Dell firmware it is a requirement so I kept it enabled there)

Version
p4-rc1

To Reproduce
Steps to reproduce the behavior:

  1. Import the signature at https://dl.3mdeb.com/open-source-firmware/QubesOS/p4-rc1/RPM-GPG-KEY-aem to rpm in dom0
  2. Add the repo at https://dl.3mdeb.com/open-source-firmware/QubesOS/p4-rc1/ to dom0
  3. qubes-dom0-update
  4. qubes-dom0-update anti-evil-maid
  5. Add the SINIT file to /boot, setup the TPM and installing AEM to the boot drive
  6. Reboot

Expected behavior
The system boots properly and I can setup AEM.

Actual behavior
The system reboots and I get TXT_ERRORCODE reports failure: 0xc00014f1.

@TommyTran732 TommyTran732 added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior. W: todo Workflow: todo. The issue is in the initial to do state. labels May 5, 2024
@TommyTran732
Copy link
Author

With the latest build (4.2.1), it just reboots into a blank screen and does nothing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior. W: todo Workflow: todo. The issue is in the initial to do state.
Projects
None yet
Development

No branches or pull requests

1 participant